Geoprocessing Package Failing

[ShaunWeston]

I've setup a geoprocessing package, which is a python script that exports an MXD to a PDF and finding that it crashes everytime with the following message:


{"error":{"code":500,"details":[],"message":"Unhandled Exception of unknown type in HandleHttpRequest: Worker process 'exportmap2_host' exited while attempting to service request (attempt 1 of 1): endpoint='GPServer' headers={} params={f=html, operation=execute, operationInput={  }, requestProperties={}} res='tasks/Test' post=0 Crash dump path=C:\\Users\\SWESTO~1.SPL\\AppData\\Local\\Temp\\ArcGISRuntimeErrorReports\\arcgisruntime_1.0.0.3057_service_20120611_001521.dmp"}}

The dump file then states:"The Thread tried to read from or write to a virtual address for which it does not have appropriate access"

When I use a gp package that is doing something like a buffer or an intersect, it works fine, however when running a script that creates a file it crashes?

I've tried debugging it using Process Monitor and can see RuntimeLocalServer accessing the file, but not exporting out the PDF. I understand this is Pre-release, so hoping it might run better when the final release is available.

[ShaunWeston]

Does anyone know anything about this????

I've been doing some testing around this and it seems to be a memory issue? When I do a simple write to a text file using a python process, it works fine, but using the Arcpy mapping module to export to PDF, crashes everytime?

[ShaunWeston]

I'm finding this issue is still occurring in the final release of the SDK...

[ShaunWeston]

It seems to be just arcpy.mapping that causes issues (for me anyway!). Using SubmitJob executation, I get a status of failed and this in the logging:

2012-07-01 13:24:34,378  INFO rid=116 'server' GPServer-exportmaptest - GET GPServer/Export Map Test/jobs/j73283e376de540ae8dfa830fd5475161?f=json&ts=1341105874377
2012-07-01 13:24:34,383  INFO rid=116 'worker-4540' STAServerObjectHost - Received Request.
2012-07-01 13:24:34,383  INFO rid=116 'worker-4540' Core - tasks/Export Map Test/jobs/j73283e376de540ae8dfa830fd5475161 (code=100001): REST request received. Request size is 0 characters.
2012-07-01 13:24:34,384  INFO rid=116 'worker-4540' Core - tasks/Export Map Test/jobs/j73283e376de540ae8dfa830fd5475161 (code=100004) (elapsed=0.000672904): REST request successfully processed. Response size is 951 characters.
2012-07-01 13:24:34,386  INFO rid=116 'server' GPServer-exportmaptest - Request handled.
2012-07-01 13:24:43,370  INFO rid=    '' WebServer - Lost connection on port 50000
2012-07-01 13:24:43,384  INFO rid=    '' WebServer - Lost connection on port 50000
2012-07-01 13:24:43,384  INFO rid=    '' WebServer - Lost connection on port 50000
2012-07-01 13:24:44,386  INFO rid=    '' WebServer - Lost connection on port 50000
2012-07-01 13:24:44,400  INFO rid=    '' WebServer - Lost connection on port 50000
2012-07-01 13:24:44,409  INFO rid=    '' WebServer - Lost connection on port 50000

[ShaunWeston]

Turns out arcpy.mapping is not supported in Runtime, so that's why I was getting these errors. From an ArcGIS Product Engineer:

"The RunTime works off of MSDs (not MXDs). The Arcpy.Mapping stuff all works off of the MXDs. So until the arcpy.Mapping enhances its core functionality, the RunTime cant do anything to support it. (They cant or wont go back and support MXDs as they�??re becoming �??legacy�?� and quite frankly their performance doesn�??t even come close to an MSD)."