FIX: MDNs are not sent to the sending party in BizTalk Server 2006 R2

Consider the following scenario:

• On a computer that has Microsoft BizTalk 2006 R2 installed, you use the AS2EDIReceive pipeline to receive and process Applicability Statement 2 (AS2) messages from your trading partners.
• You configure the receive port to receive the AS2 messages, and synchronously send a Message Disposition Notification (MDN) to the sending party.
• You receive an incoming AS2 message that is not parsed correctly by the EDI pipeline components.

In this scenario, the AS2 message will be suspended, and the MDN is not sent to the sending party as expected.

For example, in BizTalk Server you receive an AS2 message whose field delimiter/separator and segment delimiter/separator are the same. In this situation, the AS2 message will be suspended because of a parsing error. Additionally, you will receive an application event log that resembles the following:

Event Type: Error
Event Source: BizTalk Server 2006
Event ID: 5719
Description:
There was a failure executing the receive pipeline: "Microsoft.BizTalk.EdiInt.DefaultPipelines.AS2EdiReceive, Microsoft.BizTalk.Edi.EdiIntPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "EDI disassembler" Receive Port: "<Receive Port>" URI: "<URI>" Reason: Delimiters are not unique, field and segment seperator are the same

When this problem occurs, the MDN is not sent to the sending party as expected.

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 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.

For a walkthrough of how to configure receiving EDI over AS2 with a synchronous MDN, 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: