Skip to main content

Workflow Errors (URI empty) in custom Parcel Report

Permanently deleted user

Hello,

We have a custom Parcel Report (created in Sept-Oct 2012 by Latitude developers) that reports attributes from 60 layers intersected by a selected parcel.  This is accomplished by querying a "flattened" table that stores a record with a field for each feature_class.attribute of interest for each parcel.  This table is re-created monthly using a spatial join toolbox created by Latitude.  This report uses Workflows (which I am not at all familiar with), and is included in an Essentials REST v3.10.1 site with a Silverlight v1.6 Viewer.

For most parcels, this tool is working fine.  However, over time our users (mostly Planning Department) have found a few parcels that fail to generate a Parcel Report, and instead report: "Workflow Error...Exception has been thrown by the target of an invocation.  Workflow 'Create PBI Parcel Report' failed.  Aborted exception: 'Invalid URI: The URI is empty.'  Invalid URI: The URI is empty."

For each of these failures, there is an entry in the Essentials REST SYSTEM.date.log file that repeats that information, with several additional lines.  

And for each of these errors, there is a simultaneous ASP.NET4.0.30319.0  Web Event Error in the Application Event Viewer on the server that reports, with some additional detail, that "An unhandled exception occurred and the process was terminated.  Application ID: /LM/W3SVC/1/ROOT/Geocortex/Essentials/Prod/REST...Exception calling REST endpoint;System.Runtime.Serialization.SerializationException: The length of the query string for this request exceeds the configured maxQueryStringLength value."

And another .NET Runtime Error that repeats much of the same data for each failure.

 

I've been looking at this as a data problem, given that it only occurs for a few parcels (so far), but I've been unable to identify a deficiency common only to the problem parcels in either the flattened table (we call it "PR_Collector") or the intersected layers or the parcel geometry.  I've looked for excessively long query results, as suggested by the .NET error report of a query string that exceeds the maxQueryStringLength value, but don't see anything in the data to suggest that, and the error doesn't provide enough information for me to find which query string is the problem.  A general search on the maxQueryStringLength exception gets some hits, but none with answers that I can make sense of.  Likewise, I haven't found anything applicable on the "Aborted exception:  Invalid URI: The URI is empty" error.

Does anyone have any suggestions for identifying the particular URI that is "empty", or what that even means.  I have put this in the Workflow forum primarily because of all the references to Workflow in the errors.  Please bear in mind, again, that I am completely new to Workflows and their role in running tasks.  (I had thought of them as building tools, and didn't see them as runtime components in the reporting process.)

Thanks to anyone who can help me figure out how to go about diagnosing this problem.

Jim Bergstrom

County of Monterey

0

Comments

2 comments

Date Votes
  • Permanently deleted user

    Hi Jim

    my guess is that you have some parcels who geometries are complicated ie not just a nice rectangle with 4 vertices that define it.

    I would suggest adding a test for this error condition into the workflow and when it does fail have the workflow return to the client the JSON of the parcel geometry. Are you prepared to share the workflow?

    Regards

    Ralph Price

    0
  • Permanently deleted user

    Hi Ralph,

    Thanks for the quick response.  I've looked at the geometries of several parcels that both failed and succeeded in generating a parcel report, specifically looking for geometry abnormality and/or complexity.  Oddly I don't see any correlation here at all.  Parcels that have simple 4 to 6 vertex geometry, with no odd corners fail, while others nearby that have 20 vertices, with sharp angles, narrow strips, and even overlaps succeed.  This comes as a surprise to me, so I haven't ruled out geometry as a cause of failure yet.

    I'm not sure what you mean by "share the workflow", so I can't answer that question yet.  I don't know enough about Workflows to know if I could share it, or if Latitude would object to my sharing it if I could (since they created the Workflow), and I don't know what the "JSON of the parcel geometry" means.  I'm not a web programmer, which is why we bought Essentials in the first place, believing that we could build sites mostly using out-of-the-box tools;  that works up to a point, but when we needed a complex, custom report, we hired Latitude to do it for us.  So now I have a lot of catching up to do just to understand how to troubleshoot the errors it generates.

    Thanks again,

    Jim

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post