Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
MIME or S/MIME messages that are signed or encrypted are not parsed correctly when you use the MIME/SMIME Decoder in BizTalk Server 2006 R2 or in BizTalk Server 2009
Article ID: 982634 - View products that this article applies to.
Consider the following scenario:
Problem 1The message is suspended. Additionally, an error message that resembles the following is logged in the Application log:
Event Type: Error
Event Source: BizTalk Server 2006
Event Category: BizTalk Server 2006
Event ID: 5753
Description: A message received by adapter "<Adapter Name>" on receive location "<Receive Location Name>" with URI "<URI>" is suspended.
Error details: There was a failure executing the receive pipeline: "<Pipeline name>, <Pipeline assembly name>, Version=126.96.36.199, Culture=neutral, PublicKeyToken=<Token>" Source: "MIME/SMIME decoder"
Receive Port: "<Receive Port Name>" URI: "<URI>" Reason: There was an authentication failure. "Failed to decode the S/MIME message. The S/MIME message may not be valid."
Problem 2The message is received by BizTalk Server 2006 R2. However, the MIME boundary is included as part of the message. Therefore, the message is incorrect.
Note These problems also occur when you use the POP3 adapter in the receive location.
Note:If you use BizTalk Server 2009, the Event Source and Event Category in above events are “BizTalk Server 2009”.
This problem occurs because of an error in the Exsmime.dll file that is included in BizTalk Server 2006 R2. Because of this error, the MIME/SMIME Decoder pipeline component does not correctly parse MIME and S/MIME messages under certain conditions.
Cumulative update informationCumulative update informationThe hotfix that resolves this issue is included in cumulative update package 2 for BizTalk Server 2009.
For more informationabout how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/2497794/ )Cumulative update package 2 for BizTalk Server 2009
The hotfix that resolves this problem is included in Cumulative Update Package 2 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:
2211420For more information about BizTalk Server 2006 R2 SP1 hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/2211420/ )Cumulative update package 2 for BizTalk Server 2006 R2 Service Pack 1
974563For more information about BizTalk Server hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/974563/ )List of Microsoft BizTalk Server hotfixes that are included in BizTalk Server 2006 R2 Service Pack 1
(http://support.microsoft.com/kb/2003907/ )Information about BizTalk Server hotfixes
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 982634 - Last Review: March 18, 2011 - Revision: 5.0