When wwf arise on delay activity(first time, to be idled), I got exception:

InnerException {"Workflow with id \"b74cbe7e-1080-4351-b06b-766c006f6e66\" not found in state persistence store."} System.Exception {System.InvalidOperationException}theory: When WWF wait delay (10 sec..), it occured WorkflowIdled handler. At that moment, wwf is persisted at database (insert into, not select like exception message said).

What is wrong? I observed by sql profiler, SqlPersistenceService attempt to execute only select sql procedure.

Tuesday, March 21, 2006 1:14 PM

Answers

- WorkflowInstance.Unload() doesn't work correct in my sample. Nothing in persitence store, no exceptions...It must be some internal logging at debug for Microsoft team, for internal purpose.- Decompiling method Unload by Lutz Roeder's .Net Reflector. And here is: <add name="WorkflowTraceToDefault" value="1" />- It makes WorkflowTrace.log, where we have everything, what we need. I didn't make to be seriazable custom class library, which I used at statemachine workflow. I fixed that, and now is ok.

In sequential workflows, it is FaultHandler for this purpose, I didn't find at stateworkflow some activity for root exceptions.

- WorkflowInstance.Unload() doesn't work correct in my sample. Nothing in persitence store, no exceptions...It must be some internal logging at debug for Microsoft team, for internal purpose.- Decompiling method Unload by Lutz Roeder's .Net Reflector. And here is: <add name="WorkflowTraceToDefault" value="1" />- It makes WorkflowTrace.log, where we have everything, what we need. I didn't make to be seriazable custom class library, which I used at statemachine workflow. I fixed that, and now is ok.

In sequential workflows, it is FaultHandler for this purpose, I didn't find at stateworkflow some activity for root exceptions.

I really don't know if it is the same problem, but I got this exception when I added both the SqlTrackingService and the SqlWorkflowPersistenceService to the runtime. The solution was adding the SharedConnectionWorkflowCommitWorkBatchService as well. Somehow it helps those two, to use the same connection string.

I had got the same problem and the same solution worked for me too. Notice that all three services must have same connection string, this means that Persistence Data and Tracking Data are on the same database.

MS bug or normal behaviour?

Friday, January 26, 2007 11:43 PM

Microsoft is conducting an online survey to understand your opinion of the Msdn Web site. If you choose to participate, the online survey will be presented to you when you leave the Msdn Web site.