- 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.
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
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:
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:
Article ID: 2458218 - Last Review: Apr 12, 2012 - Revision: 1