Article ID: 2263355 - View products that this article applies to.
Consider the following scenario:
For example, you run two orchestrations that are named A and B and that meet the following requirements:
This issue occurs because an orphaned instance is incorrectly created in the BizTalkDTADb database.
When an orphaned instance is incorrectly created in the BizTalkDTADb database, the service instance has no corresponding record in the BizTalkMsgBoxDb database. Additionally, the dtEndTime field of the dta_ServiceInstances table is never populated in the BizTalkDTADb database. Therefore, the DTA Purge and Archive job does not remove the orphaned instance. After the BizTalk orchestrations runs for a while, and the BizTalkDTADb database becomes very large.
Cumulative update informationFor more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2429050Note KB978796 resolves a similar issue. However, this issue can still occur even if you have installed the hotfix in KB978796.
(https://support.microsoft.com/kb/2429050/ )Cumulative update package 1 for BizTalk 2009
For more information about the hotfix in KB978796, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/978796/ )FIX: An orphaned BizTalk DTA service instance is created unexpectedly after a BizTalk orchestration handles an exception
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about BizTalk Server hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/2003907/ )Information about BizTalk Server hotfixes
Article ID: 2263355 - Last Review: February 10, 2011 - Revision: 2.0