Article ID: 968654 - View products that this article applies to.
Consider the following scenario in Microsoft BizTalk Server 2006 R2:
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 informationA 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:
PrerequisitesYou must have Microsoft BizTalk Server 2006 R2 installed to apply this hotfix.
Restart requirementYou do not have to restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace a previously released hotfix.
File informationWarning 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.
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.
Collapse this tableExpand this table
To work around this problem, use one of the following options:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about failed message routing, visit the following Microsoft Web site:
http://msdn.microsoft.com/en-us/library/aa578516.aspxFor more information about orchestration dehydration and rehydration, visit the following Microsoft Web site:
http://msdn.microsoft.com/en-us/library/dd800372.aspxFor more information about how to configure the dehydration properties in the BTSNTSvc.exe.config file, visit the following Microsoft Web site:
http://msdn.microsoft.com/en-us/library/dd801219.aspxFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 968654 - Last Review: April 7, 2010 - Revision: 2.0
Contact us for more help
Connect with Answer Desk for expert help.