Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

FIX: Failed messages are routed incorrectly by a send port that has BAM tracking enabled in BizTalk Server 2006 R2 or in BizTalk Server 2009


View products that this article applies to.

Symptoms

Consider the following scenario:
  • 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>
In this scenario, the message is routed incorrectly by the send port. An event 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: 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:,,,
Notes:
  • 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�.

↑ Back to the top


Resolution

Cumulative update information

Cumulative 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:
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 Service Pack 1 (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:
2211420 Cumulative update package 2 for BizTalk Server 2006 R2 Service Pack 1
For more information about BizTalk Server 2006 R2 SP1 hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:
974563 List of Microsoft BizTalk Server hot fixes that are included in BizTalk Server 2006 R2 Service Pack 1
For more information about BizTalk Server hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:
2003907 Information on BizTalk Server hotfixes

↑ Back to the top


Status

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

↑ Back to the top


More information

For more information about how to track failed messages in BAM, visit the following Microsoft Developer Network (MSDN) website:

↑ Back to the top


Keywords: kbbiztalk2006r2presp1fix, kbbtsbam, kbfix, kbqfe, kbsurveynew, kbexpertiseadvanced, kbbiztalk2009presp1fix, KB983387

↑ Back to the top

Article Info
Article ID : 983387
Revision : 5
Created on : 3/22/2011
Published on : 3/22/2011
Exists online : False
Views : 453