Microsoft KB Archive/281176

= BUG: Multi-Document Interchange May Log Ambiguous Information Errors =

Article ID: 281176

Article Last Modified on 10/22/2003

-

APPLIES TO


 * Microsoft BizTalk Server 2000 Standard Edition

-



This article was previously published under Q281176



SYMPTOMS
Your Microsoft BizTalk Server may send documents to the Suspended Queue without a matching entry in the Event Viewer. The error description for the document instance in the Suspended Queue is similar to the following:

The document extracted from the incoming data did not contain enough information to locate a channel.



CAUSE
When you submit a document to the BizTalk Server for processing, the BizTalk Server locates a channel to process the document. This channel selection can happen in one of two ways:
 * The channel name is explicitly supplied in the Receive function or in the call to Interchange.Submit. -or-


 * The channel name is not explicitly supplied but derived indirectly from the supplied source and destination organization identifiers and supplied document definition.

If the channel name is not explicitly supplied then BizTalk scans the InterChangeBTM database to locate a channel with a document definition that matches the supplied document definition. If the interchange that you submitted to BizTalk Server contains multiple document instances and one or more of the instances has a root node that is referred to by more than one document definition, then Microsoft BizTalk Server cannot determine to which channel to submit the document instance.



RESOLUTION
There is no workaround at this time.



STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.



MORE INFORMATION
The issue described in this article occurs because the document instance in question has a root node element that is shared between multiple document definitions. These document definitions might have the same file specification as their reference property or there might exist multiple file specifications that use the same root node element name.

If the same document instance is submitted as a single document, then in addition to the Suspended Queue entry, you receive the following event log message in the Event Viewer:

Event Type: Error

Event Source: BizTalk Server

Event Category: Document Processing

Event ID: 324

Description:

An error occurred in BizTalk Server.

Details:

--

The property set is ambiguous because documents &quot;CommonPO&quot; and &quot;CommonPO2&quot; refer to the same property set and have reference &quot;http://server/BizTalkServerRepository/DocSpecs/Microsoft/CommonPO.xml&quot;.

The property set was empty.

The server could not load any documents with the given criteria.

Document #1 within submission &quot;{738E8937-53B6-4244-BD73-3B118B880CBF}&quot; was returned as a document that was not valid from the parser component named &quot;BizTalk.ParserXML.1&quot;. The most frequent cause is a document specification that is not valid or else the component was unable to determine the necessary routing fields. Verify that the proper specification is defined for this data.

NOTE: In the preceding example error, CommonPO and CommonPO2 are document definitions as defined in the BizTalk Messaging Manager.

Keywords: kbbug kbnofix KB281176

-

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

© Microsoft Corporation. All rights reserved.