FIX: You cannot correlate batched EDI/AS2 messages to incoming MDNs in BizTalk Server 2006 R2

Consider the following scenario in Microsoft BizTalk Server 2006 R2:

• You use BizTalk Server to send and receive Electronic Data Interchange (EDI) and AS2 messages.
• You enable batching for the EDI party.
  
  Note For more information about how to enable batching for the EDI party, refer to the "More information" section.
• You use the out-of-box Business Activity Monitoring (BAM) activities in the BAMPrimaryImport database for EDI and AS2 status reporting.

In this scenario,the BAM activity data is not populated to the BAM_AS2interchangeActivity_completed table in the BAMPrimaryImport database as expected after batched outgoing messages are sent from BizTalk Server. Therefore, you cannot correlate the outgoing batched messages to the incoming Message Disposition Notifications (MDNs).

This problem occurs because of an error in the BizTalk Server 2006 EDI components. After batching is enabled for outgoing messages, the interchange control number field is not populated successfully to the BAM_AS2interchangeActivity_completed table. Therefore, the activity tracking data is not generated successfully.

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 Microsoft BizTalk Server 2006 R2 installed to apply this hotfix.

Restart information

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

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 batch outgoing EDI messages, visit the following Microsoft Developer Network (MSDN) Web site:
For more information about BAM activities that are created to track EDI/AS2 messages, 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: