Error 001904: SDE or DBMS admin user cannot create a utility network

[DiegoMCastellari]

Hi! 
We are having problems trying to create a Utility Network in a SDE database. When we try to run the tool "Create Utility Network", the error 1094 occurs.

We followed the solution detailed in this post: 

• create a user running the tool from ArcGIS Pro;
• connect to the db with this user and create the datasaet and polygon layer;
• run the tool to create the utility network;

but no luck.

Before that, we tried creating the user directly from the db, with different roles and privileges, but no luck.

We are using ArcGIS Pro 3.2.2, SQL Server 2017 and ArcGIS Enterprise 11.3.

Is there something else we can try to create the Utility Network in the SDE?

[wizgis]

Hi @DiegoMCastellari 

Does the service area feature class that has been created and specified while creating utility network contains a geometry in it. As the following doc suggests that there should be features inside the service area feature class : https://pro.arcgis.com/en/pro-app/latest/help/data/utility-network/create-a-utility-network.htm

So I was not able to reproduce the issue however, couple of things that can be checked

• Make sure you are connected to the geodatabase as a DataOwner (i.e. a user that has following permissions at the backend : Create Table, Create View & Create Procedure)
• Make sure that when you add feature dataset to the Create Utility Network tool it is from the connection of user that has following permissions : Create Table, Create View & Create Procedure. 

[DiegoMCastellari]

The service area feature class has a polygon in it.

About the user, it is a DataOwner. When the user is created with the ArcGIS Pro tool, it's just a viewer, then we had to change the permissions from inside the db. We also tried with different user's permissions, but we got the same error.

[George_Thompson]

What is the name of the user that owns the data?

I believe that must be the same user that creates the utility network?

[DiegoMCastellari]

The user's name is MGUN. With that same user, we created a connection to the db, and from that connection we created the dataset and feature class.
And then with that same connection, we tried to create the utility network. At that point we keep getting the error.

In some post I read that the user that creates the utility network must have the same name than the schema. Do we have to configure something in the db? Or this condition is already met in the example above?

[wizgis]

Thank you @DiegoMCastellari for sharing the screen shots it does help. Just wanted to confirm few things here to understand your workflow:

1. How is user/dataowner (MGUN) created ? Using the Created DB user GP tool present in ArcGIS Pro or from SQL Server Management Studio. 
2. Does the user (MGUN) has the following permissions: 
   1. Create Table
   2. Create View
   3. Create Procedure

Additionally, in SQL Server Management studio after logging into the instance, navigate to Security > Login > Right click on the login (MGUN) > Properties. In the login properties window click on user mapping and check that the user (MGUN) is correctly mapped to the geodatabase where you wish to create Utility Network and the schema name matches the name of the user. Following screenshot can be used for reference. 

Hope this helps.

[DiegoMCastellari]

Exactly, the user was created using the ArcGIS Pro GP tool. But then the DBA had to change some configurations in the db, because this users was just a viewer, couldn't do anything on the db. All this mapping configuration was done by the DBA.

We finally got it, after several attemps. I'll describe what we did, and if maybe someone could explain whats happenning and kill my ignorance, will be welcome. 
Two users were created from the SQL Server. With one user, a new database was created, and enabled enterprise (with Pro); and then with the second user we did all utility network creation workflow. That worked.
The same process was done before, but using the sde user to create the db, and that didn't work.

Thanks both @wizgis and @George_Thompson for helping!