topic Re: Migrate to utility network and Apply error resolution in ArcGIS Utility Network Questions

Migrate to utility network and Apply error resolution

Davis_Dad23 — Tue, 25 Mar 2025 07:13:33 GMT

Hello

I have met issue with new migration tools.
I have successfully migrated source database to UN model and i have also used analyze network data tool to produce all errors generated successfully.

But the issue i have now, is on the apply error resolution tool that uses the error resolution table that was generated from the analyze network data if i not wrong.

I am running this apply error resolution tool but it is running successfully but the folder still is empty neither having no any change on the UN model migrated with errors.

What is the best way to use this tool and what do you think that i might be missing to run the apply error resolution successfully.

Please help me to find out how the best way to use this tools successfully and resolve the generated errors
@RobertKrisher

Re: Migrate to utility network and Apply error resolution

MikeMillerGIS — Tue, 25 Mar 2025 11:03:53 GMT

Could you share your error resolution table with us? We would like to see what resolutions are provided. Are there any messages in the GP messages? Are log files created in the output folder?

Re: Migrate to utility network and Apply error resolution

RobertKrisher — Tue, 25 Mar 2025 14:02:55 GMT

To resolve errors, you must review the Analysis Results database and provide resolutions to each error you want to fix. Applying default resolutions will only solve some of the errors.
Read these articles for more instructions on how to use the tools:

If you are still unable to resolve errors after following the process outlined in those articles, reach out again.

Re: Migrate to utility network and Apply error resolution

samshrma998 — Mon, 01 Dec 2025 09:39:56 GMT

I have been encountering same issue. For me I am getting a warning message ang log file saying "an edit operation is required".

I am running the tool to correct stacked points and have error resolution defined as "Delete all but first".

Surprisingly , the tool work as expected on AGP 3.5.1 but gives warning in AGP 3.5.5 (attached screenshot).

Further, when I add and use the standalone toolbox which I have been using in past during AGP 3.3, it works well in AGP 3.5.5 also.

Is there any additional things to consider while using this tool on 3.5.5.

Re: Migrate to utility network and Apply error resolution

RobertKrisher — Tue, 02 Dec 2025 01:14:52 GMT

Please log an issue with support for this to get a bug created so you can be notified when we release the patch that correct it.

Re: Migrate to utility network and Apply error resolution

streamside — Fri, 16 Jan 2026 19:07:59 GMT

Has the issue been reported. I am having similar issues. The tool ran a couple time in 3.5 with 'Create' action on missing junctions. Upgrade to 3.6 and the tools says it run successfully but there is no output....no logs, no table showing Inserts Updates and Deletes.

Re: Migrate to utility network and Apply error resolution

RobertKrisher — Sat, 17 Jan 2026 14:52:06 GMT

There is currently a known issue where the tool can fail to run and produce an error, but there aren't any issues I'm aware of where the tool silently fails. Please log an issue with support so we can understand what is happening.

Re: Migrate to utility network and Apply error resolution

samshrma998 — Sat, 17 Jan 2026 16:10:52 GMT

*I had logged support case and got a BUG logged for this. Though bug is not
made public yet.*

*BUG-000181823: In ArcGIS Pro, 'Apply Error Resolution' tool fails to apply
edits to the features, but executes with a warning "WARNING 004202: Some
edits failed*

Re: Migrate to utility network and Apply error resolution

RobertKrisher — Sun, 18 Jan 2026 18:38:02 GMT

@samshrma998 @streamside . If you receive a warning when applying the edits, then it's a known issue (BUG-000181823). If the tool doesn't report any warnings or errors, but no resolutions are applied, then that is not something we are aware of, and you will want to log an issue, so support can investigate what is happening.