Select to view content in your preferred language

Failing to Stage Utility Networks on Enterprise geodatabase.

669
6
Jump to solution
11-15-2024 06:01 AM
Yogesh_Chavan
Frequent Contributor

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

Yogesh_Chavan_1-1731678036519.png

 

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 = 

Yogesh_Chavan_0-1731679382293.png

SQL Server 2022.

 

0 Kudos
1 Solution

Accepted Solutions
MikeMillerGIS
Esri Frequent Contributor

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?

View solution in original post

0 Kudos
6 Replies
MikeMillerGIS
Esri Frequent Contributor

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?

0 Kudos
Yogesh_Chavan
Frequent Contributor

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?

Yogesh_Chavan_0-1731909455561.pngYogesh_Chavan_1-1731910370447.png

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.

Yogesh_Chavan_0-1731925056707.png

Is there anything specific this user is missing?

0 Kudos
MikeMillerGIS
Esri Frequent Contributor

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

Yogesh_Chavan
Frequent Contributor

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

Thank you @MikeMillerGIS 

0 Kudos
Scott-Shavnore
Emerging Contributor

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

0 Kudos
Yogesh_Chavan
Frequent Contributor

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!!

0 Kudos