Workflow Error
When I run my custom workflow in Silverlight Viewer 1.5 (Essentials 3.8), I get the following error dialog, titled Workflow Error:
Exception has been thrown by the target of an invocation.
Workflow 'WhereILiveWF' failed
Aborted exception: 'The remote server returned an error: (500) Internal Server Error.'
The remote server returned an error: (500) Internal Server Error
[OK]
I looked at the Essentials logged and they show nothing related to this error (at the dates and times I generate it). I also checked my ArcGIS Server logs (via Manager) and they don't show any errors or warnings at the dates and times I test it, either.
Just so you know, I can't run this workflow through the simulator because of calls to the Invoke Method activity (at least that's what I was told by a developer there). It was working before, and I know we made some changes to the server, not to the workflow, but I can't figure out what change caused this problem.
"Roj"
-
We are experiencing the same error - did you ever find a resolution? Thanks
0 -
Hi Nick,
Can you provide more details? What kind of workflow are you running? When is this happening, at the start of the workflow or after a specific client activity? Have you looked at the Essentials logs to see what is happening around the time of the error?
Cheers,
Christian.
0 -
Christian, our workflow captures geometry, runs QueryTask and then binds the results to the global data grid using the Select Features activity. This was running fine until we updated the "Out Fields" in QueryTask and set "Return Geometry" to False and republished the workflow. The workflow appears to still work correctly, however, we are getting this error right after the results are bound to the global data grid in the viewer. Nothing in the Essentials logs about it. Same error in designer as in the viewer. Thanks
0 -
I don't have time to look through this right now due to snow storm recovery issues right now. Our issue and workflow is very similar to what Aaron is describing.
0 -
Wayne,
I can't speak for Nick, but for us the problem seems to come and go as changes are made to the workflow after deployment and as time passes the error goes away. The workflow always completes, but it doesn't look good and confuses the user. No word back from Latitude on this defect; however, we have demonstrated to them. Hopefully, this can get resolved soon.
Thanks,
Aaron
0 -
I have not had a chance to look at it. In my case I have a workflow that is literally exactly the same as the one I have the issue with and it works fine however the other one still gets the error. I posted my xaml to this thread it is sounds very similar to the Aarons workflow so maybe some one from lattitude can take a look. The strange thing is the workflow was working fine for awhile. Is it possible xaml files can get corrupted?
(https://support.geocortex.com/Data/Sites/1/userfiles/1189/planning_mailinglabelselectionparcelowners.xaml) /Data/Sites/1/userfiles/1189/planning_mailinglabelselectionparcelowners.xaml
0 -
Exactly the same issue for me as well. This issue does seem to come and go for us as well. I have an identical workflow to this one the only difference is the one that does not work properly runs a query task on a polygon layer(parcels) and the one that does work properly runs a query task on a point layer(addresses). Each workflow is setup to create a mailing list using a geocoding task, buffer task, and query task.
0 -
Nick,
Our problem also from a polygon feature layer which we use a autocomplete box to finish the subdivision search and the workflow runs well until the last screen give you this error message.
Wayne
0 -
Looks like we may have found a common issue it seems to be related to something to do with polygon geometry possibly.
0 -
We are also selecting polygons in our workflow.
0 -
Hi Nick,
Thanks for the Xaml. Are you able to capture all the HTTP traffic with Fiddler and send it along to (support@geocortex.com) ? That should provide use with enough to reproduce this problem in our environment. Thanks.
--Ryan
0 -
Ryan,
The fiddler2 http traffic does not give any type of error message. I look at the Geocortex logs file. It says "Json string is invalid and not supported". If you need me to send the logs file I can do it for you. Thanks
Wayne
0 -
We are getting the same thing. Here is the extract from my log file related to the workflow issue. Also in fiddler it really just gives a 500 error so it does not really tell much.
="2012-02-10T08:13:51.0209981-08:00" Level="ERROR" Identity="Guest"><Message>Unable to deserialize object: JSON string is invalid or not supported.</Message></Event>
<Event Timestamp="2012-02-10T08:13:51.3803938-08:00" Level="ERROR" Identity="Guest"><Message>Error occured during REST request: Unable to load specified workflow from instance store.</Message></Event>0 -
Thanks for the log information. I'd still like to see the Fiddler traffic if possible. This isn't an HTTP problem, but the requests that lead up to the error will contain the invalid workflow state. That's what I'd like to examine. Thanks,
--Ryan
0 -
I just emailed a fiddler extract to the support email
0 -
Hi Everyone,
I did few tests after checking logs file again this morning. Since it is a Json stream type of error, I removed the Wild character "*" in the query tasks to replace with few field names and the error is gone. I guess the query tasks might not happy with certain fields. Please give it try and see your result. Thanks
Wayne
0 -
Well, the Essentials log DOES show an error; it's just that it's not more helpful to me than the dialog box. Maybe it means something to somebody else, though:
<Event Timestamp="2012-05-08T08:38:51.7361956-06:00" Level="ERROR" Identity="Guest"><Message>Workflow 'WhereILiveWF' failed. Cause: Geocortex.Workflow.WorkflowException: Aborted exception: 'The remote server returned an error: (500) Internal Server Error.'. ---> System.Net.WebException: The remote server returned an error: (500) Internal Server Error.
at Geocortex.Workflow.Activities.QueryTask.Execute(NativeActivityContext context)
at System.Activities.NativeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager)
at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
--- End of inner exception stack trace ---</Message></Event>
<Event Timestamp="2012-05-08T08:38:51.7361956-06:00" Level="ERROR" Identity="Guest"><Message>Exception has been thrown by the target of an invocation.
Workflow 'WhereILiveWF' failed
Aborted exception: 'The remote server returned an error: (500) Internal Server Error.'.
The remote server returned an error: (500) Internal Server Error.</Message></Event>"Roj"
0 -
May I please be given the Idiot of the Year Award, oh, pretty please? I changed one of my ArcGIS Server services to have 1 layer instead of 2. That made my Query Service URL change from /1 to /0 at the end. That's why the workflow was breaking. Thank you. I proudly accept this rusty medal of dishonor. I will try to surround my steps with tries and excepts so I know which query is breaking.
"Roj"
0 -
Hi Roger,
These lines are the interesting bit:
System.Net.WebException: The remote server returned an error: (500) Internal Server Error.
at Geocortex.Workflow.Activities.QueryTask.Execute(NativeActivityContext context)Basically the Execute method of the QueryTask was running and attempted to make a web request to ArcGIS Server. ArcGIS Server returned an error. Either there is a problem with the URL or the Where Clause you've configured on the QueryTask, or there is a problem with the ArcGIS REST endpoint itself. Try opening the ArcGIS REST endpoint in a web browser and verify that it is running correctly.
--Ryan
0 -
We were experiencing this error periodically as well. In our case it was a data-driven issue. One of the fields we were returning from a QueryTask contained values with a "\", Eliminating that output field and/or an alteration of the data within corrected the problem.
Paul
0
Please sign in to leave a comment.
Comments
20 comments