Hello, I am attempting to update an existing Network Dataset with added Travel Attributes > Cost, but every time I try to make a new Cost and save it by hitting the OK. I am getting the error:
It looks like it will save if I refresh and open it again, but then if I attempt to rebuild the Network to implement the changes into the ND, it will get stuck on running:
Any ideas on what to look for?
Solved! Go to Solution.
I resolve the issue myself, so I don't have the failing dataset anymore.
I used the "create template from ND" tool, then deleted the ND. I then used the "create ND from template" tool. This resolved the issue. Annoying as this was at least I didn't have to recreate the ND from scratch.
If it helps, I'm using ArcGIS Server 11.3 and ArcGIS Pro 3.4.3
Hmm, that's not a very specific error!
What version of Pro are you using?
Does it matter how you configure the new cost attribute? If you do something really simple, does it still have the problem?
This is 3.5.0 ArcPro.
It did that with every edit. I ended up deleting the _ND and starting over again.
Interesting. It sounds like something was corrupted in the network, so starting over is a good idea. If you still have a copy of the bad network around, I'd be happy to take a look at it. We can try to see if we can improve the error messaging in case you or someone else runs into this again.
Has there been any news on this? I'm having exactly the same problem.
No updates from the Esri side. The other user hasn't shared the network with us, so there's not much we can do. Can you share your network? Feel free to private message me with a sharing link or to request that I provide one for you.
I resolve the issue myself, so I don't have the failing dataset anymore.
I used the "create template from ND" tool, then deleted the ND. I then used the "create ND from template" tool. This resolved the issue. Annoying as this was at least I didn't have to recreate the ND from scratch.
If it helps, I'm using ArcGIS Server 11.3 and ArcGIS Pro 3.4.3
It sounds like the network somehow got corrupted. If you see it again, please save a copy of the bad network and share it with us. Maybe we can figure out what caused it to get into that state and fix it!
Apologies for leaving this, I too followed the same workflow that @MarcDyke2 did to get around the issue.