FIX: BAM activity data is not written when you run a BizTalk application that uses a WCF-WSHttp send port in BizTalk Server 2009

Consider the following scenario:

• You run a BizTalk application that uses a WCF-WSHttp send port in Microsoft BizTalk Server 2009.
• The send port uses a custom send pipeline.
• The custom send pipeline component of the send pipeline uses Messaging Event Streams to receive tracking data.
• You deploy a Business Activity Monitoring (BAM) activity.
• You apply a BAM activity definition-based tracking profile.
• The BizTalk application processes a message.

In this scenario, the BAM activity data is not written. Additionally, the records in the BAMPrimaryImport database are not moved from the BAM_<Activity_Name>_Active table to the BAM_<Activity_Name>_Completed table.

Cumulative update information

The hotfix that resolves this issue is included in Cumulative Update 1 for BizTalk Server 2009. 

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:

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 website: 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

To apply this hotfix, you must have Microsoft BizTalk Server 2009 installed.

Restart requirement

You do not have to restart the computer after you apply this hotfix. However, you must restart the instance of BizTalk Host after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfix.

File Information

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.

For all supported 32-bit versions of BizTalk Server 2009

For all supported 64-bit versions of BizTalk Server 2009

To work around this issue, use the following configuration:

• Use a send port that uses the WCF-Custom adapter.
• Use the wsHttpBinding binding type for the port.
• Click to select the Use Transaction check box, and then set the Isolation Level list to ReadCommitted.

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

For more information about Messaging Event Streams, visit the following Microsoft Development Network (MSDN) website:
For more information about IPipelineContext.GetEventStream method, visit the following MSDN website:
For more information about how to use BAM, visit the following Microsoft TechNet website:
For more information about BizTalk Server hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:
For more information about how to configure a WCF-WSHttp send port, visit the following MSDN website: