topic Re: Problem with status update of asyncronous geoprocessing task at 3.1 in ArcGIS JavaScript Maps SDK Questions

Problem with status update of asyncronous geoprocessing task at 3.1

StephenThornton — Thu, 13 Sep 2012 10:10:42 GMT

Hi All,

I'm having a problem updating from 2.8 API to 3.1.

I have a geoprocessing task working great at 2.8 and I can see the status of the task while it is running.

However when I use the 3.1 API the callbacks to check the status fail after the first status callback.

The error I see in Firebug is 'Job abc123 is does not exist or is inaccessible' (See attached for screenshot). However the job does exist and actually runs
to completion as my expected output file is generated correctly.

Has anybody else come across this issue? Any workarounds?

Any help would be greatly appreciated.

Thanks,

Steve

Re: Problem with status update of asyncronous geoprocessing task at 3.1

StephenThornton — Fri, 14 Sep 2012 09:19:59 GMT

Ok, so both the website and the GP Task are hosted on the same machine.

I access the website and GP task using the same domain i.e.

Website
http://mydomain/mysite/index.html

GP Task
http://mydomain/ArcGIS/rest/services/ExportPDF/GPServer/ExportToPDF

This setup worked fine at 2.8 and below. To make it work a 3.x I accessed the GP Task using the machine name i.e:

http://servername/ArcGIS/rest/services/ExportPDF/GPServer/ExportToPDF

This fixed the issue however I'm not sure why. Something must have changed in API 3.x. Can anybody shed some light on this?

Thanks,

Steve

Re: Problem with status update of asyncronous geoprocessing task at 3.1

LauraWilson — Tue, 05 Feb 2013 12:53:26 GMT

We are experiencing the same issue. We are using the public facing IP, but then it doesn't work for those inside the firewall. Did you get any feedback from ESRI?

Re: Problem with status update of asyncronous geoprocessing task at 3.1

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

see my notes in this thread for more info.