Error 160222 Tracing the network - The network feature does not have an associated network element

[lorenzoz]

Hello everyone,

I’m struggling with a persistent error while running a Trace in a Utility Network. Error 160222: https://pro.arcgis.com/en/pro-app/latest/tool-reference/tool-errors-and-warnings/160001-170000/tool-.... I see it's a rare error and there's not a single solution, so I provided a feedback and I hope this post can help.

I deployed the Utility Network using the Migrate To Utility Network tool with no initial errors. I’ve configured Tiers, Terminals, and Subnetworks, and assigned them to the appropriate devices. However, when I try to run a Trace, I consistently get the same error. I tried both Connected and Upstream/Downstream trace.

This is what I tried to solve the error:

I exported the Asset Package (with and without data) and redeployed it into a File Geodatabase (FGDB). The error persists even in a clean environment. I even tested with an empty deploy by creating and editing just a single line: same result.

The only clue I have is that, during a deployment via Asset Package to Geodatabase, I encountered an error stating "subnetwork field names cannot be nullable." Following this community thread, I deleted the problematic fields in the Asset Package and redeployed. The fields were recreated successfully, but the Trace error remains.

I feel like it's a schema inconsistency or a hidden data issue, but I'm running out of ideas since it happens even with a single feature. Has anyone encountered this specific behavior after a migration?

Any suggestions or insights would be greatly appreciated!

Thank you in advance,

Lorenzo

[RobertKrisher]

If you disable and re-enable the network topology, does that fix the error?

[lorenzoz]

It was the StartingPoint feature class. I deleted it and now it works!

[MikeMillerGIS · Accepted solution]

Could be related to the starting point layer being out of sync with the data.  In the projects home/default, delete the starting point and barrier classes.  Then re-add the starting point to the feature and give it a shot.

[lorenzoz]

This solved the problem! Thank you very much! I deleted the feature classes in the home gdb and now it works! Thanks a lot

L

[gis_KIWI4]

@lorenzoz - To troubleshoot this further, can you check the UN_Temp_tarting_Points layer in your Default Database. It should look something like this. 

Can you confirm if the FEATUREGLOBALID matches the device/element you have selected? 

[lorenzoz]

Deleting the Feature Class and re-adding it solved the problem!

[MikeMillerGIS]

Nice!  I have seen this and hoped it was the issue.  Essentially the information in the starting point layer is out of sync with the data.