Visual Studio is used to create a workflow and deploy the DLL to the BIN directory. The result shows that if there is a delay action in workflow, you will never wake up after you sleep.
Error message: the workflow assembly cannot be found.
The workflow and webpage requests are processed by different exe files. The requests sent on the webpage are processed by w3wp.exe, and workflowis processed by owstimer.exe. owstimer.exe does not know that a directory such as BIN exists for it to find the assembly. so the above situation occurs.
The solution is simple. You can deploy the DLL to GAC.
In addition, KB953630 describes a typical problem. A workflow with V1.0 has been deployed in the production environment. later, we modified the version and made a new DLL, but the version is still V1.0. In this way, the old DLL file will be overwritten. therefore, workflow may also experience sleep. the solution is to restart the Timer Service, but this is only valid for the newly created workflow. The problematic workflow still cannot be recovered. make up for it. haha.
If you use SharePoint Designer to create a workflow containing Pause for duration (Pause for _ days, _ hours, _ minutes) and never wake up after it is stopped, then we need to install. A hotfix of net framework 3.0, KB932394. after installation, the stopped workflow can be restored normally.
References
================
A workflow does not resume automatically when a delay activity is triggered in Windows SharePoint Services 3.0
Http://support.microsoft.com/kb/953630
A timer does not resume operation after a workflow is reloaded in Microsoft Windows Workflow Foundation
Http://support.microsoft.com /? Kbid = 932394