FIX: A message of the System.Xml.Xmldocument type that is sent from an orchestration is suspended and a routing failure report is generated when you specify the Direct Binding type for the ports in the orchestrations in BizTalk Server 2006 R2


Consider the following scenario in Microsoft BizTalk Server 2006 R2:
  • You have a BizTalk application that uses orchestrations that construct new messages of the System.Xml.Xmldocumenttype.
  • You specify the Direct Binding type for the ports in the orchestrations.
In this scenario, a message that is sent from these orchestrations is suspended and a routing failure report is generated. When you query the Suspended service instances field on the Group Hub page in BizTalk Server Administration Console, you may find the MessageType property is lost.

  • A routing failure report is a special message that is generated by BizTalk Server. This message does not have a body. However, this message has the context of the failed message.
  • The MessageType property indicates the message type of the failed message. BizTalk Server uses the message type to associate messages with their XML schemas.


This problem occurs because of a problem in the BizTalk XLANG engine. The BizTalk XLANG engine does not persist the MessageType property during orchestration dehydration. Also, the XLANG engine does not save the type information for messages of the System.Xml.Xmldocument type in the XLANG metadata cache. Therefore, when the orchestration rehydrates, the
MessageType property is lost, and the message is suspended. Then, you receive the routing failure report that is described in the "Symptoms" section.


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 Web site: 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.


You must have Microsoft BizTalk Server 2006 R2 installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

Warning After you have applied the hotfix, the MessageType property is always promoted if you have a message of System.Xml.Xmldocument type. There is no switch for this behavior. You should make sure that your subscription design accounts for all System.Xml.Xmldocument messages having a MessageType, regardless if a schema was deployed for your BizTalk application.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
File nameFile versionFile sizeDateTimePlatform
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.


To work around this problem, use one of the following options:
  • Force the execution of the default XML Receive pipeline on the Construct Message shape and on the Message Assignment shape in orchestration.
  • Specify the following element in the BTSNTSvc.exe.config or BTSNTSvc64.exe.config file:
    <Dehydration NeverDehydrate="true"> </Dehydration>

    • This option may cause an increase in memory consumption. Therefore, you should use this option carefully.
    • By default, the BTSNTSvc.exe.config file and the BTSNTSvc64.exe.config file are located in the following folder:
      <drive>:\Program Files\Microsoft BizTalk Server 2006
      Note <drive> is a placeholder for the hard disk on which BizTalk Server 2006 is installed.

      On 64-bit servers, the 32-bit versions of the files and the 64-bit versions of the files are located in the following folder:

      C:\Program Files (x86)\


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

More Information

For more information about failed message routing, visit the following Microsoft Web site: For more information about orchestration dehydration and rehydration, visit the following Microsoft Web site: For more information about how to configure the dehydration properties in the BTSNTSvc.exe.config file, visit the following Microsoft Web site:
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Article ID: 968654 - Last Review: Apr 7, 2010 - Revision: 1