When you configure a BizTalk application to use the SHA256 signing algorithm of Applicability Statement 2 (AS2) messages in Microsoft BizTalk Server, you may notice an unexpected behavior that one AS2 message contains two signatures, or you may receive an error message that resembles the following:
Error details: There was a failure executing the send pipeline: "Microsoft.BizTalk.EdiInt.DefaultPipelines.AS2Send, Microsoft.BizTalk.Edi.EdiIntPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=TokenID" Source: "AS2 encoder" Send Port: PortID URI: FilePath Reason: The MIME encoder failed to sign the message because the certificate has private key protection turned on or the private key does not exist