GPFeatureRecordSetLayer 10.0 vs 10.1 Server?

I have a very simple workflow I am testing my problem with for a 10.1 GP Service in a Workflow. User uses DisplayCaptureGeometry activity to draw geometry. Geometry gets added as a markup. Assign FeatureSet geometry variable to 'new ESRI.ArcGIS.Client.Tasks.FeatureSet(geometry)'. Make sure there is a record to pass into GP service using myFeatureSet.Features.count.tostring. I then pass my FeatureSet variable into my GP service's only parameter. It fails. This is the EXACT same workflow I am using for a 10.0 GP Service and it works perfectly.

Is the REST endpoint the real difference here? Same exact tool b/w 10.0 and 10.1, same code, etc. The error I am getting tells me the 'esriJobFailed.' I usually get this error if there is a problem within the script, but I believe the input variable is not being read correctly by the REST service.

.py code used for GP tool:

import arcpy, os

coords = arcpy.GetParameter(0)

arcpy.AddMessage("done")

toolbox param = Feature Set

REST param type= GPFeatureRecordSetLayer

Error from GC error log:

<Event Timestamp="2012-12-31T08:45:30.0829466-08:00" Level="ERROR" Identity="Guest"><Message>Workflow 'spo_test' failed. Cause: Geocortex.Workflow.WorkflowException: Aborted exception: 'The geoprocessor operation did not complete sucessfully and returned the job status 'esriJobFailed'.'. ---> System.InvalidOperationException: The geoprocessor operation did not complete sucessfully and returned the job status 'esriJobFailed'.

at Geocortex.Workflow.Activities.Geoprocessor.OnExternalDelayCompleted(NativeActivityContext context, ActivityInstance completedInstance)

at System.Activities.Runtime.ActivityCompletionCallbackWrapper.Invoke(NativeActivityContext context, ActivityInstance completedInstance)

at System.Activities.Runtime.CompletionCallbackWrapper.CompletionWorkItem.Execute(ActivityExecutor executor, BookmarkManager bookmarkManager)

--- End of inner exception stack trace ---</Message></Event>

<Event Timestamp="2012-12-31T08:45:30.0848998-08:00" Level="ERROR" Identity="Guest"><Message>Exception has been thrown by the target of an invocation.

Workflow 'spo_test' failed

Aborted exception: 'The geoprocessor operation did not complete sucessfully and returned the job status 'esriJobFailed'.'.

The geoprocessor operation did not complete sucessfully and returned the job status 'esriJobFailed'.</Message></Event>

Again, this works in 10.0 just fine. Any help or insight would be greatly appreciated!!! Happy New Year.

Permanently deleted user

January 03, 2013 04:10

Hi Ryan,

Can you check the Messages out argument on the Geoprocessor activity for any additional information about why the gp task failed? It should tell you there if the problem is that it can't read the input variable, or if there is something else going on.

-Victoria

Ryan Kelley

January 04, 2013 00:59

Hi Victoria,

Thank you for the reply. I am a bit stuck here. I did create a var for the out argument messages within the GP activity. I put the GP activity in a Try and an Alert of that variable in the Catch, but this doesn't seem to help any. Is this the best way to go about seeing these messages? I am guessing not.

My log .dat files on the ArcGIS Server side are not really readable, but I can make out at least that the geometry is trying to be written.

January 05, 2013 00:17

Is anyone able to assist in how to use the Messages out argument on the Geoprocessor activity? There is no help documentation on this and I am unsure where to look for the messages when the GP activity fails. I am not getting any logs generated on the ArcGIS Server side, other than in the jobs directory, which are somewhat cryptic. Anyone? thanks.

Ryan

January 05, 2013 00:31

I have not yet used 10.1 but if you run it from the endpoint directly you should be able to see the messages. At least that is how it worked in 10.

GPFeatureRecordSetLayer 10.0 vs 10.1 Server?

Comments

Didn't find what you were looking for?