Article ID: 961023 - View products that this article applies to.
Symptom 1When the Microsoft BizTalk Accelerator for HL7 (BTAHL7) receives an HL7 message type, you see an event log entry that resembles the following:
Event Type: Information
Symptom 2In a batch-in-batch-out (BIBO) scenario, if any message in the batch contains a parsing error, the whole batch is suspended.
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:
PrerequisitesYou must have Microsoft BizTalk Server 2006 R2 and the BizTalk Accelerator for HL7 2.0 installed to apply this hotfix.
Restart requirementYou do not have to restart your computer. However, you have to restart BizTalk Service(s) after apply this hotfix. For detailed installation instructions, please refer to the Readme.txt file that is included in the hotfix package.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
Installation informationWhen you install this hotfix, you may receive the following error message:
This problem occurs because the installer may clear the existing credentials. To resolve this problem, follow these steps:
Error 1920. Service Auditing and Logging Service (btsaalsvc) failed to start. Verify that you have sufficient privileges to start system services.
File informationThe 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.
Collapse this tableExpand this table
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This hotfix provides both .dll updates and user interface changes that resolve the problems that the “Symptoms” section describes.
Fix for symptom 1To prevent the excessive logging of event 4119, an Event Log Successfully Received Message option is available on the Global Settings tab under BTAHL7 Configuration Explorer.
When only the Event Log option is enabled, BizTalk Server creates warning event logs and error event logs. When the Event Log Successfully Received Message option is also enabled, BizTalk Server creates information event logs that contain event ID 4119 according to the following table:
Collapse this tableExpand this table
Fix for symptom 2To address the BIBO issue, a Recoverable interchange support required option is available on the Batch Definition tab under BTAHL7 Configuration Explorer.
When this option is set to True, processing completes even when a parsing error occurs in a message in the batch. BizTalk Server delivers successfully parsed messages in one batch. Additionally, BizTalk Server generates an acknowledgement (ACK) message. BizTalk Server individually suspends the unsuccessfully parsed messages. BizTalk Server generates a single ACK message to identify the errors for all the individually suspended messages.
For more information about the BIBO issue, see the BTAHL7 tutorials. To do this, visit the following Microsoft Developer Network (MSDN) Web site:
Article ID: 961023 - Last Review: March 25, 2009 - Revision: 1.0
Contact us for more help
Connect with Answer Desk for expert help.