Enable Network Topology fails with "ONLY_ERRORS" at 2.3

[MarkCederholm]

Starting at Pro 2.3, EnableNetworkTopology_un fails when I use the "ONLY_ERRORS" option:

ERROR 999999: Something unexpected caused the tool to fail. Contact Esri Technical Support (http://esriurl.com/support) to Report a Bug, and refer to the error help for potential solutions or workarounds.
Unexpected operation

It works just fine without the "ONLY_ERRORS" option.  Then when I disable topology and unregister as versioned, I run into the same problem again.

Has anyone else seen this?

[MarkCederholm]

FYI, I'm also seeing the issue with the Naperville dataset.

[PaulLeBlanc1 · Accepted solution]

We've addressed this issue and it's currently marked for a 2.3.x release.

[MarkCederholm]

It seems to be fixed at 2.3.2.

[LorenMueller]

@Paul LeBlanc - I am having the same issue. Does the newest untools package v2.3.1 help with this? Is that package only the Stage and Asset Package tools?

[PaulLeBlanc1]

untools will not fix this. You'll need an ArcGIS Pro patch release.

[SamiSnunu]

I've Just upgraded to Pro 2.3.1, and re-ran the Enable Network Topology, (with option Only generate errors checked). still got the same generic Error 999999.

also tried Register As Versioned, and run without the Only generate error option being checked. the tool runs forever at 2% progress without saving any dirty areas errors in the enterprise database.

[MarkCederholm]

I've confirmed I still see the bug at 2.3.1 -- I tried rebuilding my Python environment as well, with no difference.

[SamiSnunu]

Also if running the Enable Network Topology using ENABLE_TOPO, it failed due to (ERROR 001992: Dataset must be versioned.) even if the dataset is already been versioned. ArcPro 2.3.1, untools 2.3.1

[PaulLeBlanc1]

Is your database connection (SDE file) connect via branch or traditional?