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; } } }

Failing to Stage Utility Networks on Enterprise geodatabase.

Yogesh_Chavan

When trying to execute Stage Utility Network Geoprocessing tool in ArcGIS Pro, we are hitting Error:999999 and ImportXML failing.

In some testing we tried importing the Service Territory feature class from the asset package to this SDE, but it fails as well. Importing-Exporting any other layers(non-asset package) works without any issues.

What are we missing? We tried the same on a FGDB, and the UNM was created without any issues!!

Pro version = 3.3

SDE Version =

SQL Server 2022.

Najděte více příspěvků označených jako

Accepted answers

MikeMillerGIS

My guess is it is trying to create a 64bit object id, which was not supported in the 3.1 gdb. Have you tried to run upgrade geodatabase?

All comments

MikeMillerGIS

My guess is it is trying to create a 64bit object id, which was not supported in the 3.1 gdb. Have you tried to run upgrade geodatabase?

Yogesh_Chavan

Hi @MikeMillerGIS , thank you so much for looking into this.

I tried upgrading the SDE to 3.3 and the issue shows some progress.

Now, the error is quite more precise, do we need any specific user requirement for creating a UNM?

To tackle this we created a new user named UNM with non dbo role and had create, update, delete permissions. This time it gave the same import failed permission error.

Is there anything specific this user is missing?

MikeMillerGIS

I am not sure, The user definitely cannot be a dbo, so check the permissions of the new user.

Yogesh_Chavan

We found some missing permissions on the new user, and updating them worked well and now we are able to proceed.

Thank you @MikeMillerGIS

Scott-Shavnore

Hi @Yogesh_Chavan. Do you recall which specific permissions were needed that resolved the ImportXMLWorkspaceDoucment error?

Yogesh_Chavan

Hi @Scott-Shavnore,

I can't remember exactly, but I am 75% sure that it was related to one of the missing CREATE permissions maybe the CREATE_TABLE, or SNAPSHOT.

Hope this helps!!

Připojte se ke konverzaci

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

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