nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Collector Offline Map Sync Failed "Unknown error occurred"

ChazOlloqui

After a long day of collecting data in the field using an offline map area, we've received the Sync Error "Unknown error occurred". I've followed the instructions of adding global ids to our sde dataset and registering as versioned ("Register the selected objects with the option to move edits to base" unchecked), which allowed us to create an offline map area, but when we try to sync our edits through cell service or wifi, we receive the same error. Does anyone know why this error would arise?

Thanks

Encontre mais publicações marcadas com

Accepted answers

pfoppe

We found a resolution to our issue on SQL Server.

The SQL Server built-in "Editor" account "default schema" was mapped to the "data owner" schema.

by re-mapping the SQL Server "editor" account to its own schema, the offline syncs started working again.

I realize this 'redacted' screen grab is rough... but...

Using MSSQL Server Management Studio - Login to the instance

Security -> Logins -> "Editor account" -> properties (opens the window "Login Properties - <account name>")

Choose "User Mappings" on the right

Columns are:

And you can see the "edit" user was mapped to the "dbo" schema (data owner). This was the problem.

We re-mapped the default schema to the same account:

Hope this helps!

All comments

vijaybadugu

I am able to get rid of the error . Actually the map is Read-Only (Query,Sync) , But When i try to "Check for Updates" in ArcGIS Field Maps, The Updates are not showed up.

pfoppe

That is correct.

For many of our published ArcGIS Server services - we use the "Operating System Authentication" (OSA) login when publishing. This is the Active Directory (AD) account that the ArcGIS Server runs as. Our data admins/publishers will grant the ArcGIS Server AD account the read/write permissions to the database objects. Most of these workflows are for read-only access - publish the service and let customers consume it for mashing up with other datasets.

Although for some workflows (like the Esri offline 'feature server sync' capabilities) we use a SQL Server built-in account; we do NOT use the OSA account. The main driver for this was when the user syncs an offline map, there is a version created and owned by the account that was used to publish to server with (so the account the server uses to connect to SQL). If we used the OSA account, then it was challenging to manage that version without having full geodatabase administration ("sde" account) access. With the 'headless built-in SQL account', we can provide that account connection file to certain staff members who can then manage their back-end version by rec/posting to the parent version. The only way to do that with OSA would be to login to a computer with that same OSA account, or over-ride the version permissions to "PUBLIC", or give the user full SDE level admin access.

So for the situation highlighted above...

GIS Specialists use a built-in SQL account to 'own' the data. This is the account they would connect as when creating a feature class, granting permissions, applying indexes, making schema changes, etc. Lets call this account "dataowner". Objects in the database (lets call the database "mydatabase") end up looking like: mydatabase.dataowner.table_name

The GIS specialists then use a different built-in SQL account to 'publish' the data to ArcGIS Server. This is the account they would connect with when publishing from ArcMap/ArcGIS PRO. Lets call this account "dataeditor". The GIS Spec will use the "dataowner" account to grant read/modify permissions on the "table_name" to the dataeditor account.

When the user synchronizes the offline edit, then a version is usually created in the geodatabase that is owned by the 'dataeditor' account. EX - dataeditor.my_version

The problem we ran into was that when the 'dataeditor' SQL account was created, it was inadvertently mapped to the schema owned by "dataowner".

HTH.

JasonWegner

Hi Patrick, I'm having very similar issues, running SQL as well. Could you clarify your statement:

The SQL Server built-in "Editor" account "default schema" was mapped to the "data owner" schema.

Are you talking about the administrative account that you use to connect to the database, and ultimately publish the service?

pfoppe

We found another inconsistent configuration on one of our SQL Server environments. Posting here for the community.

The account used to publish had the "Connect" permissions granted, but did NOT have the "Create Procedure", "Create Table", or "Create Function". See (redacted) screenshot:

Find this in SQL Server Management Studio under "Databases" -> Right-Click the database -> "Properties" -> "Permissions" and choose the account that was published to the server

pfoppe

We found a resolution to our issue on SQL Server.

The SQL Server built-in "Editor" account "default schema" was mapped to the "data owner" schema.

by re-mapping the SQL Server "editor" account to its own schema, the offline syncs started working again.

I realize this 'redacted' screen grab is rough... but...

Using MSSQL Server Management Studio - Login to the instance

Security -> Logins -> "Editor account" -> properties (opens the window "Login Properties - <account name>")

Choose "User Mappings" on the right

Columns are:

And you can see the "edit" user was mapped to the "dbo" schema (data owner). This was the problem.

We re-mapped the default schema to the same account:

Hope this helps!

pfoppe

We too have started to experience this situation in our ArcGIS Enterprise v10.7.1 environment.

Quick Tech Details:

ArcGIS Enterprise v10.7.1 - MS IIS, Web-adaptor for portal & server, hosting server & federated (non hosting) server. This was upgraded from v10.6.1
Publishing from back-end SQL Server 2017 (running Enterprise Geodatabase v10.6.1)
Published with a SQL "editor" account (not the data schema owner)

If we publish the service with our data schema owner, then the offline download/sync functions as expected. If we publish with a built-in SQL Server "editor" account, then the sync fails with the same behavior mentioned in this thread "No path for delta data changes". All other references we searched for were related to the ORACLE "create table" issues.

We deployed a feature service with this configuration (sync enabled and published with a built-in SQL 'editor' account) when we originally built the ArcGIS Enterprise environment at v10.6.1 and were successful with offline sync then. Seems possibly related to the v10.7.1 upgrade?

We may try to upgrade the back-end Enterprise Geodatabase to v10.7.1 to see if it resolves, but expect it to continue to fail.

The back-end SQL Editor account has full "Insert/Create, Update, Delete, Query/Read" permissions on all back-end database tables (including their underlying 'a' and 'd' tables in the traditional versioned configuration). The SQL editor account also has "connect, create table/procedure/view/function" permissions.

Any help is appreciated. Thanks.

ChazOlloqui

After referencing the links Katherine Clark‌ has posted, the solutions seem to be isolated to an Oracle database. We are using SQL Server. After granting CREATE TABLE privileges to the database user (which I'm sure were already granted), I've tried creating the SDE_UUID_TEMP temporary table manually in our SQL Server database, but still no dice for either of those methods.

Can someone explain how the ArcGIS Online account we used to collect the offline data is related to the database user?

ChazOlloqui

I had just found the first link when I received your reply! I believe I've found the answer, but will respond when I know for sure.

Thank you!

Katie_Clark

Thanks for posting a screenshot of the log! Unfortunately I have to admit that I don't know an exact answer to this issue, but it gives anyone else trying to help a much better lead to go on when troubleshooting.

I did find these pages when researching that error message:

ArcGIS Enterprise 10.6.1 Sync Service: No path for delta data changes

Error: {"code":400,"description","Unable to complete operation."} Failed to execute (Sync Feature Service Replica)

Maybe those will help? Good luck!!

ChazOlloqui

We are using the new version of Collector. I have found the logs in Server Manager and have attached the screenshot. I imagine it is related to the "No path for delta data changes" error...?

Katie_Clark

Which version of Collector are you using? New or Classic? If you're using the newer version of Collector, are you able to get a more detailed error message from the logs?

Participe da Conversa

Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.

Links Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.