Assume that you install Microsoft BizTalk Server 2010 on a computer. Then, you run the "DTA Archive and Purge SQL Server Agent" job to archive and delete tracking data from the BizTalk Tracking (BizTalkDTADb) database. In this situation, orphaned rows are created in the dta_ServiceInstanceExceptions table of the BizTalkDTADb database. The issue typically occurs when a message instance is resumed and then fails again. This behavior generates multiple rows that have the same uidServiceInstanceId and uidActivityId variables in the dta_ServiceInstanceExceptions table.
Notes
Notes
- The orphaned rows are identified by Monitor BizTalk Server (BizTalkMgmtDb) as orphaned DTA service instance exceptions.
- The orphaned rows are in the dta_ServiceInstanceExceptions table and have no corresponding rows in dta_ServiceInstances table.
- The orphaned rows are never cleaned up.