Symptoms
Consider the following scenario:
-
You install one of the following updates on a computer that is running Microsoft BizTalk Server 2010:
-
Cumulative update package 1 for BizTalk Server 2010
-
Cumulative update package 2 for BizTalk Server 2010
-
-
You create a receive location that uses the PassThruReceive pipeline to process XML documents. No schema is associated with XML documents.
-
You create and then deploy a Business Activity Monitoring (BAM) activity.
-
You create a tracking profile to link the BAM activity definition.
-
You associate some fields of the BAM activity to the receive port properties. Note The receive location belongs to the receive port.
-
You apply the tracking profile.
-
An XML document arrives at the receive location.
In this scenario, the XML document is suspended unexpectedly. Additionally, an error message that resembles the following is logged in the Application log:
Log Name: ApplicationSource: BizTalk ServerDate: <Date>Event ID: 5753Task Category: BizTalk ServerLevel: ErrorKeywords: ClassicUser: N/AComputer: <Computer name>Description:A message received by adapter "<Adapter Name>" on receive location "<Receive location>" with URI "<URI>" is suspended. Error details: An output message of the component "Unknown " in receive pipeline "<Receive pipeline name>" is suspended due to the following error: The disassembler cannot retrieve the document specification using this type: "<Type namespace>". This is because the schema is not deployed correctly. . The sequence number of the suspended message is 1. MessageId: {GUID} InstanceID: {GUID}
Note This issue also occurs when you use a custom receive pipeline that has no disassembler pipeline component defined.
Cause
This issue occurs because of a regression that is included in cumulative update package 1 for BizTalk Server 2010 and in cumulative update package 2 for BizTalk Server 2010. When the issue occurs, the pipeline tries to load a disassembler pipeline component unexpectedly. Additionally, the pipeline tries to load a message schema that does not exist. Therefore, the issue that is mentioned in the "Symptoms" section occurs.
Resolution
Cumulative update information
The hotfix that resolves this issue is included in cumulative update package 3 for BizTalk Server 2010. 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:
2617149 Cumulative update package 3 for BizTalk Server 2010
More Information
This hotfix also resolves the following issue.A receive location that uses the File adapter cannot delete files on a computer that has cumulative update package 1 for BizTalk Server 2010 or cumulative update package 2 for BizTalk Server 2010 installed. This issue usually occurs when the following conditions are true:
-
The PassThruReceive pipeline is used at the receive location.
-
BAM tracking is enabled.
-
You configure the file receive adapter to rename files while you process these files.
When this issue occurs, an event that resembles the following is logged:
Log Name: ApplicationSource: BizTalk ServerDate: <Date>Event ID: 7169Task Category: BizTalk ServerLevel: ErrorComputer: <ComputerName>Description:The FILE receive adapter cannot delete file D:\Test\input\modi.txt.BTS-WIP. This file processed successfully.Please delete this file from the disk. Error code: 0x80070005
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
For more information about the File adapter, visit the following MSDN website:
General information about the File adapterFor information about the service packs and cumulative update list for BizTalk Server, click the following article number to view the article in the Microsoft Knowledge Base:
2555976 Service pack and cumulative update list for BizTalk Server For more information about BizTalk Server hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:
2003907 Information about BizTalk Server hotfixes
