topic Re: Geoprocessor : Job 'xyz' does not exist or is inaccessible : with UpdateDelay < 1 in ArcGIS JavaScript Maps SDK Questions

Geoprocessor : Job 'xyz' does not exist or is inaccessible : with UpdateDelay < 10s

MichalGasparovic — Fri, 07 Oct 2011 06:51:10 GMT

Hi everyone.

I've ran into couple of troubles with geoprocessor and geoprocessing service, this one is about the geoprocessor returning the error message
"Error: Job 'jce700bde57e945088186368fc807c527' does not exist or is inaccessible." when using JS API.

The problem is, that the job actually gets executed, I can see the outputs in the \\somserver\arcgisserver\arcgisjobs\gpbuffer_gpserver\job..., just the geoprocessor, or possibly the service gets pinged for the status, and if it's in some process of generating results it is inaccessible and thus returning the error.

If I set the UpdateDelay to 20seconds, I get the results (though I have another sort of issue with that described in another post).

I can see the same behavior in ArcGIS Explorer, the job gets submitted, is executing, but fails to the end, though the results are there in the output folder.
I can see the same behavior in REST Services Directory for the gp service, if I click the "Check values" periodically I get similar error, that the job failed "Return Messages:
An unexpected error occurred processing the request."

The service is Asynchronous, supposed to return the results via result map service.

Any ideas on how to get this running properly without setting the UpdateDelay to 'safe enough' value, but not 'boring enough' for the client to wait??

Cheers and thanks for all your help

Re: Geoprocessor : Job 'xyz' does not exist or is inaccessible : with UpdateDelay < 1

MichalGasparovic — Tue, 11 Oct 2011 08:15:03 GMT

So we have the service up and running, but this still remains an issue. With default update delay or any delay less than 8-10 seconds it just returns the above mentioned error, though the gp generates the outputs on the server.

any ideas?

thank you.

Re: Geoprocessor : Job 'xyz' does not exist or is inaccessible : with UpdateDelay < 1

StephenThornton — Fri, 14 Sep 2012 09:26:23 GMT

Hi,

I recently had a similar issue. The job ran to completion but I was receiving errors when the GP Task checks the status.

In my case the website and GP task where hosted on the same machine. If you have the same setup check out my thread:

http://forums.arcgis.com/threads/66803-Problem-with-status-update-of-asyncronous-geoprocessing-task-at-3.1

Hope it helps.

Steve

Re: Geoprocessor : Job 'xyz' does not exist or is inaccessible : with UpdateDelay < 1

Anonymous User — Thu, 20 Sep 2012 05:26:00 GMT

Please contact Esri Support and speak with a Server analyst. Another thing to do is repost this question to the server general forum and explain how the model your using works. Because you are not getting results using your REST page or via Explorer, your not likely going to see results using JavaScript.

Re: Geoprocessor : Job 'xyz' does not exist or is inaccessible : with UpdateDelay < 1

JohnGravois — Mon, 04 Nov 2013 22:41:20 GMT

I know its been quite some time since this forum thread has been updated, but I was able to reproduce this error in house and logged the following software defect.

[#NIM096349 When a 10.0 asynchronous Geoprocessing Service and JavaScript application are hosted on the same machine, ArcGIS Server can return "job does not exist or is inaccessible". ]

until this issue is resolved, it looks like it will be necessary to use one of the following workarounds.

1. use a synchronous service instead of an asynchronous service
2. run the JavaScript application from a machine other than the ArcGIS Server machine
3. ensure that you are referencing the app url and url of gp services differently (ie. IP address, server name, fully qualified servername)
4. use a timeout to ensure that you aren't checking the status of a job while it is still executing.

this problem is not reproducible in 10.1 or 10.2. sorry for the inconvenience.