Microsoft KB Archive/321773

= PRB: XLANG Scheduler Does Not Understand the Target Namespace =

Article ID: 321773

Article Last Modified on 9/20/2006

-

APPLIES TO


 * Microsoft BizTalk Server 2002 Standard Edition

-



This article was previously published under Q321773



SYMPTOMS
When you try to process a document that contains a namespace with BizTalk Orchestration, you may experience one or both of the following problems:  You can validate an XML document with a target namespace in BizTalk Messaging Manager. However, if you try to validate the same XML document against the same schema in the XLANG Scheduler, the validation is unsuccessful, and you receive error messages that are similar to the following in the BizTalk Server application log:

The Message Queuing message was not successfully validated against the schema that was provided. Check the schema and the schema path.

Instance ID: {3CB76C98-1A69-44EC-B70E-AC9D43964B43} Port name: Port_1 Queue path:bts://&Port_1&.\private$\Port_1{DA60E797-8233-481D-92D4-B5DEB0A3099A} Message type: LoanApplication Message name: LoanApplication

Validate failed because the root element had no associated DTD/schema.

Error Code = 0x80045d26 XLANG Scheduler Engine Internals Information: File: d:\bizet\private\sked\src\runtime\techbind\mq\linda\mqqueue.cpp Line: 1214 For more information, see Help and Support Center at http://support.microsoft.com.

- and -

The Message Queuing message is an invalid or unknown message and was moved to the dead-letter queue.

Instance ID: {3CB76C98-1A69-44EC-B70E-AC9D43964B43} Port name: Port_1 Queue path: bts://&Port_1&.\private$\Port_1{DA60E797-8233-481D-92D4-B5DEB0A3099A} MSMQ Message label: {3CB76C98-1A69-44EC-B70E-AC9D43964B43} XLANG Dead-Letter Queue path:.\private$\XLANG Scheduler.DeadLetter Error Code = 0x80045d2e XLANG Scheduler Engine Internals Information: File:d:\bizet\private\sked\src\runtime\techbind\mq\queue\mqasyncqueue.cpp Line: 1125 For more information, see Help and Support Center at http://support.microsoft.com.

 The data flow between messages in XLANG may work not as expected if the message specification has a target namespace. For example, if you map a constant to a message field on the Data page of the Orchestration Designer, the message field may not be populated as expected when the document is processed if the message specification for the document contains a target namespace.



CAUSE
The target namespace that is used in BizTalk Server schemas is only designed for and understood by BizTalk Messaging Manager. XLANG Scheduler does not understand the target namespace. The target namespace that BizTalk Messaging Manager understands is different from the targetNamespace attribute that is defined in XML Schema definition language (XSD).



STATUS
This behavior is by design.

Additional query words: target namespace

Keywords: kbprb KB321773

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.