PRB: Parsing Error Occurs When You Validate Document Instance Against a Schema in BizTalk Editor (306313)



The information in this article applies to:

  • Microsoft BizTalk Server 2000

This article was previously published under Q306313

SYMPTOMS

When you attempt to validate a document instance against a schema in the BizTalk Editor, a parsing error similar to the following may occur:
The "123" attribute is not allowed in the "RecordInfo" element.
Line: 8, Pos: 116.
The specification failed to load. See the following messages for details.

CAUSE

The schema contains escaped characters. For example, the following schema attribute contains the escaped characters "123" and causes document validation failures:

tag_name="123"

In this example, the escaped "123" character sequence causes the BizTalk Editor to fail to parse documents.

RESOLUTION

Check the Source Tag Identifier property for all elements in the schema, and make sure that they do not contain escaped characters. The Source Tag Identifier is located on the Parse tab in the BizTalk Editor. If any Source Tag Identifiers are escaped, modify them by removing the quotation marks, so that they are no longer escaped.

STATUS

This behavior is by design. The BizTalk Editor does not support the use of escaped characters for Source Tag Identifiers.

Modification Type:MajorLast Reviewed:10/17/2003
Keywords:kbprb KB306313