FIX: Batched and unbatched messages log event 4119 as an informational event in BTAHL7, or the whole batch is suspended if any message contains a parsing error

Article translations Article translations
Article ID: 961023 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

Symptom 1

When 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
Event Source: BizTalk Accelerator for HL7
Event Category: None
Event ID: 4119
Description:
An empty batch was received with fragmentation turned on. The 1st 1kb of the message is MSH|^~\&|SOME_SOURCE^^|4265|||...

This problem occurs even if you have disabled the Fragmentation required option for the source party's Incoming Batch field. Therefore, excessive logging may occur. Additionally, a security issue may occur if a confidential message is exposed.

Symptom 2

In a batch-in-batch-out (BIBO) scenario, if any message in the batch contains a parsing error, the whole batch is suspended.

RESOLUTION

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:
http://support.microsoft.com/contactus/?ws=support
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.

Prerequisites

You must have Microsoft BizTalk Server 2006 R2 and the BizTalk Accelerator for HL7 2.0 installed to apply this hotfix.

Restart requirement

You 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 information

This hotfix does not replace any other hotfixes.

Installation information

When you install this hotfix, you may receive the following error message:
Error 1920. Service Auditing and Logging Service (btsaalsvc) failed to start. Verify that you have sufficient privileges to start system services.
This problem occurs because the installer may clear the existing credentials. To resolve this problem, follow these steps:
  1. Open the Services MMC snap-in.
  2. Locate Auditing and Logging Service, and then click the Log On tab.
  3. Update the service account name and password.
  4. Click Retry to continue the installation.

File information

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.
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Btahl7configurationexplorer.exe2.0 .310.0350,07213-Jan- 200901:36x86
Microsoft.solutions. btahl7.auditinglogging.dll2.0.310.051,08013- Jan- 200901:36x86
Microsoft.solutions. btahl7.configuration.dll2.0.310.071,56013- Jan- 200901:36x86
Microsoft.solutions. btahl7.hl72fdasm.dll2.0.310.096,13613-Jan- 200901:36x86
Microsoft.solutions. btahl7.pipelinecommon.dll2.0.310.0 87,94413-Jan- 200901:36x86
Microsoft.solutions. btahl7.shared.dll2.0.310.087,94413-Jan- 200901:36x86
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

This hotfix provides both .dll updates and user interface changes that resolve the problems that the “Symptoms” section describes.

Fix for symptom 1

To 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
Batch or message that BizTalk Server receivesMessage when fragmentation is turned on for the source partyMessage when fragmentation is turned off for the source party
A batch messageA batch was received with fragmentation turned on.A batch was received with fragmentation turned off.
An empty batchAn empty batch was received with fragmentation turned on. The 1st 1KB of the message is {…}A batch was received with fragmentation turned off.
A simple messageA message was received of type {…} A message was received of type {…}

Fix for symptom 2

To 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:
http://msdn.microsoft.com/en-us/library/bb669447.aspx

Properties

Article ID: 961023 - Last Review: March 25, 2009 - Revision: 1.0
APPLIES TO
  • Microsoft BizTalk Server 2006 R2 Standard Edition
  • Microsoft BizTalk Server 2006 R2 Enterprise Edition
  • Microsoft BizTalk Server 2006 R2 Developer Edition
  • Microsoft BizTalk Server 2006 R2 Branch Edition
  • Microsoft BizTalk Accelerator for HL7 1.0 Enterprise Edition
Keywords: 
kbsurveynew kbautohotfix kbbtsaccelerators kbhotfixserver kbqfe KB961023

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com