"No permissions to sync replica" error

5103
2
Jump to solution
02-04-2016 05:27 PM
MichaelDavis3
Occasional Contributor III

We've run into a bit of an issue checking in field data from a mobile app.

We have an app installed on client infrastructure that requires the use of a token to connect to the host ArcGIS Server.  Their field crew checked out a number of databases using a token generated by an employee who then left for another job.  Since that token is no longer valid we switched to a new one created using the credentials of another employee.  When trying to check in data from one of the replicas created using the old token we get a strange error:

"No permissions to sync replica: {long replica ID string}"

This error message would appear to indicate that the replica is somehow tied to the token (and user account) that was used to generate it.  Is this correct?  Has anyone else seen this error? Any suggestions to work around this issue are appreciated, we have a significant amount of filed data waiting to check-in I'm not really looking forward to converting a stack of runtime databases to file geodatabase and manually adding the data. 

0 Kudos
1 Solution

Accepted Solutions
YueWu1
by Esri Regular Contributor
Esri Regular Contributor

Hi Michael,

Have you checked this documentation talks about the Sync permission:

ArcGIS REST API - Sync permission

Replicas owned by authenticated users can only be accessed by the owner or the admin user. Consequently, only owners and admin users can sync or unregister the replica. Replicas owned by anonymous users can be accessed by anyone who has access to the service.

View solution in original post

2 Replies
YueWu1
by Esri Regular Contributor
Esri Regular Contributor

Hi Michael,

Have you checked this documentation talks about the Sync permission:

ArcGIS REST API - Sync permission

Replicas owned by authenticated users can only be accessed by the owner or the admin user. Consequently, only owners and admin users can sync or unregister the replica. Replicas owned by anonymous users can be accessed by anyone who has access to the service.

MichaelDavis3
Occasional Contributor III

We have a winner!  Turns out the new credentials were created by an account in the Publisher role.  The user was elevated to Admin and the data is checking in without issue.