ESRI Field Maps Sync Errors

5965
12
09-29-2022 08:40 AM
MilesThompson
Occasional Contributor

I have been working on updating our GIS workflows to mobile data collection, and am having issues with several layers from ArcGIS Online, and syncing data after offline data collection.

I get the following errors:

GENERAL ERRORS

Unable to synchronize replica.
Exporting data changes failed.


I have followed all the leads here, https://community.esri.com/t5/arcgis-field-maps-blog/arcgis-field-maps-offline-edits-fail-to-sync-le...

Recreated entire new hosted feature layers to replace the ones causing issues, new copies of maps, signed out/in, cleared caches, everything....still get errors.

Does anyone have any ideas of where to look next?

- Miles

12 Replies
BrendanNewell
Esri Contributor

Hi @MilesThompson,

Definitely a great resource from @GlenShepherd 

Another great step you have taken is republishing the hosted feature layers, as the issue still persists.

So, this may suggest that one of the layers is causing the unexpected behaviour with the sync.. 

I am not sure how many hosted feature services we have here. But let's say we have a single hosted feature services containing 4 layers. Remove a layer and republish, rinse and repeat in till we can sync the data from offline. I know this can be tedious but this will help us isolate if there a single layer causing this behaviour.

When we have identified any layers causing issues we can drill down on that specific layer to identify the cause.

Cheers,
Brendan

🙂
0 Kudos
MilesThompson
Occasional Contributor

I re-published the features as single hosted layers so I could add and remjve them from maps easier.

 

I will get a list of all the layers that I am having issues with and get log files that show the errors.... Hopefully this next week, but I have a lot of other things on my schedule ahead of this. 

0 Kudos
DougBrowning
MVP Esteemed Contributor

Is there anything in the log file?  Make sure to turn it on then try and get the error.

0 Kudos
MilesThompson
Occasional Contributor

I will see what I have on Monday. There are at least 3 feature layers that are causing issues. If I remove them all, the offline data in the other layers sync just fine. 

0 Kudos
MilesThompson
Occasional Contributor

Here is the log file from the last time I tried to sync, after completing all the steps outlined above.

9/29/22, 10:36 AM [77571f9e-8e01-4e96-b94e-577e75205da8] - Layer: (Barriers) Error: Error Domain=com.esri.arcgis.runtime.services.error Code=500 "Unable to synchronize replica." UserInfo={NSLocalizedFailureReason=Exporting data changes failed., NSURL=https://services6.arcgis.com/cNDpj8YEaSU9UFO9/arcgis/rest/services/Barriers/FeatureServer/jobs/bbbf3..., responseJSON={
error = {
code = 500;
details = (
"Exporting data changes failed."
);
message = "Unable to synchronize replica.";
};
lastUpdatedTime = 1664465798177;
replicaID = "9bf55c59-7fb1-4aa8-8f8f-277c572a323f";
replicaName = "MyReplica_e49741a6d4684a42bad79219fb610786";
status = Failed;
submissionTime = 1664465796310;
targetType = client;
}, AGSCredentialErrorKey=username: mlsthmpsn
token: hfY4d1x8hOTpZzfZe4vTjkAo-tiAPaFxtg9AOHVIIjkT_DmwcdLr2bMnUREB270whJdienTWW37a0LtmzcGFdTiIjr8cidIlGz8jSJgUZVe9iAj8w57etsYRny7YJOgoPVLzj94AYJ678ZMS2kWaFe0P-DIRkW4kyrvvcD88VPogdGjohz-9lxVeJIa8GrCaqbL49JqAKEdyY70K_F8HcSXJ_apnBVAcYHJ4HJjDVgndu6FlXENVYFnEA9KNb2jpHv9TbAS_ePPMIO0t2ymcMKDqy8KjJtPajJNs74Dvs2Ajh9UE7JtGvTsdc4EqDQlo
tokenURL: https://www.arcgis.com/sharing/rest/generateToken
tokenExpiration: 2022-09-29 15:54:14 +0000
, NSLocalizedDescription=Unable to synchronize replica.}

0 Kudos
MilesThompson
Occasional Contributor

Here are the log files when I put the layers in one map and try to sync, which all seem to be a similar issue?:

10/3/22, 8:30 AM [ea2b1a65-a5b9-4320-8a44-457aacb15405] - Layer: (Pavement Segment) Error: Error Domain=com.esri.arcgis.runtime.services.error Code=404 "Unable to synchronize replica." UserInfo={NSLocalizedFailureReason=Replica with GUID : 490d8049-2467-4331-b3e6-378afb64282d does not exist on the server., NSURL=https://services6.arcgis.com/cNDpj8YEaSU9UFO9/arcgis/rest/services/Pathways/FeatureServer/synchroniz..., responseJSON={
error = {
code = 404;
details = (
"Replica with GUID : 490d8049-2467-4331-b3e6-378afb64282d does not exist on the server."
);
message = "Unable to synchronize replica.";
};
}, AGSCredentialErrorKey=username: mlsthmpsn
token: Q3q_ESZHFuHL4dn9t8bS9vF7YOsrukz2mI0PDLpPEh0-sobY4dhZLruDalCeuXSVlq7qkwVb_xXpXZ3GUZw3OFma0k4cPlVCN1Se_Yxi_NECZO1pbydmNmTwsJqtsKhLv2h6QJ8_aHRj9F5GzZyWyMBIyeKhKy7SBTSNSIjU_eziMzc-hS5olz_YqI5qh945zSQSDNuUHxtMSj3H6PAdIIcnM4u4FN2N7liVFlU-XYznWxAMmFeU9Uma7MMKkg6ZtpUSy3icjZ-Xs93lLVKheCqjNGU1PxvWEXti_e0_YABWSS6-MRMhyqypptji7JBw
tokenURL: https://www.arcgis.com/sharing/rest/generateToken
tokenExpiration: 2022-10-03 13:41:26 +0000
, NSLocalizedDescription=Unable to synchronize replica.}

 

10/3/22, 8:30 AM [ea2b1a65-a5b9-4320-8a44-457aacb15405] - Layer: (Unpaved Surface) Error: Error Domain=com.esri.arcgis.runtime.services.error Code=404 "Unable to synchronize replica." UserInfo={NSLocalizedFailureReason=Replica with GUID : 490d8049-2467-4331-b3e6-378afb64282d does not exist on the server., NSURL=https://services6.arcgis.com/cNDpj8YEaSU9UFO9/arcgis/rest/services/Pathways/FeatureServer/synchroniz..., responseJSON={
error = {
code = 404;
details = (
"Replica with GUID : 490d8049-2467-4331-b3e6-378afb64282d does not exist on the server."
);
message = "Unable to synchronize replica.";
};
}, AGSCredentialErrorKey=username: mlsthmpsn
token: Q3q_ESZHFuHL4dn9t8bS9vF7YOsrukz2mI0PDLpPEh0-sobY4dhZLruDalCeuXSVlq7qkwVb_xXpXZ3GUZw3OFma0k4cPlVCN1Se_Yxi_NECZO1pbydmNmTwsJqtsKhLv2h6QJ8_aHRj9F5GzZyWyMBIyeKhKy7SBTSNSIjU_eziMzc-hS5olz_YqI5qh945zSQSDNuUHxtMSj3H6PAdIIcnM4u4FN2N7liVFlU-XYznWxAMmFeU9Uma7MMKkg6ZtpUSy3icjZ-Xs93lLVKheCqjNGU1PxvWEXti_e0_YABWSS6-MRMhyqypptji7JBw
tokenURL: https://www.arcgis.com/sharing/rest/generateToken
tokenExpiration: 2022-10-03 13:41:26 +0000
, NSLocalizedDescription=Unable to synchronize replica.}

 

10/3/22, 8:30 AM [ea2b1a65-a5b9-4320-8a44-457aacb15405] - Layer: (Barriers) Error: Error Domain=com.esri.arcgis.runtime.services.error Code=404 "Unable to synchronize replica." UserInfo={NSLocalizedFailureReason=Replica with GUID : b470824f-0550-4aca-8ee6-32d6b7591822 does not exist on the server., NSURL=https://services6.arcgis.com/cNDpj8YEaSU9UFO9/arcgis/rest/services/Barriers/FeatureServer/synchroniz..., responseJSON={
error = {
code = 404;
details = (
"Replica with GUID : b470824f-0550-4aca-8ee6-32d6b7591822 does not exist on the server."
);
message = "Unable to synchronize replica.";
};
}, AGSCredentialErrorKey=username: mlsthmpsn
token: Q3q_ESZHFuHL4dn9t8bS9vF7YOsrukz2mI0PDLpPEh0-sobY4dhZLruDalCeuXSVlq7qkwVb_xXpXZ3GUZw3OFma0k4cPlVCN1Se_Yxi_NECZO1pbydmNmTwsJqtsKhLv2h6QJ8_aHRj9F5GzZyWyMBIyeKhKy7SBTSNSIjU_eziMzc-hS5olz_YqI5qh945zSQSDNuUHxtMSj3H6PAdIIcnM4u4FN2N7liVFlU-XYznWxAMmFeU9Uma7MMKkg6ZtpUSy3icjZ-Xs93lLVKheCqjNGU1PxvWEXti_e0_YABWSS6-MRMhyqypptji7JBw
tokenURL: https://www.arcgis.com/sharing/rest/generateToken
tokenExpiration: 2022-10-03 13:41:26 +0000
, NSLocalizedDescription=Unable to synchronize replica.}

 

10/3/22, 8:30 AM [ea2b1a65-a5b9-4320-8a44-457aacb15405] - Message 16/17: Layer result: Sync failed. Name: Barriers, LayerID: 0, TableName: Barrier, URL: https://services6.arcgis.com/cNDpj8YEaSU9UFO9/arcgis/rest/services/Barriers/FeatureServer/0 Job error 22 Propagated error. Error while handling start sync geodatabase on the server. Job error -1 Service error code 404. Unable to synchronize replica.
Details:
Replica with GUID : b470824f-0550-4aca-8ee6-32d6b7591822 does not exist on the server.

 

10/3/22, 8:30 AM [ea2b1a65-a5b9-4320-8a44-457aacb15405] - Message 15/17: Layer result: Sync failed. Name: Pavement Segment, LayerID: 0, TableName: Pavement_Segment, URL: https://services6.arcgis.com/cNDpj8YEaSU9UFO9/arcgis/rest/services/Pathways/FeatureServer/0 Job error 22 Propagated error. Error while handling start sync geodatabase on the server. Job error -1 Service error code 404. Unable to synchronize replica.
Details:
Replica with GUID : 490d8049-2467-4331-b3e6-378afb64282d does not exist on the server.

 

10/3/22, 8:30 AM [ea2b1a65-a5b9-4320-8a44-457aacb15405] - Message 14/17: Layer result: Sync failed. Name: Unpaved Surface, LayerID: 1, TableName: Unpaved_Surface, URL: https://services6.arcgis.com/cNDpj8YEaSU9UFO9/arcgis/rest/services/Pathways/FeatureServer/1 Job error 22 Propagated error. Error while handling start sync geodatabase on the server. Job error -1 Service error code 404. Unable to synchronize replica.
Details:
Replica with GUID : 490d8049-2467-4331-b3e6-378afb64282d does not exist on the server.

 

10/3/22, 8:30 AM [ea2b1a65-a5b9-4320-8a44-457aacb15405] - Message 13/17: Sync geodatabase: Failed: "Job error 22 Propagated error. Error while handling start sync geodatabase on the server. Job error -1 Service error code 404. Unable to synchronize replica.
Details:
Replica with GUID : 490d8049-2467-4331-b3e6-378afb64282d does not exist on the server."

 

10/3/22, 8:30 AM [ea2b1a65-a5b9-4320-8a44-457aacb15405] - Message 12/17: Sync geodatabase: Failed: "Job error 22 Propagated error. Error while handling start sync geodatabase on the server. Job error -1 Service error code 404. Unable to synchronize replica.
Details:
Replica with GUID : b470824f-0550-4aca-8ee6-32d6b7591822 does not exist on the server."

 

 

 

 

0 Kudos
DougBrowning
MVP Esteemed Contributor

Seems like a rights issue but I assume you tried that.  Or maybe the repilca was created with a different user than the sync?  Sorry not sure.

"Replica with GUID : b470824f-0550-4aca-8ee6-32d6b7591822 does not exist on the server."
);
message = "Unable to synchronize replica.";
};
}, AGSCredentialErrorKey=username: mlsthmpsn

0 Kudos
MilesThompson
Occasional Contributor

Yeah, that was one of the suggestions from @GlenShepherd  post, about making sure to try an Admin level, which mine is....and I am the only user in our organization, so there is no other log-in that it could be.

 

0 Kudos
jtmouw_NCDOT
Regular Contributor

Did you ever find a solution for this? We recently had a few layers begin to give us the same error.