FIX: Some BAM events are not tracked for a batch of messages if continuation is defined in the tracking profile in BizTalk Server 2006 R2

Consider the following scenario in Microsoft BizTalk Server 2006 R2:

• You create and then deploy some Business Activity Monitoring (BAM) activities.
• In the Tracking Profile Editor (TPE), you create a tracking profile that contains continuation. You apply this tracking profile.
  Note For detailed instructions about how to create a continuation, see the "More Information" section.

In this scenario, when a batch of messages is received by BizTalk Server 2006 R2, not all BAM events are tracked. Instead, the events are tracked only for the last message. The events are not tracked for previous messages, or for consecutive messages. Therefore, when you open the BAM table in the BAMPrimaryImport database, you cannot find tracking record entries for consecutive messages. Additionally, you cannot find corresponding information in the TDDS_FailedTrackingData table.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have BizTalk Server 2006 R2 installed to apply this hotfix.

Restart information

You do not have to restart the computer after you apply this hotfix. However, you must restart the BizTalk service process (Btsntsvc.exe).

Registry information

You do not have to change the registry.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about how to create a continuation, visit the following Microsoft Developer Network (MSDN) Web site:

For more information about activity continuation, visit the following Microsoft Developer Network (MSDN) Web site:
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: