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

Validate Network Topology Fails ArcGIS Pro 3.7 for Water UN, Sewer UN

DavidColey

Hello - The Validate Network Topology GP Tool fails to validate network topology at ArcGIS Pro version 3.7. I ran the tool as part of our ValidateTopology>Update IsConnected> Update Subnetworks python gp tool nightly workflow but the tool cannot get past the validate network step.

The tool errors out with a 'cannot validate topology because another session is currently running error'.

The Enterprise is at 12.0. The UN build is UN7

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

Accepted answers

RobertKrisher

The plan is to include that issue in the next ArcGIS Pro 3.7 pro patch, which at this point is ArcGIS Pro 3.7.2. Once the patch has been released the page will be updated to indicate which patch it was included in. This issue was specific to 3.7, so it does not need to be included in any earlier patches.

All comments

GIS_kiwi4

@DavidColey - I am guessing your GP tool is calling Validate Topology operation in quick succession.
Also in this chain - ValidateTopology>Update IsConnected> Update Subnetworks you can removed the "Update IsConnected" operation. Update Subnetworks will modify the IsConnected Flag.

Any chance you can share the logs or some screenshots?

RobertKrisher

@DavidColey I'd start by logging a case with support since it may be a bug. If no one else is validating default on the server then you shouldn't see this error.

How are you calling validate? Does validating manually via ArcGIS Pro or a geoprocessing tool work? Does this error happen immediately, or does it take a little while? Presumably this is in default, or is this in a named verion?

rlyding

@RobertKrisher I was working along with @DavidColey as we were trying to troubleshoot the validate error. To answer your questions. The validate is being called from a python script using the database owner account on the DEFAULT version. We tried to run the validate from the gp tool in ArcPro 3.7 and it fails immediately with the same error. We also tried with another user account in 3.7 with the gp tool and got the same error. We tested in ArcPro 3.6 and validate gp tool runs with no error. A few other things we tried we had all users exit the system and reconcile/post and delete all versions and started and stopped the services. We also tried disabling and re-enabling topology and even tried a service overwrite with no luck. Thanks for the help on this.

RobertKrisher

Definitely log a case with support, if there's aren't any other sessions validating default you shouldn't be seeing that error. It is interesting that you get the error with an ArcGIS Pro 3.7 client, but not an ArcGIS Pro 3.6 client.

DavidColey

Thanks for the replies @rlyding @RobertKrisher @gis_KIWI4 - We may have narrowed this down some. I ran a test on a disconnected Service Connection sewer device in our Sewer UN. I set up a version off the sde.Default, dropped the point disconnected to from its service line to create a dirty area and then used the Validate topology toolbar GUI tool.

The validate was successful.

Now - because I am our org admin I set up an arcpy clone so that I am able to take advantage of adding in packages and being able to update the arcgis.

I switched back to the default arcpy environment, repeated the edit steps above except this time I ran the validate topology from the toolbox tool.

The validate was again successful.

Long story short, I may have a bad clone. Typically when I upgrade pro I always delete the clone, perform the update, re-clone the environment to the default clone location then run the conda update -c esri arcgis command.

However, when I completed the conda update and searched for the untools package, it was not present for 3.7. Now it is:

Last week, I did not get these options when updating the clone for conda install -c esri untools --insecure

The following packages will be downloaded:

    package                    |            build
    ---------------------------|-----------------
    certifi-2026.5.20          | py313haa95532_0         131 KB
    untools-3.7.0              |          py313_0         867 KB esri
    ------------------------------------------------------------

So we'll see.

RobertKrisher

A few more clarifying questions;

1. You said: "The validate is being called from a python script using the database owner account on the DEFAULT version". You're running the Validate Network Topology tool against a service right? So presumably you're running it as the Portal Dataset Owner account (DB Owner account implies you're running it using a SDE connection).

2. Are you using something in the UN Tools or UDMS in your validation script? Or were you just explaining why you had a cloned Conda environment, which appears to be the cause of the issue.

DavidColey

Well I'm at a loss. The tool simply will not run from the python IDLE, whether the arcpy environment is set to the default or to the clone.

All of my other hundreds of scripts run just fine from the IDLE, including ones that use the:

import arcpy
arcpy.SignInToPortal(https://myorg.net/portal, 'username', 'password')
L950SewerUN_Utility_Network = "https://myorg.net/agsfed/rest/services/CollectorServices/Sewer_Utility_Network/FeatureServer/950"
arcpy.un.ValidateNetworkTopology(in_utility_network=L950SewerUN_Utility_Network, extent='474063.442811626 1070897.65903111 474156.933218947 1070963.47578807')

so who knows. Everytime I try this run from the idle as the unowner user it comes back as

ERROR 004403: Unable to validate network topology because another session is currently validating.Failed to execute (ValidateNetworkTopology).

RobertKrisher

@DavidColey Ok, so now I have two more questions: does it run from inside ArcGIS Pro and does it run in the script you use for your nightly task?

DavidColey

Yes @RobertKrisher the tool did run successfully inside ArcGIS Pro using the toolbox tool from both the default arcpy environment and then from the cloned environment (after I ran the conda install -c esri untools --insecure).

The validate portion of the script runs nightly from a Windows task where it calls the python.exe from the command and uses the unc path to the full script as the task argument - our standard Windows Task Scheduler procedures we've been doing for years.

Regardless, when I try to run my UNMaintenance.arcpy script from the python IDLE window, I get the error.

All of my other scripts that use arcpy like FeatureSharing run this way and are just fine.

@rlyding

RobertKrisher

@DavidColey if it works in Pro and it works standalone then that's what matters from a bug perspective. I'm not familiar with how to configure IDLE and what could be causing issues there.

DavidColey

Yes thanks @RobertKrisher and that's what I told @rlyding - IDLE is simply when you right-click an *.py file in windows and select 'Edit with IDLE (ArcGIS Pro):

There is no configuration of that environment, other than like setting indents vs spaces, etc.

Could be something with dot10 is messing it up for that tool.

DavidColey

Hi @RobertKrisher - in doing a lot more troubleshooting on this it does appear that the gp tool for validate un topology will now only run against a named user version... It simply will not run against the sde.DEFUALT version as the unowner portal account when connecting to the Utility Network service in Pro 3.7, or when trying to connect to portal via a python workflow, whether in the instant window, a model, or a notebook.

Thanks

@rlyding

RobertKrisher

please open a case with support

DavidColey

sometime next week perhaps after we upgrade to 12.1, thanks.

DavidColey

@RobertKrisher - we have submitted a premium support case:

Support Case Number #04201129

Thanks

DavidColey

Here are our findings that we have submitted to Support Case Number #04201129:

We have completed all requested actions support listed and we are still getting the error in ArcGIS Pro 3.7 when trying to validate using the Validate Network Topology GP tool on the DEFAULT version. ERROR 004403: Unable to validate network topology because another session is currently validating.

All versions were reconciled/posted and deleted, and all users exited the system to remove all locks. GDBs were updated and are now at version 12.1, the Prune Branch History tool was run on all datasets, all indexes were rebuilt, disable/enable topology was done, services overwritten, and verified no other locks were present on the database.

After the above we tested in Pro 3.6 and the Validate Network Topology GP tool works with no errors on the DEFAULT version. Pro 3.7 still gives the error and fails. It would seem this is a bug related to Pro 3.7.

This was a lot of work.

At this time, we now need support to replicate and confirm.

GISUser1619_Nguyen

HI @DavidColey Do you have solution for this issue? Now, I got same Error when running Validate Network Topology GP tool with 12.1 and pro 3.7

Capture.JPG

DavidColey

No @GISUser1619_Nguyen - I do not. It is a confirmed bug for the ArcGIS Utility Network at Pro 3.7:

https://support.esri.com/en-us/bug/the-validate-geoprocessing-tool-fails-on-default-but-wo-bug-000185836https://my.esri.com/#/support/bugs/bugs?bugNumber=BUG-000185836

We were hoping for a fix at 3.7.1 but no. Not sure when 3.8 is scheduled for release.

GISUser1619_Nguyen

Thank you @DavidColey for your sharing information, Now I work in UN project and this issue also make trouble with customer data when they reconcile and post a million feature. We also buy premium support from Esri so I will try to ask if possible fix in 3.7 patch. 3.8 too late.

RobertKrisher

DavidSDouglas

I have also logged this error (validate returning this error from the nightly Python script with 3.7.0, 12.1 and UN 7). The case was closed on Fri. 17th July, stating that the issue will be addressed in 3.8. So I'm glad to hear it will be fixed earlier, in 3.7.2. For us, being unable to do nightly batch validation is a showstopper. That was also the case last year when we were upgrading to 3.5.4 and 11.5 and could not validate. ESRI really needs to do more testing of UtilityNetworks when upgrading.

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.