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: Pipeline errors occur when you use BAM tracking in BizTalk Server 2010 CU7


View products that this article applies to.

Symptoms

When you use the Business Activity Monitoring (BAM) tracking profile in Microsoft BizTalk Server 2010 Cumulative Update 7 (CU7), the following event entries for pipeline errors are logged in the Application log:

Log Name: Application
Source: BizTalk Server
Date: <Date> <Time>
Event ID: 5753
Task Category: BizTalk Server
Level: Error
Computer: <Computer Name>
Description:
A message received by adapter "FILE" on receive location "<Receive Location Name>" with
URI "<File Path>" is suspended.
Error details: There was a failure executing the receive pipeline: "<Pipeline Name>" Source: "Pipeline "
Receive Port: "<Receive Port Name>" URI: "<File Path>" Reason: An error occurred when parsing
the incoming document: "Unexpected XML declaration. The XML declaration must be the first node in the
document, and no white space characters are allowed to appear before it. Line 61, position 16.".
MessageId: {<GUID>}
InstanceID: {<GUID>}

Log Name: Application
Source: BizTalk Server
Date: <Date> <Time>
Event ID: 5719
Task Category: BizTalk Server
Level: Error
Computer: <Computer Name>
Description:There was a failure executing the receive pipeline: "<Pipeline Name>" Source: "Pipeline "
Receive Port: "<Receive Port Name>" URI: "<File Path>" Reason: An error occurred when parsing
the incoming document: "Unexpected XML declaration. The XML declaration must be the first node in the
document, and no white space characters are allowed to appear before it. Line 61, position 16."

↑ Back to the top


Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Cumulative update information

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

Prerequisites

To apply this hotfix, you must install the BizTalk Server 2010 Cumulative Update 7 (CU7).

↑ 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


Keywords: kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseadvanced, kb

↑ Back to the top

Article Info
Article ID : 3047071
Revision : 1
Created on : 1/7/2017
Published on : 8/17/2015
Exists online : False
Views : 364