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?
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.
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?
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.
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.
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.
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.
