FIX: Pipeline execution fails when you deploy BAM tracking profile to the send port or receive port in BizTalk Server

Applies to: BizTalk Server 2013 R2 BranchBizTalk Server 2013 R2 DeveloperBizTalk Server 2013 R2 Enterprise


Symptom 1:
Assume that you deploy a Business Activity Monitoring (BAM) tracking profile against the AS2 send port in Microsoft BizTalk Server. When the process tries to match the outgoing Message Integrity Check (MIC) with the incoming MIC, the following integrity check error is logged in the Application log:

The AS2 Decoder failed processing when validating the MIC value returned in the MDN. Details of the MDN message are as follows: AS2-From:"<XXX>" AS2-To:"<XXX>" MessageID:"<XXX>" OriginalMessageID:"<XXX>".
Symptom 2:
Assume that you are using MLLP adapter and BTAHL7 2010. BAM tracking profile that references BTAHL7 messaging payload schemas is applied on the receive port. Pipeline execution fails and you receive the following error message:
A pipeline component in the receive pipeline:<ReceivePipelineName> is using the message context properties <PropertiesName> in a unsupported fashion. The pipeline processing is being terminated.


Cumulative update information

This issue was first fixed in the following cumulative update of BizTalk Server:


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.