Persistence errors when switching from self-hosted workflow to a workflow service in Workflow Foundation 4

I am developing an application that is using a state machine constructed in Windows Workflow Foundation 4 in order to control the workflow of several application tiers. The workflow executes admirably, for the most part, however unexpected problems appeared when sqlWorkflowInstanceStore was added.

More specifically, when running as a workflow service some of the necessary data (ActiveBookmarks, ExecutionStatus, IsInitialized, IsSuspended and a few other fields) does not get saved into the database when a workflow is persisted.

I have spent several days debugging this only to find that when the exact same workflow is run with the exact same settings, but as a self-hosted activity, instead of a workflow service ever开发者_运维百科ything performs without a hitch. This leads me to believe that the problem is somewhere in the server/host configuration.

I am going to try hosting under different configs as well as hosting an activity in IIS as per these guides:

Hosting a self-hosted WF in IIS

http://msdn.microsoft.com/en-us/library/ff729688.aspx

However, if someone can point me to a more specific reason for this error, I would be very grateful as this is currently the single biggest issue that needs to be tackled before we can release.

Check out How to troubleshoot Windows Server AppFabric and Workflows