Consider the following scenario on a computer that is running Microsoft BizTalk Server 2006 R2:
You apply the hotfix that is described in Microsoft Knowledge Base (KB) article 967765. Or, you apply BizTalk Server 2006 R2 Service Pack 1 (SP1), which contains the hotfix.
For more information about the hotfix, click the following article numbers to view the articles in the Microsoft Knowledge Base:
967765 FIX: A Business Activity Monitoring (BAM) activity does not track the first message of a batch in BizTalk Server 2006 R2
974563 List of Microsoft BizTalk Server hot fixes that are included in BizTalk Server 2006 R2 Service Pack 1
You create a BizTalk receive location that uses a custom receive pipeline. Additionally, the custom receive pipeline contains the Flat File disassembler pipeline component.
You create and then deploy a Business Activity Monitoring (BAM) activity.
In Tracking Profile Editor (TPE), you create a tracking profile that is based on the BAM activity definition.
You apply this tracking profile.
In this scenario, BAM tracking does not work for the messages that are received through this receive location. Therefore, when you open the BAM table in the BAMPrimaryImport database, you cannot find a tracking record entry. Additionally, you cannot find any corresponding information in the TDDS_FailedTrackingData table.
This problem occurs because of an issue with the Flat File disassembler.
The hotfix for this problem is included in cumulative update package 1 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:
982061 Cumulative update package 1 for BizTalk Server 2006 R2 Service Pack 1
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about BAM, visit the following Microsoft TechNet Web site: