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-errors-and-warnings-160201-160225-160222.htm. 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
