topic Re: Sync fails at 10.5.1 with 500 error in ArcGIS Enterprise Questions

Sync fails at 10.5.1 with 500 error

FraserHand1 — Mon, 04 Sep 2017 03:05:38 GMT

Hi,

We have just upgraded a customer today to 10.5.1 from 10.4.1 and we have found that syncing with Collector now fails. The edits get pushed up to the enterprise geodatabase but do not come down from ArcGIS Server from the enterprise geodatabase.

After investigating it appears that during the sync process the GP tool is looking for the wrong schema in SQL Server for some of the temporary tables that get created.

We have SDE schema with geodatabase repository
We have GISADMIN schema with feature classes
ArcGIS Server runs as Domain\server_ArcGIS (OSA authentication)
Feature classes have archiving enabled

If we go offline with Collector the replica creation works fine, and if we sync, the edits get pushed up from Collector but it does not refresh the data from the enterprise geodatabase to the mobile device – we get a 500 sync failed error.

NOTE: The feature class is GIS.GISADMIN.SomePoints – syncing fails – ArcGIS Server has correct editing permissions assigned

If we give the ArcGIS Server creation rights on the enterprise geodatabase and create the feature class to be GIS.” Domain\server_ArcGIS”.SomePoints then all works as expected. If we set ArcGIS Server to connect to the enterprise geodatabase as the data schema owner (as a db connection GISADMIN) all works as expected.

This workflow was fine 10.1 through 10.4.1 – this customer has been using it.

Please note that versioned feature classes work as expected. It is just an issue with archiving.

Also be aware we have applied the recent SQL Server Permissions patch (10.5.1)

Has anyone hit this? This seems like a bit of a biggie.

Many thanks,

Fraser

Re: Sync fails at 10.5.1 with 500 error

JoeHershman — Fri, 15 Sep 2017 11:42:17 GMT

I have observed the exact same issue, but did not think to test the scenario you found that works.

See: Download Sync not working in AGS 10.5.1 . In my case it is a Runtime application that presents the identical issue. I honestly question whether esri tests their software at all. This is the standard configuration, how can it never have been tested.

Re: Sync fails at 10.5.1 with 500 error

JustinBurdette — Wed, 27 Sep 2017 13:49:23 GMT

We also tried to upgrade to server 10.5.1 and found the same problems so we rolled back to 10.5. Does ESRI know this is a huge problem? I can't find any bug reported that mentions this. It is a show stopper for sure if you do any offline collector editing and suddenly the sync is not working.

Re: Sync fails at 10.5.1 with 500 error

FraserHand1 — Wed, 27 Sep 2017 19:33:51 GMT

Hi Justin,

I have been trying to work through this will Esri Inc support but at this point they haven't been able to reproduce - even though I have done it consistently in Azure and on various customer sites. Have you logged a support call and shraed your workflow with Esri?

Thanks,

Fraser

Re: Sync fails at 10.5.1 with 500 error

JustinBurdette — Wed, 27 Sep 2017 19:42:34 GMT

No, we did not, after the problem was discovered we saw the 2 other posts on geonet and decided to rollback to 10.5, assuming that ESRI knew about the issue.

Re: Sync fails at 10.5.1 with 500 error

FraserHand1 — Wed, 27 Sep 2017 20:29:54 GMT

Hi, AFAIK they didn't - the issue is in the sync tools - when it is looking for the onprem changes it is looking in the wrong schema for a temp table - in SQL anyway - which causes it to fail. I would most definitely log an issue and also highlight you had to roll back to ensure your workflow didn't break.

Fraser

Re: Sync fails at 10.5.1 with 500 error

JoeHershman — Wed, 27 Sep 2017 22:06:35 GMT

We have reported the issue with support. I do not know status nor have a formal bug. I have sent them this link to see it is occurring with others

Re: Sync fails at 10.5.1 with 500 error

JonathanQuinn — Thu, 28 Sep 2017 15:53:27 GMT

Full disclosure, I rarely if ever work with syncing, but throwing this out there in case it's helpful; getting SDEINTERCEPT logs may help identify if there's a invalid SQL statement that's being sent. If it's schema related, you should be able to identify this in the SDEINTERCEPT logs:

How To: Diagnose ArcSDE connection and performance issues using SDEINTERCEPT

They may help Support log a bug if required.

Re: Sync fails at 10.5.1 with 500 error

JoeHershman — Thu, 28 Sep 2017 18:30:35 GMT

When things work on versions 10.3.1 through 10.5, with the same exact setup it certainly makes one think it has something to do with 10.5.1.

Re: Sync fails at 10.5.1 with 500 error

JustinBurdette — Fri, 10 Nov 2017 16:38:13 GMT

ESRI ever resolve these issues for any of you? I'd like to get our server up to 10.5 if the sync functions would work.

Re: Sync fails at 10.5.1 with 500 error

JoeHershman — Fri, 10 Nov 2017 16:48:09 GMT

The issue is at 10.5.1 and 10.6 not at 10.5. Syncing works at 10.5. There is a 10.5 patch associated to sync at 10.5 Esri Support 10.5 (10.5.1) . This fixes a bug that occurs if you are using a workflow that includes copy and register of your replicas. Sync will fail without the patch is the user registering the replica did not create the replica or is an admin

Re: Sync fails at 10.5.1 with 500 error

JustinBurdette — Fri, 10 Nov 2017 16:52:02 GMT

Typo on my end, I meant 10.5.1.....we are at 10.5 now and sync works fine.

Re: Sync fails at 10.5.1 with 500 error

FraserHand1 — Wed, 22 Nov 2017 18:53:21 GMT

Hi,

I passed it to out support team and they logged an issue with Redlands on behalf od the customer. From then I've been out of the loop but I don't believe it was resolved.

Thanks,

Fraser

Re: Sync fails at 10.5.1 with 500 error

FraserHand1 — Wed, 22 Nov 2017 18:54:09 GMT

*our not out

Re: Sync fails at 10.5.1 with 500 error

LucasScharenbroich — Thu, 21 Dec 2017 22:29:42 GMT

Rather than creating another post, I'll bump this one up. On a fresh 10.5.1 installation I have run into the exact same issue that was very well-described in the post.

Feature class owned by a 'GIS' schema named TestPoints
ArcGIS Server connecting using OSA
Feature class has Archiving enabled
Push & Pull sync fails due to the SyncTools trying to access a "<domain\username>".TestPoints instead of GIS.TestPoints

I did try one variation where I created a separate DBMS user named "AGS" and used that in a DBMS connection string rather than an OSA connection string from ArcGIS Server. The same error happened with SyncTools trying to query the AGS.TestPoints feature class.

There is a passing reference in the documentation about using synchronous vs asynchronous methods for checkout that states only asynchronous methods go through SyncTools.

Prepare data for offline use—Documentation | ArcGIS Enterprise

Is there any way to force Collector to use synchronous methods directly against the Feature Service endpoint instead of going through SyncTools? That may be a way to work around the problem.

In the interim, one can turn on "Push Only" synchronization in the Collector settings in order to avoid seeing the error in the application. The downside is that the user needs to create a new checkout in order to see any new point that others have uploaded.

Re: Sync fails at 10.5.1 with 500 error

JoeHershman — Thu, 04 Jan 2018 15:22:43 GMT

The downside is that the user needs to create a new checkout in order to see any new point that others have uploaded.

This is a non-starter in our case. The replicas are far too large and users only have access over a mobile network most of the time. Both generation time and transport time individually preclude this as something we could consider, Certainly, hope this is resolved at upcoming 10.6 and Runtime 100.2 release because we would like to incorporate other fixes and new features from those upcoming releases

Re: Sync fails at 10.5.1 with 500 error

jaykapalczynski — Fri, 29 Jun 2018 19:35:27 GMT

How do I roll back to 10.5 from 10.5.1?

What will this screw up?

Has ESRI stopped testing? Seems like a critical error to simply not alert users before they go through the headache of upgrading, only to find out they have to roll back. Either they knew about it or simply decided not to test their software. Either way a little upsetting.

Re: Sync fails at 10.5.1 with 500 error

ScottPrindle — Wed, 18 Jul 2018 23:11:20 GMT

The root cause of this issue is touched on in a few comments. Joe Hershmanshared the relevant patch for the original issue outlined by OP.

The issue is tied to the database connection file's credentials that were used when publishing the service. More specifically, if the data owner (ex. GISADMIN) differs from the service's publishing credentials (ex. Publisher, GIS, etc.), at 10.5 the sync would fail.

If this is the issue you're encountering, then the patch should be applied to your environment, or upgrade to the most recent release (if possible). If these options don't work, you can attempt to republish your feature services using the data owner (ex. GISADMIN). This is a workaround, so it should only be done if there are no concerns with this approach.

The bug (BUG-000103326) can be viewed here.

Thanks,

Scott

Re: Sync fails at 10.5.1 with 500 error

jaykapalczynski — Thu, 19 Jul 2018 12:41:14 GMT

I am running 10.5.1

I go to my Server that ArcGIS Server is installed on.
Double Click the .msp file
I get this error???

Esri Support 10.5 (10.5.1)

Thoughts? I am assuming that this patch will fix the 10.5.1 install and not the 10.6x

Re: Sync fails at 10.5.1 with 500 error

JoeHershman — Thu, 19 Jul 2018 13:38:36 GMT

It is a 10.5 patch, it will not work on any other version