Symptoms
Consider the following scenario:
-
You have a computer that is running Microsoft BizTalk Server 2010, or Microsoft BizTalk Server 2006 R2 Service Pack 1 (SP1).
-
The AS2 Decoder decrypts an encrypted Applicability Statement 2 (AS2) or an encrypted Electronic Data Interchange (EDI) message.
-
The AS2 or EDI message does not have a MIME Content-Type header.
In this scenario, the AS2 Decoder cannot decrypt the message. Additionally, the following events are logged in the Application log:Event 1
Event Type: WarningEvent Source: BizTalk Server 2006 EDIEvent Category: NoneEvent ID: 8132Description:An error was encountered when attempting to generate an AS2 status report. Error: Object reference not set to an instance of an object. Event 2
Event Type: ErrorEvent Source: BizTalk Server 2006Event Category: BizTalk Server 2006 Event ID: 5719Description:There was a failure executing the receive pipeline: "Microsoft.BizTalk.EdiInt.DefaultPipelines.AS2Receive, Microsoft.BizTalk.Edi.EdiIntPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "Pipeline " Receive Port: "<receive port>" URI: "<URI>" Reason: The Messaging Engine encountered an error while reading the message stream. Event 3
Event Type: ErrorEvent Source: BizTalk Server 2006Event Category: BizTalk Server 2006 Event ID: 5753Description:A message received by adapter "HTTP" on receive location "<receive location>" with URI "<URI>" is suspended. Error details: There was a failure executing the receive pipeline: "Microsoft.BizTalk.EdiInt.DefaultPipelines.AS2Receive, Microsoft.BizTalk.Edi.EdiIntPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "Pipeline " Receive Port: "<receive port>" URI: "<URI>" Reason: The Messaging Engine encountered an error while reading the message stream.
Cause
This issue occurs because the AS2 Decoder does not treat messages that do not contain a MIME Content-Type header as plain text (US-ASCII).Note According to a Request for Comments (RFC) memorandum that defines a standard for messages that do not contain MIME Content-Type headers, a default content-type should be assumed. The RFC states that any message that does not contain a MIME Content-Type header should be treated as a plain text (US-ASCII) message. This content-type is specifically defined as the following:
Content-type: text/plain; charset=us-ascii
Resolution
Cumulative update information
BizTalk Server 2010For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2497789 Cumulative update package 1 for BizTalk 2010
BizTalk Server 2006 R2The hotfix that resolves this issue is included in cumulative update package 4 for BizTalk Server 2006 R2 SP1. 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:2682056Cumulative update package 4 for BizTalk Server 2006 R2 SP1
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 website:
http://support.microsoft.com/contactus/?ws=supportNote 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
To apply this hotfix, you must have Microsoft BizTalk Server 2006 R2 SP1 installed.
Restart requirement
After you apply this hotfix, you do not have to restart the computer. However, you must restart the BizTalk host instance service.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
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 name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Microsoft.biztalk.edi.messagecore.dll |
3.6.2229.12 |
350,088 |
25-Jan-2011 |
11:07 |
x86 |
|
Microsoft.biztalk.edi.pipelinecomponents.dll |
3.6.2229.12 |
190,352 |
25-Jan-2011 |
11:07 |
x86 |
|
Microsoft.biztalk.edi.reporting.common.dll |
3.6.2229.12 |
25,488 |
25-Jan-2011 |
11:07 |
x86 |
|
Microsoft.biztalk.edi.reporting.dll |
3.6.2229.12 |
55,168 |
25-Jan-2011 |
11:07 |
x86 |
|
Microsoft.biztalk.edi.shared.dll |
3.6.2229.12 |
161,656 |
25-Jan-2011 |
11:07 |
x86 |
|
Microsoft.biztalk.ediint.pipelinecomponents.dll |
3.6.2229.12 |
128,920 |
25-Jan-2011 |
11:07 |
x86 |
|
Microsoft.biztalk.ediint.reporting.dll |
3.6.2229.12 |
34,696 |
25-Jan-2011 |
11:07 |
x86 |
|
Microsoft.biztalk.messaging.dll |
3.6.2229.12 |
92,024 |
25-Jan-2011 |
11:07 |
x86 |
|
Microsoft.biztalk.pipeline.components.dll |
3.6.2229.12 |
292,752 |
25-Jan-2011 |
11:07 |
x86 |
|
Microsoft.biztalk.pipeline.dll |
3.6.2229.12 |
292,728 |
25-Jan-2011 |
11:07 |
x86 |
|
Microsoft.biztalk.streaming.dll |
3.6.2229.12 |
51,064 |
25-Jan-2011 |
11:07 |
x86 |
|
Microsoft.biztalk.xpathreader.dll |
3.6.2229.12 |
79,744 |
25-Jan-2011 |
11:07 |
x86 |
|
Microsoft.xlangs.basetypes.dll |
3.6.2229.12 |
104,312 |
25-Jan-2011 |
11:07 |
x86 |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
For more information about AS2 receive components, visit the following Microsoft Developer Network (MSDN) website:
General information about AS2 receive componentsFor more information about MIME RFCs, visit the following webpage:
General information about MIME RFCsFor more information about BizTalk Server hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:
2003907 Information on BizTalk Server hotfixes
