- In Microsoft BizTalk Server 2006 R2 or in Microsoft BizTalk Server 2009, you create a receive port and then you enable the�Enable routing for failed messages property on the receive port.
- You create a receive location for the receive port that uses the XMLReceive receive pipeline to receive incoming messages.
- You create a send port that acts as a subscriber for failed messages.
Note For detailed instructions about how to do this, refer to the "How to track failed messages in BAM" in the �More Information� section. - You create and deploy a Business Activity Monitoring (BAM) activity to track the failed messages.
- In Tracking Profile Editor (TPE), you create a tracking profile for the activity and associate the activity with the send port. Then, you apply the tracking profile.
- The BizTalk server receives an ill-formatted XML message. For example, BizTalk server receives a message as follows:
<Items> <Item> Bad message </Item> </Itemse>
Event Type: Error
Event Source: BizTalk Server 2006
Event Category: BizTalk Server 2006
Event ID: 5754
Description:
A message sent to adapter "<Adapter>" on send port "<send port>" with URI "<URI>" is suspended.
Error details: Unable to read the stream produced by the pipeline.
Details: An error occurred when parsing the incoming document:,,,
Event Source: BizTalk Server 2006
Event Category: BizTalk Server 2006
Event ID: 5754
Description:
A message sent to adapter "<Adapter>" on send port "<send port>" with URI "<URI>" is suspended.
Error details: Unable to read the stream produced by the pipeline.
Details: An error occurred when parsing the incoming document:,,,
- This issue occurs even if the send port uses the PassThruTransmit send pipeline.
- This issue does not occur if BAM tracking is disabled on the send port.
- If you use BizTalk Server 2009, the Event Source and Event Category in above events are �BizTalk Server 2009�.