Select the product you need help with
Error message when you create a workflow that uses custom persistence services and the transaction service on a Windows Vista-based or Windows Server 2008-based computer: "Cannot request revert of instance state without calling checkpoint first"Article ID: 950679 - View products that this article applies to. On This PageSYMPTOMSOn a Windows Vista-based computer or on a Windows Server 2008-based computer, you create a workflow that uses custom persistence services and the transaction service. When you run the workflow, the process stops. Additionally, you receive an exception together with the following error message: Cannot request revert of instance state without calling checkpoint first CAUSEThis problem occurs because the Unload method in the workflow leads to an inconsistent state during a transaction scope rollback.
RESOLUTIONIf the computer is running Windows XP or Windows Server 2003, apply hotfix 948254.
For more information about hotfix 948254, click the following article number to view the article in the Microsoft Knowledge Base:
948254 If the computer is running Windows Vista or Windows Server 2008, use one of the following methods.
(http://support.microsoft.com/kb/948254/
)
Error message when you create a workflow that uses the custom persistence services and the transaction service by using the .NET Framework 3.0 Service Pack 1: "Cannot request revert of instance state without calling checkpoint first"
Method 1: Install the Microsoft .NET Framework 3.5 Service Pack 1 (SP1)To resolve this problem, install the .NET Framework 3.5 SP1. To obtain the .NET Framework 3.5 SP1, visit the following Microsoft Download Center Web site:http://www.microsoft.com/downloads/details.aspx?familyid=ab99342f-5d1a-413d-8319-81da479ab0d7&displaylang=en
(http://www.microsoft.com/downloads/details.aspx?familyid=ab99342f-5d1a-413d-8319-81da479ab0d7&displaylang=en)
Method 2: Apply this hotfixA supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.To resolve this problem immediately, 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.
(http://support.microsoft.com/contactus/?ws=support)
PrerequisitesThere are no prerequisites.Restart requirementYou do not have to restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other hotfixes.File informationThe 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.Windows Vista and Windows Server 2008 file information notes
For x86 versions of Windows Vista Service Pack 1 or of Windows Server 2008Collapse this table
For x64 versions of Windows Vista Service Pack 1 or of Windows Server 2008Collapse this table
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONFor 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 updatesAdditional file information for Windows Server 2008 and for Windows VistaAdditional file information for x86 versions of Windows Vista Service Pack 1 or of Windows Server 2008Collapse this table
Additional file information for x64 versions of Windows Vista Service Pack 1 or of Windows Server 2008Collapse this table
Call stack traceWhen you receive the exception, the call stack trace is as follows:
System.Workflow.Runtime.WorkflowStateRollbackService.RequestRevertToCheckpointState() System.Workflow.Runtime.WorkflowExecutor.System.Workflow.ComponentModel.IWorkflowCoreRuntime.RequestRevertToCheckpointState()
System.Workflow.ComponentModel.ActivityExecutionContext.RequestRevertToCheckpointState() System.Workflow.ComponentModel.TransactedContextFilter.System.Workflow.ComponentModel.IActivityEventListener<System.Workflow.ComponentModel.ActivityExecutionStatusChangedEventArgs>.OnEvent()
System.Workflow.ComponentModel.ActivityExecutorDelegateInfo<System.Workflow.ComponentModel.ActivityExecutionStatusChangedEventArgs>.ActivityExecutorDelegateOperation.Run()
System.Workflow.Runtime.Scheduler.Run()
System.Workflow.Runtime.WorkflowExecutor.RunScheduler()
System.Workflow.Runtime.WorkflowExecutor.RunSome()
System.Workflow.Runtime.Hosting.DefaultWorkflowSchedulerService.WorkItem.Invoke({System.Workflow.Runtime.Hosting.DefaultWorkflowSchedulerService})
System.Workflow.Runtime.Hosting.DefaultWorkflowSchedulerService.QueueWorkerProcess()
System.Threading._ThreadPoolWaitCallback.WaitCallback_Context()
System.Threading.ExecutionContext.Run()
PropertiesArticle ID: 950679 - Last Review: February 13, 2009 - Revision: 1.0
|
Back to the top
