topic Error modifying terminal configuration or terminal paths in ArcGIS Utility Network Questions

Error modifying terminal configuration or terminal paths

Isaac_King — Tue, 20 Feb 2024 00:09:30 GMT

Working in a gas UN fGDB using ArcGIS Pro 3.0 with topology enabled.

I have subnetwork controllers defined and configured, terminal configurations defined and set, and I'm generating duplicate rule errors at by subnetwork controller locations. When I attempt to modify terminal paths or connections to remediate the error, Pro is consistently giving me the following error:

"No asset groups and asset types that support terminal configuration paths were found in the selection."

I have recreated the UN and reapplied the asset package a few times now trying to be sure all configurations are in order, but can't shake this error.

What am I missing?

Re: Error modifying terminal configuration or terminal paths

Isaac_King — Fri, 23 Feb 2024 14:51:24 GMT

@MikeMillerGIS @RobertKrisher any thoughts on this? Pro 3.0 gremlin perhaps?

Re: Error modifying terminal configuration or terminal paths

RobertKrisher — Fri, 23 Feb 2024 14:57:55 GMT

@Isaac_King If this is a converted dataset, there may be other errors at that location preventing the tool from allowing you to connect the features. Try manually creating the junction and edge you have a rule for and see if it works.

If this doesn't work, then there may be something with how you have your map configured (selectability, duplicate layers, etc) that is interfering with the tool. Add the utility network to a brand-new map and try again.

If this still doesn't work, log a case with support. While there's no reason why this shouldn't work with ArcGIS Pro 3.0, I would recommend you stick to network management releases if possible. That way, you can apply patches that will include bug fixes for the utility network.

Re: Error modifying terminal configuration or terminal paths

Isaac_King — Fri, 23 Feb 2024 17:07:54 GMT

Thanks, @RobertKrisher. I created a new map and attempted to configure with migrated and newly created features and I'm still encountering the issue. We'll get a ticket submitted.

And believe me, we'll be on Pro 3.2 as soon as we can on this project!