Hello,
I have created a test Network Dataset using in-house Street data maintained by our GIS dept, and used the Publish Routing Utility tool to publish and author it onto our server.
I am getting a strange error when attempting to simply use the 'Directions' tool, where inside Pro using the Routing Service that was published by aforementioned Network Dataset will properly produce a Route, where in a blank test webmap, the routing service may or may not produce a result. Sometimes it will produce a route, and other times it only states Warning, Unable to route to between stops.
IE: ArcPro Imported stops from Address
ArcPro Routing Service | Enterprise Map Routing Service | Enterprise Map Route Service other |
Stop 1: 69290 xxxxxxx | Stop 1: 69290 xxxxxxx | Stop 1: 68609 xxxxxx |
Stop 2: 68700 xxxxxxx | Stop 2: 68700 xxxxxxx | Stop 2: 68700 xxxxxxx |
|
|
I have a geocoder that works, everything works in ArcPro connected to the same services the MapViewer Map is using, any help is appreciated.
Attached is a quick 10sec video showing in a WebApp the above error (minus the ArcPro side)
Solved! Go to Solution.
Hey Gregory, I worked with Alex on getting it resolved and he is using the publish routing services utility tool, https://enterprise.arcgis.com/en/server/10.9/develop/windows/publishing-routing-services.htm, it is the .bat utility you mentioned.
Did you get the network traffic and see what is the service response? Although directions widget show the same error, the underlying error from service could be different.
Hi Max, thank you for reaching out.
I ended up rolling back to the original published network analysis layer and it worked again.
So I wont be able to capture the network traffic.
The reason I was re-publishing was because we added to our road network recently.
Can you confirm that the Geocoder must be updated with the same new locations as well?
Are you able to advise about using the routing service utility as I have not had success with that.
Thanks
Greg
Hi Max,
Just to advise that I recreated the network again and got the same error. Following your advice I pulled the network traffic that provided this message:
{"error":{"code":400,"extendedCode":-2147200984,"message":"Unable to complete operation.","details":["The network dataset does not support driving directions."]}}
Our road network does not need driving directions (meaning this was not an option I particularly wanted to use) so I used another field for the base name, rebuilt and republished and it now works! Thank you!
For anyone with a similar issue this guide was helpful
https://pro.arcgis.com/en/pro-app/2.8/help/analysis/networks/setting-directions.htm
Hey Greg,
Great to hear that it works for you after setting up directions. To answer your previous question, yeah I would advise to use publish routing services utility since it publish the full set of service and register the utility services. And it also detects these kind of issues with network dataset before publish. It is especially helpful if your intention is to publish routing services and then use in one of Esri's client apps (such as directions widget and ArcGIS Pro).
For your question regarding Geocoder, I am asking around and will let you know when I have an answer.
Thanks,
Max
Hey Greg,
From my understanding of your question regarding Geocoder, you essentially added new streets to your streets data, and is wondering whether you need to update your geocoding service, is this correct?
If this is what you are asking, I think you need to create a new locator and then overwrite the existing geocoding service with the new locator.
Hi Max,
Thank you for letting me know. Yes we have added new roads and wondered if the geocoder had to be updated with location in this new area as well. I will create a new locator.
Thank you!