Network Topology Error

[Joshua_Moreno]

I am getting an error when trying to update subnetwork, it is saying to enable topology. As I go to enable topology, it returns that the topology is already existing. I've disabled and reenabled it against the UN service but in my network properties, it is showing Is Enabled still as "False". Anyone know what this issue is?

[RobertKrisher]

@Joshua_MorenoAre you doing this in a local geodatabase or an enterprise geodatabase? Can you show a screenshot of enabling the network topology succeeding (with the parameters) and update subnetwork failing? 

If you're enabling the network topology against an enterprise service, its possible you're doing this in a version other than default. Its also possible that your enable network topology GP tool is set to "only generate errors", which will create topology errors but not enable the network topology for tracing.

[Joshua_Moreno]

Hi Robert, I was doing this in an enterprise geodatabase. The same thing happened again yesterday but I followed the steps above for fixing posted by Venkat. I believe what may be happening is that I wasn't logged into portal within my Pro session so when trying to post edits or update topology/subnetwork, it provided an error that made the geodatabase/service out of sync thus turning off the network topology.

I did ensure the only generate errors param was disabled. Do you think what I had mentioned above might be the cause? I can try to replicate again and see if this is the issue. I work in a VM so my login isn't persistent and I always forget to login to the correct portal/account.

Also, side note. For editing, is it okay to edit via the portal web map within arcgis pro (adding the published web map as a map in pro) or do you recommend a separate map that consumes the published service?

[RobertKrisher · Accepted solution]

Disabling and re-enabling the network topology on a regular basis is going to have some long-term performance implications, and you shouldn't need to do that. I'd make sure that going forward, you're just always logged into portal, and if you run into any strange behavior, make sure you're logged into the right portal/service, restart Pro, and hopefully that fixes it.

If you find the experience of editing using the web map from Portal acceptable, then that's fine. There's a lot more you can do with a desktop map in ArcGIS Pro than you can do with a Web Map in Map Viewer, but you aren't relying on any of those capabilities so you're fine (display filters, layers with multiple definition queries, etc).