Consider the following scenario:
Note This issue also occurs when you use a custom receive pipeline that has no disassembler pipeline component defined.
- 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.
Log Name: Application
Source: BizTalk Server
Date: <Date>
Event ID: 5753
Task Category: BizTalk Server
Level: Error
Keywords: Classic
User: N/A
Computer: <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}
Source: BizTalk Server
Date: <Date>
Event ID: 5753
Task Category: BizTalk Server
Level: Error
Keywords: Classic
User: N/A
Computer: <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.