topic Re: Publishing Network Analysis Service - ERROR 001487 in ArcGIS Enterprise Questions

Publishing Network Analysis Service - ERROR 001487

Fouad_Geoffrey — Tue, 20 Feb 2018 18:45:22 GMT

I am publishing a network analysis service as instructed here.

Tutorial: Publish a network analysis service—Documentation | ArcGIS Enterprise

Upon publishing, I get this error.

The server log shows this error.

I have tried many ways to publish the service. Registered database, registered folder, not registered folder. The final changes the error to 001369, with the following error logged on the server.

Any ideas would be greatly appreciated.

Thanks,

Geoff

Re: Publishing Network Analysis Service - ERROR 001487

BrianVan_Nostrand — Wed, 13 Mar 2019 17:23:32 GMT

Did you ever get this working?

Re: Publishing Network Analysis Service - ERROR 001487

Fouad_Geoffrey — Mon, 01 Apr 2019 20:15:11 GMT

This was a student project, and we did not resolve the matter before the end of semester. Another student may pick up the project again in the future, and we will update any progress on using a network analysis service here.

Please let us know if you ever make any progress on this problem.

Re: Publishing Network Analysis Service - ERROR 001487

BrianVan_Nostrand — Mon, 01 Apr 2019 22:01:26 GMT

Thanks for the reply. I'll say both to you and for future viewers of this thread, the issue we were having was a version clash between our server (10.3.1) and desktop (10.6) versions. I resolved it by installing desktop 10.3.1 on the server machine with the old server version and published from there. This is also not an issue that can be resolved by saving a copy down from the current desktop version. ESRI has not really documented this issue and couldn't solve it on my support call. This thread is the end of the line

Re: Publishing Network Analysis Service - ERROR 001487

Fouad_Geoffrey — Tue, 02 Apr 2019 18:13:02 GMT

Very helpful. Thank you, Brian. Original issue occurred now over a year ago, but I seem to recall difference in versions between server and desktop. I will note this for the future, and mark your answer as correct since you've likely identified the source of the error.