Hi All,

In one node of our PROD BizTalk server giving continuous warning for "The total number of failed TDDS". I have restarted and stopped tracking host instance sometime then also getting same email notification". Performance count for BizTalk: TDDS -> Total failed event =6.

Please suggest..

Reagrds

Suman

 

Hi Suman ,

Can you verify what is the event log entry in this case . It will give us better idea to tell you what is going wrong within your environment . You also check the dbo.TDDS_FailedTrackingData table in the BAMPrimaryImport database, if there are any entries, the error description will be in the errMessage column.

Thanks

Abhishek

both i had checked ..there is no logs in event viewer and table also empty..

According to http://mpwiki.viacode.com/default.aspx?g=posts&t=164354 the threshold for this counter in the BizTalk Management Pack is 5 (which fit the fact that it was reported as being 6 on the alert). 

Restarting tracking host instances can resolve issue temporarily but as per MS, reducing tracking in your live environment is recommended, which (of course) also make this error disappear.

Refer: SCOM alert on "The total number of failed TDDS batches" but no error details found

both i had checked ..there is no logs in event viewer and table also empty..

Hi Suman ,

Have you validate  BAMPrimaryImport.[dbo].[TDDS_FailedTrackingData] table . There can be potential two reason's 

1) ESB exception management DB"s also used TDDS for getting properties information from BizTalk Prmiary import table . In this case you need to modify certain things.

Under Microsoft.Practises.ESB Application you need to modify the SQL send port .

Right click on this send port and open the pipeline configuration of ESBFaultProcessor Under the sectionStage 1: Encode Component ESB BAM Tracker changed the Enabled settings to False, this is true by default.

2) You need to decrease the level of port tracking which you  have on your individual Application .  I would suggest that on individual host instance used you should remove the tracking and let the default host instance responsible for tracking purpose 

Thanks

Abhishek

both i had checked ..there is no logs in event viewer and table also empty..

Hi Suman ,

Have you validate  BAMPrimaryImport.[dbo].[TDDS_FailedTrackingData] table . There can be potential two reason's 

1) ESB exception management DB"s also used TDDS for getting properties information from BizTalk Prmiary import table . In this case you need to modify certain things.

Under Microsoft.Practises.ESB Application you need to modify the SQL send port .

Right click on this send port and open the pipeline configuration of ESBFaultProcessor Under the sectionStage 1: Encode Component ESB BAM Tracker changed the Enabled settings to False, this is true by default.

2) You need to decrease the level of port tracking which you  have on your individual Application .  I would suggest that on individual host instance used you should remove the tracking and let the default host instance responsible for tracking purpose 

Thanks

Abhishek

• Proposed as answer by Abhishek0127[Abhishek kumar]MVP 13 hours 14 minutes ago

both i had checked ..there is no logs in event viewer and table also empty..

Hi Suman ,

Have you validate  BAMPrimaryImport.[dbo].[TDDS_FailedTrackingData] table . There can be potential two reason's 

1) ESB exception management DB"s also used TDDS for getting properties information from BizTalk Prmiary import table . In this case you need to modify certain things.

Under Microsoft.Practises.ESB Application you need to modify the SQL send port .

Right click on this send port and open the pipeline configuration of ESBFaultProcessor Under the sectionStage 1: Encode Component ESB BAM Tracker changed the Enabled settings to False, this is true by default.

2) You need to decrease the level of port tracking which you  have on your individual Application .  I would suggest that on individual host instance used you should remove the tracking and let the default host instance responsible for tracking purpose 

Thanks

Abhishek

• Proposed as answer by Abhishek0127[Abhishek kumar]MVP Monday, July 06, 2015 5:51 PM
• Marked as answer by Angie xuMicrosoft contingent staff, Moderator 1 hour 42 minutes ago

both i had checked ..there is no logs in event viewer and table also empty..

Hi Suman ,

Have you validate  BAMPrimaryImport.[dbo].[TDDS_FailedTrackingData] table . There can be potential two reason's 

1) ESB exception management DB"s also used TDDS for getting properties information from BizTalk Prmiary import table . In this case you need to modify certain things.

Under Microsoft.Practises.ESB Application you need to modify the SQL send port .

Right click on this send port and open the pipeline configuration of ESBFaultProcessor Under the sectionStage 1: Encode Component ESB BAM Tracker changed the Enabled settings to False, this is true by default.

2) You need to decrease the level of port tracking which you  have on your individual Application .  I would suggest that on individual host instance used you should remove the tracking and let the default host instance responsible for tracking purpose 

Thanks

Abhishek

• Proposed as answer by Abhishek0127[Abhishek kumar]MVP Monday, July 06, 2015 5:51 PM
• Marked as answer by Angie xuMicrosoft contingent staff, Moderator Wednesday, July 08, 2015 5:22 AM

Hi Suman,

Have you created Dedicated Tracking Host for the tracking purpose.