I have a few geoprocessing services published onto a production ArcGIS server but after a series of Windows 2012R2 and ArcGIS server updates, the services stopped function.

When I submit a job, these are the messages I would get:

  • esriJobMessageTypeInformative: Submitted.
  • esriJobMessageTypeInformative: Executing...
  • esriJobMessageTypeError:
  • esriJobMessageTypeError: Failed.

To test and see if there is something wrong with the server, I published an empty python script. When I submit a job to that service, I get the same set of message. If it had function normally, there wouldn't be any "esriJobMessageTypeError". Its as if the code did not execute at all, stopped at the first line.

Does anyone have similar problems after updates and any fixes?

Attempting to built my service from scratch step by step and I think I have located where the problem started.

Starting from the beginning,

  1. Published an empty python script to a test python service and confirmed that it is running normally.
  2. Update the script with some imports. Service is executing normally.
  3. Update the service with one input parameter. The service failed with the above 4 lines of esriJobMessag. However server log did not record anything

Have test the empty script with a single parameter on another ArcGIS server and the server execute the service with no problem.

So what should I do next? Anything before completely re-install the problem ArcGIS server?

  • The message level for this service is "Info" – swap0 Jun 15 '18 at 14:05
  • Try this patch: support.esri.com/en/download/7576 ? Although, you wouldnt even be able to publish a new GP service if this was indeed your problem. – KHibma Jun 15 '18 at 23:27
  • 2
    Debugging service failures usually requires a great deal of messaging code within the service code, and changing the Server logging level to support Verbose logging. We do not have a fraction of the information needed to help answer the question as written. – Vince Jun 16 '18 at 12:12
  • I really don't have any other information. I literally published an empty python script and still got those exact 4 lines of messages. WIll try the patch and update on what happened. – swap0 Jun 17 '18 at 1:45
  • Hi KHibma. The patch did not work. There is just no information. I check the log in the management portal and all it said in Verbose mode is was "SEVERE Jun 18, 2018, 8:50:43 AM Error executing tool. <Service Name> Job ID: j25facd72254643cd9e9e5e320cbbdd87 <Service Path>". Where else can I get more detailed debugging information? – swap0 Jun 18 '18 at 11:55

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.