FIX: Orphaned DTA service instances are generated by the backup transport in BizTalk Server 2006 R2 or in BizTalk Server 2009

Article translations Article translations
Article ID: 2153742 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario:
  • You are using a computer that is running Microsoft BizTalk Server 2006 R2 or in BizTalk Server 2009.
  • You configure backup transport options for a send port.
  • The primary transport does not process an incoming message. Then, the backup transport process the message correctly.
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.

RESOLUTION

Cumulative update information

Cumulative update informationThe hotfix that resolves this issue is included in cumulative update package 2 for BizTalk Server 2009.

For more informationabout how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2497794 Cumulative update package 2 for BizTalk Server 2009

The hotfix that resolves this problem is included in cumulative update package 2 for BizTalk Server 2006 R2 Service Pack 1.

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:

2211420 Cumulative update package 2 for BizTalk Server 2006 R2 Service Pack 1

STATUS

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

REFERENCES

How to Configure Backup Transport Options for a Send Port

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
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


For more information about the list of Microsoft BizTalk Server hot fixes that are included in BizTalk Server 2006 R2 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
974563 List of Microsoft BizTalk Server hot fixes that are included in BizTalk Server 2006 R2 Service Pack 1

Properties

Article ID: 2153742 - Last Review: March 18, 2011 - Revision: 2.0
APPLIES TO
  • Microsoft BizTalk Server 2006 R2 Branch Edition
  • Microsoft BizTalk Server 2006 R2 Developer Edition
  • Microsoft BizTalk Server 2006 R2 Enterprise Edition
  • Microsoft BizTalk Server 2006 R2 Standard Edition
  • Microsoft BizTalk Server 2009 Branch
  • Microsoft BizTalk Server 2009 Developer
  • Microsoft BizTalk Server 2009 Enterprise
  • Microsoft BizTalk Server 2009 Standard
Keywords: 
kbautohotfix kbqfe kbhotfixserver kbfix kbbiztalk2009presp1fix KB2153742

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com