FIX: An orphaned BizTalk DTA service instance is created unexpectedly after a BizTalk orchestration handles an exception

Consider the following scenario:

• You have a BizTalk orchestration on a computer that is running Microsoft BizTalk Server 2006 R2 or Microsoft BizTalk Server 2009.
• The BizTalk orchestration contains a Catch Exception block.
• You disable all the tracking options for the BizTalk orchestration.
• When the BizTalk orchestration processes a message, an exception is thrown. This exception is caught and handled by the Catch Exception block. Therefore, the orchestration finishes the processing operation gracefully.

In this scenario, an orphaned BizTalk DTA service instance is created in the BizTalk Tracking (BizTalkDTADb) database unexpectedly. This orphaned BizTalk DTA service instance is never removed by the DTA Purge and Archive job. Therefore, after the BizTalk orchestration runs for some time, the BizTalkDTADb database becomes very large.

Note An orphaned DTA service instance has a record in the dta_ServiceInstances table of the BizTalkDTADb database. The dtEndTime field in this record contains a NULL value. However, the service instance has no corresponding record in the MessageBox database. Therefore, the dtEndTime field is never populated, and the DTA Purge and Archive job never removes the orphaned BizTalk DTA service instance.

Cumulative update information

For BizTalk Server 2009, the hotfix that resolves this issue is included in Cumulative Update 1 for BizTalk Server 2009.�

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:�

2429050 Cumulative update package 1 for BizTalk Server 2009

Hotfix information

For BizTalk Server 2006 R2and BizTalk Server 2009

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have BizTalk Server 2006 R2 or BizTalk Server 2009 installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix. However, you must restart the BizTalk Server host instance after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace other hotfixes.

File information

The 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.

For all supported versions of BizTalk Server 2006 R2

For all supported versions of BizTalk Server 2009

For BizTalk Server 2006 R2 SP1

The hotfix that resolves this problem is included in cumulative update package 1 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:
For more information about BizTalk Server 2006 R2 SP1 hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

This issue is a known issue for BizTalk Server. For more information, visit the following Microsoft Developer Network (MSDN) Web site: For more information about how to add a Catch Exception block, visit the following MSDN Web site:For more information about how to configure tracking for an orchestration, visit the following MSDN Web site: For more information about BizTalk Server hotfixes, click the following article number to view the article in the Microsoft Knowledge Base: An orphaned BizTalk DTA service instance may also be created unexpectedly when you use configure backup transport options for a send port. To resolve this issue, apply cumulative update package 2 for BizTalk Server 2006 R2 Service Pack 1. For more Information, click the following article numbers to view the article in the Microsoft Knowledge Base: