Recently performed an upgrade from ArcGIS Server 10.3.1 to 10.4.1. Everything seemed fine but two geoprocessing services refused to start and were throwing an error of;
GPServer: java.rmi.UnmarshalException: Error unmarshaling return header; nested exception is: java.net.SocketException: Connection reset
Turns out (according to this link) that the registry key under HKEY_LOCAL_MACHINE\SOFTWARE\Python\PythonCore\2.7 might be empty. Checked the registry and indeed it was empty.
Turns out uninstalling the background geoprocessing for ArcGIS Desktop shouldnt be done after upgrading ArcGIS Server (forgot that it was installed!).
Luckily I could recover the registry keys from another environment and all was well.
With the move to virtualisation and especially cloud its very easy to change the specification of your ArcGIS Server – increase cores, memory etc. While updating some tiles on a cache service the other day I noticed the number of caching service instances was set to 3 which was odd considering the AWS instance had 8 cores (originally it was 2 cores). Continue Reading
After what seems like ages (over a year in fact) the Esri Professional Services team have released an update to System Designer. There are a bunch of fixes, updated hardware (including Amazon M4 series) and finally we have models for Portal (10.2 though).
Go get it; https://www.arcgis.com/home/item.html?id=8ff490eef2794f428bde25b561226bda
What to do when your ArcGIS Server service refuses to start?
Firstly don’t panic! There are a couple of things to check before you panic; Continue Reading
We’ve all seen it – Service failed to start. I recently had a Printing Tools service on 10.3.1 that refused to start no matter what.
I noticed the other day that a feature service I was using on AGOL was referring to the sharing proxy page (i.e. http://www.arcgis.com/sharing/proxy?http://serviceurl) and failing because the server was an internal server not exposed to the internet.
It turns out that its related to CORS so make sure your browser supports CORS and that you can see the access control headers in the response from your web server.