PRB: "Additional Data in the Document Instance Was Not Parsed" Error Message While Parsing Flat File Documents (814416)



The information in this article applies to:

  • Microsoft BizTalk Server 2002
  • Microsoft BizTalk Server 2000

SYMPTOMS

When BizTalk Server validates a delimited flat file document that contains positional records, and the records are not in the order specified in the validating schema, an error message similar to the following appears in the BizTalk Server application log:
Event Type:			Error
Event Source:			BizTalk Server
Event Category:			Document Processing 
Event ID:			324
Computer:			BIZTALKSERVER
Description:
An error occurred in BizTalk Server.
 
 Details:
 ------------------------------
 [0x1433] The parser failed to convert the document due to processing errors. See the following messages for details.

 [0x1440] While trying to process document #1 during submission "{8A902B5E-6948-47E8-9A3D-48965E75B430}", 
 the parser component named "BizTalk.ParserFFile.1" failed on the method "GetInterchangeDetails" with the error code 
 "0xc0c01433". Possible causes are: the component found unexpected data in the incoming stream; a document 
 specification could not be found given the data; or an internal component failure occurred. If this problem continues, 
 remove this component from the valid list of parser components or contact your system administrator.

 [0x1730] Suspended Queue ID: "{8C2CFEB9-EAF4-4A8A-AD56-225CE8E537C8}"

 [0x1433] The parser failed to convert the document due to processing errors. See the following messages for details.
Additionally, when you try to validate a flat file by using BizTalk Server Editor, and the file has out-of-order records, you receive the following error message in the Editor:
Additional data in the document instance was not parsed. Make sure that the document instance you want to validate contains only one document. The parser failed to convert the document due to processing errors. See the following messages for details.

CAUSE

This error can occur when the BizTalk flat file parser is parsing a flat file where the records are not in the order that is specified in the schema. Because the BizTalk flat file parser does not reorder records when parsing them, all out-of-order records are considered superfluous data. These records cause the document that is being parsed to fail validation.

WORKAROUND

To work around this problem, do one of the following:
  • Enforce a business rule to make sure that all documents that BizTalk Server processes contain records that are in the order that is specified in the schema.

    -or-
  • Write a preprocessor to rearrange the records in the document so that they are in the correct order before the document is submitted to BizTalk.

STATUS

This behavior is by design.

Modification Type:MajorLast Reviewed:6/4/2003
Keywords:kberrmsg kbprb KB814416 kbAudDeveloper