PRB: Error Message: No Parser Component Recognizes the Data (327233)
The information in this article applies to:
- Microsoft BizTalk Server 2002
This article was previously published under Q327233 SYMPTOMS
BizTalk Server moves documents that are processed with a custom parser component to the suspended queue, and the Application log of BizTalk Server generates an error message that is similar to the following:
Event Type: Error
Event Source: BizTalk Server
Event Category: Document Processing
Event ID: 324
Description:
An error occurred in BizTalk Server.
Details:
------------------------------
[0x1439] No parser component recognizes the data. This might be caused by an interchange specification that is missing or not valid, or it might be caused by data that is not valid. Verify that both the interchange specification (if one is specified) and the data match.
[0x1730] Suspended Queue ID: "{65C027FA-C191-4E55-85AA-78CA85773AC0}"
[0x0147] The business document that was passed in is not in a recognized format and could not be parsed or decrypted.
For more information, see Help and Support Center at http://support.microsoft.com.
NOTE: This may occur only when you use a custom parser with the IInterchange::Submit() method. File receive functions operate normally, and successfully pass the data to your custom parser component.
CAUSE
The data that is submitted to BizTalk Server is not encoded in the format that the custom parser component expects. The custom parser component fails using the ProbeInterchangeFormat() method.
RESOLUTION
To resolve this issue, use one of the following methods:
- Method 1: Add code to your custom parser component so that it detects the encoding on the data stream, and converts the encoding if it is different from the encoding that the custom parser component expects.
- Method 2: Make sure that the encoding type of the data that is submitted is the encoding type that the parser component expects.
STATUSThis behavior is by design.MORE INFORMATION
This error occurs if you use the DirectIntegration BizTalk SDK sample to submit a document to BizTalk Server, and the Send as document instead of file option is turned on. If you click this option, you submit Unicode data to BizTalk even if the source file is in ASCII format. Because your parser component expects an ASCII encoded document, you receive the error message that is listed in the "Symptoms" section.
| Modification Type: | Major | Last Reviewed: | 9/22/2006 |
|---|
| Keywords: | kbprb KB327233 |
|---|
|