Select the product you need help with

A timer does not resume operation after a workflow is reloaded in Microsoft Windows Workflow Foundation

Article ID: 932394 - View products that this article applies to.

SYMPTOMS

In Microsoft Windows Workflow Foundation, a timer does not resume operation after a workflow is reloaded.

This problem occurs because the unload operation changes the status of the timer queue and does not set the dirty bit for the workflow. The timer queue has a Boolean flag. This flag is used to indicate whether the scheduler service must reregister the timer queue. When the workflow is unloaded, this flag changes to indicate that the workflow must be reregistered to reload the workflow. If the unload operation does not set the dirty bit for the workflow, this change may not be saved. If this change is not saved, the problem that is mentioned in the "Symptoms" section occurs.

Back to the top | Give Feedback

Update information

A supported update is now available from Microsoft. This update is available for download from the following Microsoft Download Center Web site:

http://www.microsoft.com/downloads/details.aspx?FamilyID=6096ce0f-d21e-47ac-afe2-d4e1c2fce670

(http://www.microsoft.com/downloads/details.aspx?FamilyID=6096ce0f-d21e-47ac-afe2-d4e1c2fce670)

Prerequisites

You must have the Microsoft .NET Framework 3.0 installed to apply this update.

Restart requirement

Although you may not receive a prompt at the end of the installation, you must restart the computer after you apply this hotfix.

Update replacement information

This update does not replace any other updates.

File information

The English version of this software update package has the file attributes or the later file attributes that are listed in the following table.

32-bit versions

Collapse this tableExpand this table

File name	File version	File size	Date	Time
System.workflow.activities.dll	3.0.4203.201	1,111,424	20-Feb-2007	16:53
System.workflow.componentmodel.dll	3.0.4203.201	1,643,912	20-Feb-2007	16:53
System.workflow.runtime.dll	3.0.4203.201	591,224	20-Feb-2007	16:53

64-bit versions

Collapse this tableExpand this table

File name	File version	File size	Date	Time
System.workflow.activities.dll	3.0.4203.201	1,111,424	20-Feb-2007	16:53
System.workflow.componentmodel.dll	3.0.4203.201	1,643,912	20-Feb-2007	16:53
System.workflow.runtime.dll	3.0.4203.201	591,224	20-Feb-2007	16:53

Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Back to the top | Give Feedback

MORE INFORMATION

The following issues are also fixed in this update:

After you rename an activity, you cannot add the same type of activity to a workflow.
The version of an assembly is incorrect in custom workflow actions.

This update resolves the issue that is mentioned in Microsoft Knowledge Base article 932816. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

932816

(http://support.microsoft.com/kb/932816/ )

FIX: You experience various problems in Windows Workflow Foundation

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684

(http://support.microsoft.com/kb/824684/ )

Description of the standard terminology that is used to describe Microsoft software updates

Back to the top | Give Feedback