Extract Data Task

Permanently deleted user

18. Juni 2014 00:27

I am working to setup my Extract Data Task.  My geoprocessing service now works in ArcMap.  I setup the workflow like the LA County example site.  I am recieving an error at the point where I need to be returned the file, I get:

"There was a workflow error running activity: Exception has been thrown by the target of an invocation. Workflow 'Extract' failed Unhandled exception: 'The geoprocessor operation did not complete successfully and returned the job status 'esriJobFailed'.' in activity '1.22: Geoprocessor'. The geoprocessor operation did not complete successfully and returned the job status 'esriJobFailed'."

What are the possible reasons this operation could fail?  When I run the geoprocessing service in ArcMap I get a zip file with correct contents here:C:\Users\userNameHere\AppData\Local\Temp\arcDBB2.

0

• 

  Permanently deleted user

  18. Juni 2014 21:19

  I found this forum:

  http://forums.arcgis.com/threads/20601-Data-Extract-Widget-Error-%28esriJobFailed%29

  Thus, I went into ArcGIS Server Manager, changed the times and then my workflow was partly successfull.  My Extract Data Task geoprocessing service works in ArcMap.  However, the workflow only errors out when features are set to download that have underscores, _ , in their SDE feature class names.  The workflow is successfull if I select feature classes that do not have underscores in their file names.  Where would this error be stemming from?  Is there anything to fix this?

   

  0
• 

  Permanently deleted user

  18. Juni 2014 21:47

  The error in the Server Manager Log file is : ERROR 000732: Layers to Clip: Dataset RuralLegacy;FFP does not exist or is not supported The value does not exist. The value is empty. ERROR 000732: Layers to Clip: Dataset RuralLegacy;FFP does not exist or is not supported.  

  The dataset with the underscore is Rural_Legacy.  Also, when I run the tool with one or more  files with no underscores it works fine. 

  0
• 

  Permanently deleted user

  18. Juni 2014 21:56

  Disregard, it is fixed, I was naming the layer list differently than the name of the layer as for some reason I was thinking they would be selected by order instead of the literal value of the string. 

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.