You are currently offline, waiting for your internet to reconnect

FIX: An error message occurs when BizTalk Server receives an MDN that does not contain the Message-ID field in the HTTP header: "System.ArgumentException: Empty parameter string not allowed"

SYMPTOMS
Consider the following scenario:
  • You use Microsoft BizTalk Server 2006 R2 to send AS2 messages.
  • On the AS2 Properties configuration page for the partner, on the "Party as AS2 Message Receiver" tab, you have enabled the “Require MDN” setting.
  • The Message Disposition Notification (MDN) response that is sent from the partner does not contain the Message-ID field in the HTTP header.

Note The Message-ID field contains a unique identifier which refers to the current version of the message. The uniqueness of the message identifier is guaranteed by the host that generates the MDN response.
In this scenario, you receive an Application event log that resembles the following:

Event Type: ErrorEvent Source: BizTalk Server 2006 EDIEvent Category: NoneEvent ID: 4112Description:System.ArgumentException: Empty parameter string not allowed.Parameter name: MessageIDat Microsoft.BizTalk.Edi.Reporting.Common.Utilities.ValidateArgument(Object o, String parameterName, Boolean isEmptyStringValidationRequired)at Microsoft.BizTalk.Edi.Reporting.Common.Utilities.ValidateArgument(String s, String parameterName, Boolean isEmptyStringValidationRequired, Int32 maxLength)at Microsoft.BizTalk.EdiInt.Reporting.AS2BaseActivity.ValidateParameters()at Microsoft.BizTalk.EdiInt.Reporting.AS2MdnActivity.ValidateParameters()at Microsoft.BizTalk.EdiInt.Reporting.AS2MdnActivity.Create()

CAUSE
BizTalk Server checks if the Message-ID HTTP header field exists when BizTalk Server receives the MDN response. However, according to RFC2298 and RFC822, the Message-ID is an optional field. Therefore, if other AS2 servers send an MDN response that does not contain the Message-ID header property, BizTalk Server raises an error.
RESOLUTION

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.
File nameFile versionFile sizeDateTimePlatform
Microsoft.biztalk.ediint.reporting.dll3.6.1484.237,94421-Aug-200812:09x86
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.
WORKAROUND
To work around this problem, use one of the following two methods:
  • Do not use MDN when you send AS2 messages from the BizTalk Server. To do this, clear the "Require MDN" property in the "Party as AS2 Message Receiver" tab on the AS2 Properties configuration page for the partner.
  • Make sure that your partner uses an Electronic Data Interchange (EDI) system that includes the Message-ID in the MDN response.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
For more information about AS2 support in BizTalk Server 2006 R2, visit the following Microsoft Developer Network (MSDN) Web site:

For more information about RFC822, visit the following Internet Engineering Task Force (IETF) Web site:

For more information about RFC2298, visit the following Internet Engineering Task Force (IETF) Web site:
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
EDI AS2 MDN BizTalk 2006 R2 MessageID
Properties

Article ID: 956916 - Last Review: 08/13/2009 06:16:26 - Revision: 1.1

Microsoft BizTalk Server 2006 R2 Standard Edition, Microsoft BizTalk Server 2006 R2 Enterprise Edition, Microsoft BizTalk Server 2006 R2 Developer Edition, Microsoft BizTalk Server 2006 R2 Branch Edition

  • kbbtsadapters kbautohotfix kbbiztalk2006r2sp1fix kbexpertiseinter kbfix kbhotfixserver kbqfe KB956916
Feedback
">amp;did=1&t=">