topic Re: enable utility network topology errors in ArcGIS Utility Network Questions

enable utility network topology errors

gpgisandsky — Fri, 18 Apr 2025 16:32:06 GMT

Hi,

I deployed Utility Network v7 on ArcGIS Enterprise 11.3 (Oracle 19) with ArcGIS Pro 3.3.2.

When I try to enable the Utility Network topology directly on the .sde connection, it fails.

I also tried enabling the Utility Network topology through the service, but that fails as well.:

ERROR 999999: Something unexpected caused the tool to fail. Contact Esri Technical Support (http://esriurl.com/support) to Report a Bug, and refer to the error help for potential solutions or workarounds.

Failed to execute (EnableNetworkTopology).

I also tried updating ArcGIS Pro from 3.3.2 to 3.3.5, but the operation still fails.

I also tried to excute repair geometry but when I select xy Device from my project the following error appear:

Error 003341 This operation is not supported on Esri Spatial Types.

Has anyone experienced a similar issue?

Re: enable utility network topology errors

gpgisandsky — Tue, 22 Apr 2025 13:03:58 GMT

@RobertKrisher , @MikeMillerGIS Do you have any ideas?

Re: enable utility network topology errors

RobertKrisher — Tue, 22 Apr 2025 19:10:41 GMT

Please log a case with support.

Re: enable utility network topology errors

DanieleFabro — Tue, 13 May 2025 11:59:15 GMT

Re: enable utility network topology errors

gpgisandsky — Tue, 13 May 2025 12:00:16 GMT

Hi @RobertKrisher the ticket has been opened with ID 03901423 from Italy. Do you have visibility on this?

Re: enable utility network topology errors

RobertKrisher — Tue, 13 May 2025 13:17:30 GMT

@gpgisandsky I will try to keep an eye on it as it develops, but at this point we need to work it through the process until we can get something reproducible to development.

If you copy your utility network from Oracle to a File or Mobile Geodatabase, does it succeed there? If not, that's a much easier reproducible issue to push through support.

If you can enable the network topology in a local geodatabase, try copying the dataset back into an enterprise environment and version the dataset. If versioning fails, that narrows down the issue. If that works, then you can move forward with that utility network.

Re: enable utility network topology errors

gpgisandsky — Tue, 13 May 2025 14:10:21 GMT

Hi @RobertKrisher you are very kind. I tried twice with an empty enterprise gedatabase. I wrote a document with all steps that i follow to migrate asset package to enterprise geodatabase. Also I have assetpackage file and a file geodatabse that I used to try anything. I can enable network topology on file geodatabase and i haven't error within. Can I send you all data and docs by e-mail? Do you need a Oracle dump too?

Re: enable utility network topology errors

RobertKrisher — Tue, 13 May 2025 15:30:43 GMT

@gpgisandsky Does this work in a local geodatabase? What happens if you copy the enabled network topology to enterprise and version it?

Re: enable utility network topology errors

gpgisandsky — Tue, 13 May 2025 17:00:40 GMT

In a local geodatabase anything works fine.

In the enterprice geodatabase I follow these steps:

On Open PRO with un owner
On an empty geodatabase with direct connetcion reti.sde (with branch option) :
- Stage Utility Network (UNTOOLS 3.3.3.1)
- Apply Asset Package (UNTOOLS 3.3.3.1)
On UtilityNetwork dataset and un tables (right click of dataset/table-->manage-->check on versioning branch and Editor Tracking) .
Execute tool “Enable Topology” on reti.sde (branch option and network topology off)

ERROR 999999: Something unexpected caused the tool to fail. Contact Esri Technical Support (http://esriurl.com/support) to Report a Bug, and refer to the error help for potential solutions or workarounds.
FDO error: -2147196578
The requested operation is unsupported by instance db.
Failed to execute (EnableNetworkTopology).

If I open network topology information on db I have the value one on Dirty area count.

Regarding "What happens if you copy the enabled network topology to enterprise and version it?"

Do you want that I try to copy and paste utility network that I have on a file geodabase (with enabled topology) directly in the empty enterprise geodatabase (without stage, apply... steps)?

Re: enable utility network topology errors

Olusoji23 — Wed, 14 May 2025 13:48:53 GMT

I have this same issue too.
After migrating my utility network, the service territory loses critical attributes (e.g., Area, Length). Technical Support confirmed the service territory is empty, which causes the Enable Network Topology tool to fail.

@RobertKrisher

Are there specific steps to preserve attributes during migration?
How can I rebuild the service territory correctly?

Re: enable utility network topology errors

RobertKrisher — Wed, 14 May 2025 15:45:23 GMT

@gpgisandsky yes, I am suggesting you try copying a utility network with an enabled network topology from a local geodatabase to an enterprise geodatabase.

Re: enable utility network topology errors

RobertKrisher — Wed, 14 May 2025 15:48:51 GMT

@Olusoji23 Did you deploy your utility network using the UN Package tools? If so, they should have appended the service territory into your utility network when you staged your utility network. Adding in @MikeMillerGIS from the ArcGIS Solutions team.

Re: enable utility network topology errors

Olusoji23 — Wed, 14 May 2025 20:12:01 GMT

The first image shows the service territory pre-migration, and the second shows post-migration.

My workflow: Export Asset Package for migrated utility data, create new SDE, create feature dataset, create utility network, apply Asset Package to the created utility network. Correct me if I’m wrong.

After these steps, I discovered my service territory was empty after migration, which is causing the 'Enable Network Topology' tool to fail in the deployment stage (according to support)."

Re: enable utility network topology errors

RobertKrisher — Thu, 15 May 2025 13:24:26 GMT

@Olusoji23Here's the process you should be following

Instead of running Create Feature Dataset and Create Utility Network, you should use the Stage Utility Network tool in the UN Toolbox. You can find instructions for the migration and deployment process in this article/video series (if you already have a migration, you can ignore the data mapping/migration steps).

You should be relying on the service territory from the asset package during your staging/deployment process. My guess is

Re: enable utility network topology errors

Olusoji23 — Mon, 19 May 2025 14:43:28 GMT

@RobertKrisher I got these warnings after following the steps you just mentioned.
Maybe this still has to do with the empty service territory?
Can I just create a new service territory that has M and z enabled, then use the newly created service territory in the stage UN geoprocessing tool

Re: enable utility network topology errors

gpgisandsky — Fri, 16 May 2025 15:31:35 GMT

@RobertKrisher I tried to:

a) Copy and Paste UtilityNetwork with an enabled network topology in on Oracle 19c. This time, the topology works fine. Now, I can enable and disable the topology without issues. The ASSOCIATIONSTATUS field is populate correctly for associations. Howerver, when I try to edit a structure junction container and add a content feature (using Modify association in ArcGIS Pro) the following error apper:

b) Using the ASSETPACKAGE file geodb (without associations due to a known bug when applying the asset creation CSV of associations—see my post on ESRI Community), I attemped to deploy on Postgres15 (with stage un+apply asset untools 3.3.3.1 method).

After deployment, I imported the associations using the Import Association tool (Utility Network Tools). The tool completed successfully, but the ASSOCIATIONSTATUS value was not correctly populated for Content/Container associations—it remained set to "None".

However, if I use ArcGIS Pro with the UN feature service to edit a structure junction container via Modify Association, and then add a content feature, the association is applied correctly, and the ASSOCIATIONSTATUS is updated appropriately.

c) Using the same file geodatabase, I tried again on Postgres 15. This time, I used Copy & Paste to migrate the Utility Network. In this case, the ASSOCIATIONSTATUS values were correctly populated. Also, editing a structure junction container using Modify Association in ArcGIS Pro and adding content updated the ASSOCIATIONSTATUS as expected.

So the un solution work fine only in case C) but I need to work on Oracle (case A). What might be causing "Edit operation failed" issue?

Re: enable utility network topology errors

RobertKrisher — Fri, 16 May 2025 18:15:02 GMT

I recommend you continue to work the case through support, there is something very unusual happening with your data that I don't think we're going to be able to work through in the comments section here.

Re: enable utility network topology errors

HusseinNasser2 — Fri, 16 May 2025 20:40:55 GMT

The error "The requested operation is unsupported by instance db" often indicates that the geodatabase the UN is loaded on is not upgraded where some stored procedures maybe required by the application and they are not there. That explains why you are getting it on both enable and applyEdits.

Can you try running upgrade geodatabase from your current Pro?

Before you do that, take a screenshot of the current geodatabase version, I want to know what geodatabase version you are on because it is been years since I saw this error. You can find out by logging in as sde user and go to the properties. Expand Geodatabase version, upgrade status.

Then run upgrade geodatabase gp tool when you are ready.

If it works after that, will do some work to improve the doc.

Re: enable utility network topology errors

gpgisandsky — Mon, 19 May 2025 08:10:49 GMT

@HusseinNasser2

We are in the case A) of my previous post.

I did update geodatabase before starting to load Un data. The empty geodatabase has been created first time with 3.3.2 but I updated it using pro 3.3.5 and now it is:

Let'me know if I can verify other things.

Thank you

Re: enable utility network topology errors

RobertKrisher — Mon, 19 May 2025 14:14:13 GMT

You shouldn't make or have made any modifications to the definition of the service territory polygon class in your asset package. I recommend you restore the class to its original definition and try it again. This is also a different issue than what is being discussed in the rest of the thread, so its getting a little confusing trying to keep the two threads separate.