Orphaned BizTalk DTA service instances are not removed by the "DTA Purge and Archive" job in BizTalk Server

BizTalk Health Monitor (BHM) reports Orphaned DTA Service Instances or the Monitor BizTalk Server SQL Server Agent job fails with an error message that resembles the following:

Step ID: 2
Job Name: Monitor BizTalk Server (BizTalkMgmtDb)
Step Name: Generate error string in case of any issue
Duration: 00:00:00
Sql Severity: 11
Sql Message ID: 50000
Retries Attempted: 0
Executed as user: BTSSQLAGENTUSER. 550 Orphaned DTA Service Instances in BTSSQLSERVER.BizTalkDTADb [SQLSTATE 42000] (Error 50000). The step failed.

These orphaned DTA service instances are never removed by the DTA Purge and Archive job. Therefore, the BizTalkDTADb database can become very large.

Cumulative update information

The fix that resolves this issue is included in Cumulative Update 5 for BizTalk Server 2013.

Note After you install this update, you must manually update the DTA Purge and Archive job definition to pass the additional parameter @fHardDeleteRunningInstances if you want to clean up running service instances that are older than @nHardDeleteDays. By default, this new parameter is set to 0. This continues the current behavior. If you require the new behavior, set this parameter to 1.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

ID do Artigo: 3194293 - Última Revisão: 10/10/2016 21:27:00 - Revisão: 1.0

Microsoft BizTalk Server 2013 Branch, Microsoft BizTalk Server 2013 Developer, Microsoft BizTalk Server 2013 Enterprise, Microsoft BizTalk Server 2013 Standard

  • kbqfe kbsurveynew kbfix kbexpertiseinter KB3194293