topic ERROR 160021: Topology errors and dirty areas/objects may not be directly modified (sewer expanded) in ArcGIS Utility Network Questions

ERROR 160021: Topology errors and dirty areas/objects may not be directly modified (sewer expanded)

MarianoDiNapoli — Thu, 19 Jun 2025 09:31:48 GMT

Hi everyone,

after successfully creating the Utility Network, we tried adding various rules to resolve error code 8. However, when we ran the Enable Topology tool again, we encountered ERROR 160021.

Do you have any suggestions on how to fix this error and understand why it is occurring?

Thanks in advance,

Mariano

Re: ERROR 160021: Topology errors and dirty areas/objects may not be directly modified (sewer expanded)

RobertKrisher — Thu, 19 Jun 2025 12:35:12 GMT

Were you able to successfully enable your topology before? Also, what version of Pro and Enterprise are you using and is this a file, mobile, or enterprise geodatabase?

Re: ERROR 160021: Topology errors and dirty areas/objects may not be directly modified (sewer expanded)

MarianoDiNapoli — Thu, 19 Jun 2025 12:45:12 GMT

Hi Robert,
Thanks for your support.

I tried to enable Network Topology by selecting the "Only generate error" option, and it worked as expected. Afterwards, I added some rules to address the code 8 error, but when I tried again, enabling Network Topology stopped working altogether.

Best regards,
Mariano

Re: ERROR 160021: Topology errors and dirty areas/objects may not be directly modified (sewer expanded)

RobertKrisher — Fri, 20 Jun 2025 13:26:40 GMT

You should open a case with support about this, as this is not the expected behavior.

Are you still able to Enable Network Topology to generate errors? Or do you only receive this error when you Enable Network Topology with the generate errors option off?

Also, please answer the question about what type of database you are using and what version of Pro you are using.

Re: ERROR 160021: Topology errors and dirty areas/objects may not be directly modified (sewer expanded)

MarianoDiNapoli — Fri, 20 Jun 2025 15:25:59 GMT

Hi Robert,
I'll reply right away: I’m using a file geodatabase and Pro version 3.5.1.
Also, I’ve just checked that this abnormal behavior occurs when the “only generate errors” option is enabled. If I disable this option, the tool works correctly.
As I mentioned in my previous message, before adding the rules, the tool worked correctly even with this option enabled.

Thank you,
Mariano

Re: ERROR 160021: Topology errors and dirty areas/objects may not be directly modified (sewer expanded)

RobertKrisher — Mon, 23 Jun 2025 16:06:30 GMT

Please log a case with support. As a workaround, copy your utility network dataset to a mobile geodatabase and you should be able to enable it to generate errors.

Re: ERROR 160021: Topology errors and dirty areas/objects may not be directly modified (sewer expanded)

egcon27 — Thu, 14 Aug 2025 19:42:00 GMT

@RobertKrisherI'm having the same issue. I'm following the workflow from "Running a Successful Utility Network Prototype" (https://mediaspace.esri.com/media/t/1_2o2s2lev/246131802 enable network topology, summarize errors, analyze, correct one error, then repeat. Maybe I'm doing this wrong. Should I edit directly in the utility network database or the asset package?

I've tried fixing errors in the utility network and rerunning "Enable Network Topology" with "Generate Error" checked, but I get ERROR 160021: Topology errors and dirty areas/objects may not be directly modified. It works when I uncheck "only generate errors," but I still have more errors to fix. I'm disabling network topology to keep fixing errors. Is there a better workflow? Or should I switch to a mobile SQLite geodatabase?

Using Pro 3.5.1 and FGDB.

Re: ERROR 160021: Topology errors and dirty areas/objects may not be directly modified (sewer expanded)

RobertKrisher — Fri, 15 Aug 2025 16:32:16 GMT

@egcon27 Please open a case with support. This is a known issue (workaround provided above). The fix for this should be out in the next patch for ArcGIS Pro 3.5.