BizTalk Server 2016 TDDS issue

Copper Contributor

Infra detail of Biztalk server enviornment

 

Multi node enviornment (one node is primary and another one is joined to that group)

MSSQL server database- BizTalk db's are distributed in two servers (MSSQL Server Instance1: BizTalkmsgboxDB & BizTalkmgmtDB, MSSQL Server Instance 2: BizTalkDTADb & SSODB).

 

In our enviornment BiztalkTalk server logging a error message in Event log for every 9-10Min.

 

Error message:

 

Either another TDDS is processing the same data or there is an orphaned session in SQL server holding TDDS lock.Either another TDDS is processing the same data or there is an orphaned session in SQL server holding TDDS lock. SQLServer: xxxxx, Database: BizTalkDTADb.

Permissions are properly granted as per the microsoft documents and also from the blogs, but issue is still exist.

 

Please check and give me the suggestion.

3 Replies

@naveen_b_N please check [BizTalkDTADb].[dbo].[TDDS_FailedTrackingData] table to see if there are rows with more detailed information about the TDDS failures.

 

Please note sometimes the root cause of a TDDS error could be pretty complicated and it's impossible to perform very comprehensive investigation in the community. Hence I'd also suggest you should consider create a support ticket to Microsoft CSS for resolution:

Contact https://support.microsoft.com/help/13948/global-customer-service-phone-numbers 

@naveen_b_N please check [BizTalkDTADb].[dbo].[TDDS_FailedTrackingData] as is mentioned in previous reply, check size of tracking data, check whether SQL jobs are correctly, especially TrackedMessages_Copy_BizTalkMsgBoxDb / DTA Purge and Archive (BizTalkDTADb).

 

I found also useful info on https://docs.microsoft.com/en-us/archive/blogs/biztalknotes/errors-during-biztalk-tdds-processing

 

@naveen_b_N Have you installed and run BizTalk Health Monitor? That can help to see if there are any issues.