Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. BizTalk orchestration instance may crash when you restart BizTalk host instances while ordered message instances are active

BizTalk orchestration instance may crash when you restart BizTalk host instances while ordered message instances are active

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You create a BizTalk application in Microsoft BizTalk 2006 R2, in Microsoft BizTalk 2009, or in Microsoft BizTalk 2010. The application uses BizTalk orchestrations to implement ordered message delivery.
  • You use the BizTalk Administration console to restart the BizTalk host instances that host the BizTalk application while the ordered message delivery instances are active.
In this scenario, the orchestration instance that publishes the ordered message delivery instances may crash. Additionally, you receive an error message that resembles the following:

Uncaught exception (see the 'inner exception' below) has suspended an instance of service '<service name and GUID>'.
The service instance will remain suspended until administratively resumed or terminated.
If resumed the instance will continue from its last persisted state and may re-throw the same unexpected exception.
InstanceId: service instance
Shape name: shape name
ShapeId: shape ID
Exception thrown from: segment 2, progress 4
Inner exception: The handle is invalid. (Exception from HRESULT: 0x80070006 (E_HANDLE))

Exception type: COMException
Source: Microsoft.XLANGs.BizTalk.Engine
Target Site: Void Commit()
The following is a stack trace that identifies the location where the exception occured at Microsoft.BizTalk.XLANGs.BTXEngine.BTXXlangStore.Commit()
at Microsoft.XLANGs.Core.Service.Persist(Boolean dehydrate, Context ctx, Boolean idleRequired, Boolean finalPersist, Boolean bypassCommit
Note In this error message, the word "occured" is a misspelling for the word "occurred."

↑ Back to the top

Cause

This issue occurs because of a race condition when the XLANG engine shuts down orchestration instances and when the XLANG engine processes message instances.

↑ Back to the top

Resolution

BizTalk Server 2006 R2

Cumulative update information

The hotfix that resolves this issue is included in cumulative update package 4 for BizTalk Server 2006 R2 SP1.

For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:


2682056 Cumulative update package 4 for BizTalk Server 2006 R2 SP1

BizTalk Server 2009

The fix for BizTalk Server 2009 is currently not available.

BizTalk Server 2010

Cumulative update information

The fix for this issue was first released in Cumulative update package 1 for BizTalk Server 2010. For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2497789 Cumulative update package 1 for BizTalk Server 2010

↑ Back to the top

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

More Information

For more information about ordered message delivery, visit the following MSDN website:
General information about ordered message delivery
For more information about BizTalk Server hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:
2003907 Information about BizTalk Server hotfixes

↑ Back to the top

Keywords: kb, kbqfe, kbexpertiseadvanced, kbsurveynew, kbfix

↑ Back to the top

Article Info
Article ID : 2458218
Revision : 1
Created on : 1/7/2017
Published on : 4/12/2012
Exists online : False
Views : 510