You have a send pipeline that uses the MIME/SMIME encoder pipeline component in Microsoft BizTalk Server 2006 R2 or in Microsoft BizTalk Server 2009. You set the signature type of the MIME/SMIME encoder pipeline component to ClearSign.
You create a BizTalk orchestration that runs the send pipeline to sign outgoing messages.
For example, you use an expression to call the send pipeline of a message assignment shape in the orchestration. For more information, see to the "More Information" section.
You install Microsoft BizTalk Server 2006 R2 Service Pack 1 (SP1). Or, you upgrade to Microsoft BizTalk Server 2010.
You run the BizTalk orchestration.
In this scenario, the outgoing messages are not signed. Additionally, an error message that resembles the following is logged in the Application log:
There was a failure executing the send pipeline: "<pipeline name>" Source: "MIME/SMIME encoder" Send Port: "<send port name>" URI name" Reason: Unable to sign outbound message because the encoder could not find the signing certificate in the "Current User\Personal" certificate store.
This issue occurs because BizTalk Server tries to locate a certificate in an incorrect location.
Note BizTalk Server 2006 R2 SP1 and BizTalk Server 2010 introduce a new feature that lets you use multiple certificates for signing.
Cumulative update package information
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:
2573000 Cumulative update package 2 for BizTalk Server 2010
Note If you encounter this issue in BizTalk Server 2006 R2 SP1, you can follow the steps in the "Workaround" section to work around this issue.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
To work around this issue, following these steps:
Use the following namespace to deploy a property schema: