Article ID: 2458218 - View products that this article applies to.
Consider the following scenario:
Note In this error message, the word "occured" is a misspelling for the word "occurred."
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
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
This issue occurs because of a race condition when the XLANG engine shuts down orchestration instances and when the XLANG engine processes message instances.
BizTalk Server 2006 R2
Cumulative update informationThe 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:
(http://support.microsoft.com/kb/2682056 / )Cumulative update package 4 for BizTalk Server 2006 R2 SP1
BizTalk Server 2009The fix for BizTalk Server 2009 is currently not available.
BizTalk Server 2010
Cumulative update informationThe 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:
(http://support.microsoft.com/kb/2497789/ )Cumulative update package 1 for BizTalk Server 2010
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about ordered message delivery, visit the following MSDN website:
General information about ordered message deliveryFor more information about BizTalk Server hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/2003907/ )Information about BizTalk Server hotfixes
Article ID: 2458218 - Last Review: April 12, 2012 - Revision: 3.0