The purpose of the Windows workflow transaction services is to enable custom logic regarding the commitment of work batches.
23-11-2009 15:33:33 - -184.108.40.206
Workflow Scheduler Services manage how workflow instances are scheduled by the workflow runtime engine.
23-11-2009 15:33:20 - -220.127.116.11
Tracking services manage tracking profiles and storage of tracking information.
23-11-2009 15:33:31 - -18.104.22.168
Another possible reason is that the workflow you are sending a message to is already terminated. This might happen if your code is responding to an event that has already timed out allowing the workflow to terminate. The error is misleading in this case because the WorkflowRuntime doesn't know that the workflow has finished and tries to load it from the, in this case, non existent WorkflowPersistenceServices. In this case you will find an InnerException with the text "The workflow hosting environment does not have a persistence service as required by an operation on the workflow instance "SomeId"."
The set of objects used to host the Workflow and provide services to it.
23-11-2009 15:33:06 - -22.214.171.124
add a one or paragraph summary or description of what's discussed here; put yours after 'Summary:'
23-11-2009 15:24:27 - 126.96.36.199