Currently we are building large network datasets using a quite complex template in ArcGIS Server 10.9.1:
We created a custom geoprocessing tool, include a XML with function evaluators (VBScript as well as Python) and publish this via ArcGIS Pro to our ArcGIS Server 10.9.1
When we start this process everything works just fine:
create network from template, build network (with some warnings, but nothing fancy) and we receive a nice feature collection with the needed network dataset.
Unfortunately this NDS is just bad: I cannot solve the route layer on it and it barely works, when I turn off all the restrictions. But even then it gives me really strange routes.
But if I take the same gdb that holds this NDS and I open this in ArcGIS Pro 2.9, delete the NDS and recreate it with the same template and rebuild it, everything works just like expected.
Furthermore I've tested to alter just one restriction on the original server-side created NDS which forced a rebuild as dirty areas were created, it was perfect after building it using ArcGIS Pro on desktop.
We have no idea, where this behaviour is coming from.
What we have tested:
- switched from arcpy.nax.buildNetwork on server to the good old arcpy.na.buildNetwork
- disabled ArcMAP legacy support
- checked the python executable on server (yes it was 3.9.11)
- checked the original gdb as it is returned from the server side as a compressed format and we would like to make sure that the compression isn't causing the problem.
We are a. bit stucked now.