FIX: Persisted workflows do not run after you upgrade the tracking service to a newer version in Windows Workflow Foundation

Article translations Article translations
Article ID: 956630 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario. You have a custom tracking service that tracks persisted workflows in Windows Workflow Foundation. After you upgrade the tracking service to a newer version, the persisted workflows do not run. Additionally, you receive an exception that resembles the following:
System.Workflow.Runtime.QueueException: Event Queue operation failed with MessageQueueErrorCode QueueNotFound for queue 'Message Properties
Interface Type:<Interface type>
Method Name:<Method>
CorrelationValues:
'.

CAUSE

In Windows Workflow Foundation, the type information is saved in persisted workflows. The type information includes the tracking interface and the assembly version numbers. After you upgrade the tracking service to a newer version, the persisted workflows do not run, and a System.Workflow.Runtime.QueueException exception is thrown.

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

You must have the Microsoft .NET Framework 3.0 Service Pack 2 (SP2) or the Microsoft .NET Framework 3.5 Service Pack 1 (SP1) installed to apply this hotfix. You must apply this hotfix on Windows XP or on Windows Server 2003.

Restart requirements

Although you may not be prompted at the end of the installation, you must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

Post-installation instructions

After you install this hotfix, you can add a PreviousTrackingService attribute to your custom tracking service code. This attribute will allow for multiple entries of previous assembly versions. The resulting code should resemble the following:
   [System.Workflow.Runtime.Tracking.PreviousTrackingService("myNamespace.Workflow.StateMachineTrackingService, myNamespace.Workflow.StateMachineTracking, Version=1.0.0.1, Culture=neutral, PublicKeyToken=gr4b2191f58h9e0d")]
   [System.Workflow.Runtime.Tracking.PreviousTrackingService("myNamespace.Workflow.StateMachineTrackingService, myNamespace.Workflow.StateMachineTracking, Version=1.1.0.1, Culture=neutral, PublicKeyToken=gr4b2191f58h9e0d")]
   [System.Workflow.Runtime.Tracking.PreviousTrackingService("myNamespace.Workflow.StateMachineTrackingService, myNamespace.Workflow.StateMachineTracking, Version=1.2.0.1, Culture=neutral, PublicKeyToken=gr4b2191f58h9e0d")]
   public class StateMachineTrackingService : TrackingService
   {
   }

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
.NET Framework 3.0 SP2, x86-based version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
System.workflow.runtime.dll3.0.4203.4076540,67210-Mar-200923:08x86

.NET Framework 3.0 SP2, x64-based version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
System.workflow.runtime.dll3.0.4203.4076454,65610-Mar-200922:39x64

WORKAROUND

To work around this issue, remove the tracking interface from the implementation assembly, and then create a separate assembly for the tracking interface.

Note Do not change the interface assembly or the version of the interface assembly.

In this manner, all the persisted workflows will have the same type information in the tracking interface. In addition, there will be no errors or exceptions even if the implementation assembly is changed or if the version of the implementation assembly is changed.

Note This workaround will not work if there is a change in the interface definition.

STATUS

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

MORE INFORMATION

For more information about the workflow versioning in Windows Workflow Foundation, visit the following Microsoft Web site:
http://msdn.microsoft.com/en-us/library/aa349375(VS.85).aspx
For more information about the tracking services in Windows Workflow Foundation, visit the following Microsoft Web site:
http://msdn.microsoft.com/en-us/library/bb264459(VS.80).aspx
For more information about hosting Windows Workflow Foundation, visit the following Microsoft Web site:
http://msdn.microsoft.com/en-us/library/aa663362.aspx

Properties

Article ID: 956630 - Last Review: June 22, 2009 - Revision: 2.1
APPLIES TO
  • Microsoft .NET Framework 3.0 Service Pack 2
  • Microsoft .NET Framework 3.5 Service Pack 1
  • Windows Workflow Foundation
Keywords: 
kbhotfixserver kbexpertiseadvanced kbsurveynew kbqfe KB956630

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com