Sync Failed but Data being uploaded successfully

[VickyFu]

The data collected in the field can be uploaded successfully. But, "Sync Failed" was popped up all the time. It says Sync Replica Internal Error. 

I checked the troubleshooting blog. It showed that the issue occurred on those layers I shared from ArcGIS Pro to web. The code is  "500". I tried changing those layers either editable or non-editable, which does not resolve the issue. 

Does anyone have the same issue and have a solution?

Thank you very much! 

[ColinLawrence]

Hi @VickyFu , are you seeing a consistent sync failure on a given map (or data used across multiple maps)? There are scenarios where you might see a sync failure message but the data is actually sync'd back to the service successfully. Are you using attachments, and if so, are all of your attachments added client side making it back to the service? The sync failure can also happen when downloading the most recent changes from the service as the sync process is bidirectional. Let me know if you are still seeing consistent problems with syncing and we can troubleshoot further. Thanks!

[VickyFu]

Hi Colin, thank you for helping!

Yes, the issue is still there. I have a same scenario that data is sync'd back successfully but a sync failure message is shown up. I tried using attachments and not using it. They both can be sync'd back. 

As I said, the errors occur only on those layers being published from ArcGIS Pro to web based on troubleshooting log. For those layers I created by Field Map Designer, they are able to be sync'd.

Regards,

Vicky

[ColinLawrence]

Do you mean the troubleshooting log is pointing to a specific layer, and that layer is one you published from Pro? Is there anything unique about what is in that layer and have you tried republishing (or publishing another copy of it) to see if you can reproduce still? Just to get the whole picture, are you creating layers from scratch in Designer or using a template?

[VickyFu]

Yes, it happened on specific layers I published from Pro. But I don't see any special on these layers. They are sort of database. I tried republishing or publishing a copy, the error is still there. 

I created other layers from scratch in Designer, which are good to be sync'd. 

[ColinLawrence]

If you are working in ArcGIS Online, are you able to share the Map and feature service(s) to a Group and invite the user "arcgisfieldmaps"? That way I cant attempt to reproduce the problem and see if I can debug what is happening. If you are using Portal please let me know which version. 

[VickyFu · Accepted solution]

Hi Colin,

I am not able to share the Map out of our organization. But, the issue is resolved after I change those layers to shapefiles and then republish them although I still don't know the root cause. 

I am very thankful for your help. Your posts and questions made me think more about those specific layers instead of being stuck with Field Map itself. 

Regards,

Vicky

[ColinLawrence]

Good to hear things are working for you now. So it sounds like potentially a setting at the Geodatabase level was causing this issue. If you decide to dig into this more at a later time let me know!

[VickyFu]

Could you please explain more about what kind of setting at the Geodatabase level can cause the issue? I'd like to learn more so that I might be able to fix it at its core. Thank you.

[ColinLawrence]

Not really sure to be honest as it is not my expertise but there are some differences where it could be factoring in. The shapefile is going to be published as a single standalone layer whereas the layer in your GDB could contain relationships with other layers and tables (and attachments) that would be published along with that layer in the same service. Shapefiles also do not support the storing of Subtypes and Domains so if those are being used in you GDB layers, that would be another difference in what gets published with the service. You could try copying the layer to a new geodatabase and publishing that new copy.