PRB: Error Message: The Parser Cannot Parse the ISA Section of the X12 Document (326775)



The information in this article applies to:

  • Microsoft BizTalk Server 2002

This article was previously published under Q326775

SYMPTOMS

When you try to process an X12 document by using BizTalk messaging, you may receive an error message similar to the following in the Application log of your BizTalk Server:
Event Type: Error
Event Source: BizTalk Server
Event Category: Document Processing
Event ID: 324
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.

[0x1448] The parser cannot parse the ISA section of the X12 document. This segment is fixed-width; if fields in this segment do not have correct length, the parsing will fail because the delimiters are picked up from the wrong offsets.

[0x1440] While trying to process document #0 during submission "{1B69D580-49FB-4FAA-98DC-45493616F72D}", the parser component named "BizTalk.ParserX12.1" failed on the method "GetInterchangeDetails" with the error code "0xc0c01448". 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: "{BCAF8B2E-6E8C-4FBB-B3D2-BFAAC0B3B979}"

[0x1448] The parser cannot parse the ISA section of the X12 document. This segment is fixed-width; if fields in this segment do not have correct length, the parsing will fail because the delimiters are picked up from the wrong offsets.

CAUSE

This problem occurs because an XML character that is not valid is used as either the field or sub-field delimiter. BizTalk Server converts all documents to an XML format during processing. If the documents contain XML characters that are not valid, you receive the error message in the "Symptoms" section.

RESOLUTION

Service Pack Information

To resolve this problem, obtain the latest service pack for Microsoft BizTalk Server 2002. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

815781 How to Obtain the Latest BizTalk Server 2002 Service Pack

Hotfix Information

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date          Time    Version      Size      File name
   --------------------------------------------------------------
   26-Jul-2002   14:57   3.0.1531.0   712,976   Cisparser.dll
   26-Jul-2002   14:57   3.0.1531.0   504,080   Validatedoc.dll
   11-Apr-2002   16:40   1.0.0.2       33,040   Hotfixsetup.exe
   26-Jul-2002   15:22                    578   Qfehotfix.ini
   26-Jul-2002   15:09                309,248   Qfepatch.msp
   26-Jul-2002   15:10                  7,168   Qfeunpatch.msp
   26-Jul-2002   15:10                    753   Bts2002.xml
   26-Jul-2002   15:10                    718   Cbts2002.xml
   26-Jul-2002   15:10                    368   Notifybts2002.xml
				

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft BizTalk Server 2002 Service Pack 1.

Modification Type:MinorLast Reviewed:10/12/2005
Keywords:kbHotfixServer kbQFE kbBizTalk2002SP1fix kbprb KB326775 kbAudDeveloper