Skip to main content

Workflow crash after upgrade

Eric Kriener

I have a workflow that was working perfectly, then we upgraded the silverlight viewer to the latest version. We also upgraded Essentials to the latest 'Instant Search' version.

Now my workflow explodes when I try to run it.

I can tell it works part of the way because the feature returns a count of 1 if I put in an Alert. When the Select Features activity runs, it highlights the record (in red), but then the workflow crashes and I get the following error below.

It runs to completion and I do not get an error in the simulator.

/customer/servlet/servlet.FileDownload?file=00P6000000eltpLEAQ   It throws the NullReferenceException and debugging resource strings are unavailable errors.

Here's the kicker though....If an identify/search/view details (of the clearly selected parcel) operation happens, this workflow will run w/o error.

Like I said, this worked before instant search and Silverlight 2.1

Also, I get this exact same behavior on TWO DIFFERENT servers (test and production)

The workflow can be found in this thread: (https://support.geocortex.com/SupportForums/Thread.aspx?pageid=0&mid=2&ItemID=20&thread=54961&pagenumber=2) S (https://support.geocortex.com/essentialsGSCForum?sub-nav=forum&main-nav=essentials&feedtype=SINGLE_QUESTION_SEARCH_RESULT&id=9066000000009qaAAA) erver Scope

It blows up on the select parcel after the decision.

Thoughts???

0

Comments

4 comments

Date Votes
  • Nico Burgerhart

    Are the mapservice/layer ids the same, after the upgrade?

    Try to remove the Select Features from your workflow and add it again. I've seen similar issues where this solved the problem.

    Is a collection name set in the Select Features activity? If it is, try to run the workflow without a collection name.

    0
  • Eric Kriener

    Yes

    No luck

    No, never has been.

    0
  • Eric Kriener

    The problem is definately in the SelectFeatures action.

    If I remove it from the flow, the process finishes, but I want the feature selected on my map.

    I have created an entirely new workflow (same process) and assigned it to a new button and it fails the exact same way.

    If I turn on debug, the In Arguments are there, layer and map service id and FeatureSet.

    Why am I getting that error?

    Why does searching/identifying/selecting something previous to using this tool, allow it to work?

    Why did it start failing after an upgrade?

    0
  • Permanently deleted user

    I am having the same problem.  Has anyone figured out what maybe the cause of this error??

     

    Jake

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post