Workflow and ServiceDesk Community

"Error starting/continuing dialog model execution LogicBase.Framework.ObjectDeserializationError: could not deserialize: LogicBase.Core.IOrchestrationComponent[] ---> System.Exception: could not find type UpdateUser.SqlQuery.UpdateUser"

The application crashes immediately with this error. It works fine in debug mode.

I have a lot of different SQL generators in my workflow and I've never had this problem. I just added a few more today and now this is happening.

Anyone know what's going on?

It's already checked :(

I would try manually moving it then, just as a sanity check.

Manually move the Dll file to IIS?

I can't even find the current file in IIS.

Make sure your updated component also resides on the server you deployed to, not just the one you're debugging on. Checking Publish in the Project Properties should make it do this.

I mean manually move the generated library from your server to the server you're publishing to.

I sometimes get confused as to the difference between Publish/Copy Local myself (I have to look at the code sometimes just to make sure). usually I find it quicker just to update the library on my deployment machine manually though... and just to really make sure the versions are exactly the same.

I have been publishing locally.

You probably have multiple copies of the generated lib on your local machine. And Workflow is loading the "wrong" one when you publish.

If you've been publishing locally, I'd uncheck Publish from your project properties. Then I'd hunt for the bad copy (probably in the \bin folder of the deployed project). I like to keep the "latest and greatest" copies of my generated DLLs in the standard place: <install>/Shared/customlib.

Wow, thank you =)