We have seen the following error in our SharePoint workflows, regardless of whether they were created with Office SharePoint Designer 2007 or Visual Studio 2005:
The error, at least in our solutions, occurs as the result of two specific conditions:
- The workflow includes an action to update the current list item.
- The save/submit operation came from a client application (e.g., Office Word 2007, Office InfoPath 2007) that was still open at the time the workflow was triggered.
Essentially, the Windows Workflow Foundation timer does not resume correctly after a workflow is reloaded. NOTE: The error cannot be reproduced when submitting a browser form.
In the past, we have tried workarounds for this issue. One option is to have the end user first close the client application. This will prompt the end user to save the file, and the application will be closed before the workflow is triggered. Another option is to add a Pause For Duration action to the workflow, thus providing the end user with a specific amount of time in which to close the client application before other actions occur, as shown in the following figure.
The problem with either of these workarounds is the dependency on the end user to follow a specific save/submit procedure. In a production setting, there is no guarantee that the client application will be closed in a certain manner.
Then, I stumbled across this post. A comment at the bottom indicates that a combination of Windows Server 2003 SP2 and KB932394 solves the problem. I tried the update and patch for my server and it worked. Many thanks to the SharePoint User Group UK for posting this information…