Symptoms
Consider the following scenario:
-
You use a dynamic send port to send AS2 messages in Microsoft BizTalk Server 2010.
-
You specify the Receipt-Delivery-Option header for incoming AS2 messages.
-
You process lots of AS2 messages.
In this scenario, the Message Disposition Notification (MDN) is routed to the wrong URL when different Receipt-Delivery-Option HTTP header values are specified in different incoming messages.
Cause
This issue occurs because there is a code defect in ASDecoder component when multiple instances are changing the same Protocol Settings object, and there are different values of Async MDN URI in incoming messages.
Resolution
Cumulative update information
This issue was first fixed in the following cumulative update of BizTalk Server:
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.