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: You cannot use a dynamic port to process some XmlDocument messages that do not have type definitions in BizTalk Server 2006 R2 SP1


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You�install Microsoft BizTalk Server 2006 R2 Service Pack 1 (SP1). Or, you apply the hotfix that is described in the following Microsoft Knowledge Base (KB) article:

    968654� �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.
  • You have a BizTalk orchestration that produces System.Xml.Xmldocument messages�that do not have type definitions.
  • You create a dynamic send port to process the Xmldocument messages that are sent by the orchestration.
  • The orchestration receives an incoming message on the receive port. The message contains a DOCTYPE header that includes a Document Type Definition (DTD).�
In this scenario, the message that is sent from the orchestration is suspended. Additionally, an error that resembles the following is logged in the Application log:

Event Type: Error
Event Source: XLANG/s
Event Category: None
Event ID: 10024

Description:
Uncaught exception (see the 'inner exception' below) has suspended an instance of service '<service instance name>'.
The service instance will remain suspended until administratively resumed or terminated.
If resumed the instance will continue from its last persisted state and may re-throw the same unexpected exception.
InstanceId: <instance id>
Shape name: <shape name>
ShapeId: <shape ID>
Exception thrown from: segment 1, progress 15
Inner exception: The value assigned to property 'BTS.MessageType' is not valid: 'http://schemas.microsoft.com/BizTalk/2003/Any#Root'.

Exception type: InvalidPropertyValueException
Source: Microsoft.XLANGs.BizTalk.Engine
Target Site: Microsoft.BizTalk.Agent.Interop.IBTMessage PrepareMessage(Microsoft.XLANGs.BaseTypes.XLANGMessage, System.Collections.IList, System.Col

↑ Back to the top


Cause

This problem occurs because the BizTalk XLANG engine populates the MessageType context property for messages that do not have type definitions after hotfix 968654 or BizTalk Server 2006 R2 SP1 is installed. Because the document type is also defined in the DTD, the processing error occurs.

↑ Back to the top


Resolution

The hotfix that resolves this problem is included in cumulative update package 2 for BizTalk Server 2006 R2 Service Pack 1.

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:

2211420� Cumulative update package 2 for BizTalk Server 2006 R2 Service Pack 1

↑ 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


References

How to configure backup transport pptions for a send port

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
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


For more information about the list of Microsoft BizTalk Server hotfixes that are included in BizTalk Server 2006 R2 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:�
974563� List of Microsoft BizTalk Server hot fixes that are included in BizTalk Server 2006 R2 Service Pack 1

↑ Back to the top


Keywords: KB2224213, kbfix, kbhotfixserver, kbqfe, kbautohotfix

↑ Back to the top

Article Info
Article ID : 2224213
Revision : 2
Created on : 8/20/2010
Published on : 8/20/2010
Exists online : False
Views : 270