FIX: Error message "Fatal error encountered in EDI Disassembler" is logged in the Application event log when you receive an HIPAA 837 Professional document that contains more than 50 occurrences of Loop 2400 in BizTalk Server 2006 R2
You use Microsoft BizTalk Server 2006 R2 to receive Health Insurance Portability and Accountability Act (HIPAA) messages.
You receive an 837 Professional document.
The 837 Professional document contains more than 50 occurrences of the Loop 2400 service line.
In this scenario, the document is suspended. Additionally, you find event 4097, event 5719 and event 5753 logged in the Application event logs as follows:
Event ID: 4097: Fatal error encountered in EDI Disassembler, error information is Unexpected end of file has occurred. The following elements are not closed: ns0:TS837Q1_2300_Loop, ns0:TS837Q1_2000B_Loop, ns0:TS837Q1_2000A_Loop, ns0:X12_00401_837_P. Line 1, position <number>.
Event ID: 5719 There was a failure executing the receive pipeline: "Microsoft.BizTalk.Edi.DefaultPipelines.EdiReceive, Microsoft.BizTalk.Edi.EdiPipelines, Version=188.8.131.52, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "EDI disassembler" Receive Port: "<receive port>" URI: "<URI>" Reason: Unexpected end of file has occurred. The following elements are not closed: ns0:TS837Q1_2300_Loop, ns0:TS837Q1_2000B_Loop, ns0:TS837Q1_2000A_Loop, ns0:X12_00401_837_P. Line 1, position 288006.
Event ID: 5753 A message received by adapter "<Adapter>" on receive location "<Receive Location>" with URI "<URI>" is suspended.
Loop 2400 should not occur more than the maximum limit of 50 times in an 837Professional document. Therefore, the expected result is that the 837Professional document is suspended with a validation error.
This problem occurs because of an error in the EDI components of BizTalk Server 2006 R2.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
You must have Microsoft BizTalk Server 2006 R2 installed to apply this hotfix.
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
The English version of this hotfix has the file attributes (or later file attributes) 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 item in Control Panel.
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about BizTalk Server 2006 R2 Electronic Data Interchange (EDI) tutorials, visit the following Microsoft Web site: