FIX: A Request Response Receive Location that uses an MLLP adapter does not work correctly if you configure the per-instance pipeline properties for the custom send pipeline when you use Microsoft BizTalk 2009 Accelerator for HL7

Consider the following scenario,

• On a computer that is running Microsoft BizTalk Server 2009, you have installed Microsoft BizTalk 2009 Accelerator for HL7(BTAHL7).
• In BTAHL7 Configuration Explorer, you enable the option "Route ACK to send pipeline on request-response receive port", and you set Acknowledgement type to "OriginalMode" for an HL7 trading party.
• You create a Request Response Receive Location that uses a Minimal Lower Layer Protocol (MLLP) adapter to receive HL7 messages.
• You use a custom pipeline as a send pipeline for the Request Response Receive Location, and you configure the per-instance pipeline properties for the custom pipeline.

In this scenario, the per-instance pipeline properties do not take effect during message processing. Therefore, BTAHL7 does not promote the necessary properties to process the Acknowledgements (ACK). When this occurs, the Request Response Receive Location does not work as expected.

This problem occurs because of an error in Microsoft BizTalk 2009 Accelerator for HL7. Because of this error, ACKs are not processed correctly.

When the MLLP receive adapter operates in two-way mode, the adapter will not receive a new message from the connection until the pipeline has generated the acknowledgement (ACK) for the previous message. Therefore, the Request Response Receive Location described in the "Symptoms" section does not work as expected.

Apply this hotfix to address the problem. For detailed steps, refer to the Readme.txt file that is included in this hotfix package.

Hotfix information

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.

Prerequisites

You must have BizTalk Server 2009 and BizTalk 2009 Accelerator for HL7 installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix. However, you must restart the BizTalk Host Instance service after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

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.Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

To work around this problem, set the Acknowledgement type to "None" in BTAHL7 Configuration Explorer for the HL7 trading party. In this manner, the ACKs will be processed correctly with the Configuration of the Per-instance Pipeline Properties. Therefore, the Request Response Receive Location works as expected.

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

For more information about MLLP receive adapter processing, visit the following Microsoft Developer Network (MSDN) Web site:

For more information about how to configure the per-instance pipeline properties for a receive location, visit the following Microsoft Developer Network (MSDN) Web site:
For more information, click the following article number to view the article in the Microsoft Knowledge Base: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: