FIX: Messaging properties are not tracked for some messages in an interchange in Microsoft BizTalk Server 2006 R2 or BizTalk Server 2009

Consider the following scenario in Microsoft BizTalk Server 2006 R2 or BizTalk Server 2009:

• You configure a receive location by using the XMLReceive pipeline.
• 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 select some properties from the Messaging Property Schema to map the data item folders of the activity, and then you apply this tracking profile.

In this scenario, when a batch of messages passes through the XMLReceive pipeline, you find that the messaging properties are not tracked for some messages in the batch. Specifically, if there is a map for the XMLReceive pipeline, the messaging properties for the last message is not tracked. Additionally, if there is no map for the XMLReceive pipeline, the messaging properties for the last two messages are not tracked.

For example, you receive the following message from the adapter:

If there is a map defined for the XMLReceive pipeline, after this message passes through the XMLReceive pipeline, the map is applied to produce the following message:

In this example, the PortEndTime messaging property is not tracked for the fourth message. Additionally, the BAM table in the BAMPrimaryImport database contains the following four entries:


Note The <OrderID> element is from the <MyMessage> schema, and the PortEndTime is from the Messaging Properties Schema. These values are defined in the tracking profile.

If there is no map for the XMLReceive pipeline, the PortEndTime messaging property is not tracked for the third and fourth message. Therefore, the BAM table in BAMPrimaryImport database resembles the following:

Note If there is no map for the XMLReceive pipeline, the message is tracked directly from the XMLReceive pipeline.

Cumulative updated information

For BizTalk Server 2009, 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 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 requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released 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.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.

To uninstall this hotfix, follow these steps:

1. Open �Control Panel, click�Add or Remove Programs, and then locate hotfix 970856.
2. Remove hotfix 970856
3. When the uninstall operation is complete, run the following commands by using the Global Assembly Cache tool (Gacutil.exe):

   Gacutil /if Microsoft.BizTalk.GlobalPropertySchemas.dll
   Gacutil /if Microsoft.BizTalk.Messaging.dll
   Gacutil /if Microsoft.BizTalk.Pipeline.Components.dll
   Gacutil /if Microsoft.BizTalk.Pipeline.dll
   

   
   

For more information about BAM, visit the following Microsoft Web site:
For more information about how to install an assembly into the global assembly cache, visit the following Microsoft Web site:
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

Query Word

kbbiztalk2009cu1fix