Latest Contributions by MilesThompson

Has this gone anywhere? We need this capability in Field Maps for tree maintenance activities and inspection records. ... View more

I did, but I don't remember exactly what the solution was. I remade all my hosted layers and also updated all the apps and desktop versions before I remade them.   Everything has been working fine since then. ... View more

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.   ... View more

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/synchronizeReplica, 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/synchronizeReplica, 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/synchronizeReplica, 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."         ... View more

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/bbbf32a7-9a2d-4dfb-8a45-b3ff7750310b, 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.} ... View more

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.  ... View more

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.  ... View more

We would use this functionality in a botanical garden setting for treatment records and plant maintenance records (pruning, injections, etc)...for instance, groups of trees the arborists treat for a fungus or pest issue, which is repeated multiple times within a season, and also annually...so a lot of repetitive table entries currently (as in hundreds and hundreds every year)....could use it in Collector more so, but a Web App would work as well. ... View more

My maps downloaded just now in Collector Classic. Made some edits off line, and was able to sync edits back to AGOL. Still cannot download offline areas on the new Collector (but thimaybe be a separate issue?).  ... View more

Thanks for the update Doug. Looking forward to resolving this. ... View more

Hope they find the issue quickly. I have aerial packages sideloaded onto both iPads. The AGOL maps I'm trying to download are just one editable point layer with some tables and a couple polygon layers to reference planting beds, turf areas, and pathways that cannot be discerned in the aerial basemap package. Unfortunately, the layers were all updated last week and re-populated to AGOL...no old map versions exist.  I was getting an error for wrong coordinate system yesterday (for the tile package I has used just fine for over a year now), so I remade a smaller tile package with the AGOL option using the ArcMap tool, and used that during the map download process...now I get and error "data type mismatch". I can load the map in online mode, but cannot download anything. ... View more

Same issue here....tried it with Collector "classic" (which I use on our older version iPad) and a new iPad with both the new and old collector versions....used to work just fine with a map used for updating trees and marking areas that need attention for employees....now none of it works. On top of that, I have a meeting tomorrow with the big boss to go over all this offline data collection stuff and how we are implementing it...and trying to justify the just received maintenance coontract with ESRI...right now, it's not going to go well. ... View more