Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. FIX: No ACK or NAK is returned when you process an invalid MSH3 message in BizTalk 2010 Accelerator for HL7

FIX: No ACK or NAK is returned when you process an invalid MSH3 message in BizTalk 2010 Accelerator for HL7

View products that this article applies to.

Symptoms

When you process an invalid MSH3 message whose source party does not exist in Microsoft BizTalk 2010 Accelerator for HL7 (BTAHL7), you notice that no ACK or NAK message is returned. Therefore, the upstream system continues to wait until it times out.

↑ Back to the top

Cause

The issue occurs because no ACK or NAK message is generated when an MSH3 message that contains an invalid source party is submitted to BizTalk Server 2010.

↑ Back to the top

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 website:
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.

This hotfix is for BizTalk Server 2010, and it includes the following fixes:
  • HL7: Messages that contain invalid MSH should now be sent an ACK or NAK.

    If the MSH3 field is not valid, and if the MSH15 and MSH16 fields are null or empty, an ACK or NAK is not generated. The MSH3 file is not valid if the corresponding party is not configured in the HL7 configuration explorer. After you apply this hotfix, a NACK is generated if a new registry setting that is named ReturnErrorForInvalidMSH3 is set to 1.

    Note To generate the ACK or NAK in HL7 2010, create the ReturnErrorForInvalidMSH3 registry key, and set its value to 1. To do this, use the following method:
    • Create a DWORD type registry entry that is named "ReturnErrorForInvalidMSH3" in one of the following registry subkeys.

      For 32-bit (x86) operating systems:

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BizTalk Accelerator for HL7\Version 2010
      For 64-bit (x64) operating systems:

      HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\BizTalk Accelerator for HL7\Version 2010
    Notes:
    • Make sure to restart the host instance after you create this registry entry.
    • Applications can subscribe to the failed messages by using the following filter condition:

      BTAHL7Schemas.ParseError = True
    • Set the pipeline to pass-through status for the port that is subscribed to the failed messages.

↑ Back to the top

More Information

Prerequisites to install the software update

To apply this hotfix, you must have the following software installed:Note You can refer to the Readme.txt file of this hotfix for more information about how to install this hotfix. If any issue occurs that requires you to uninstall BTAHL7, uninstall BTAHL7, and then reinstall HL7 by including all the listed hotfixes in the specified order.

Restart requirements

You do not have to restart the computer after you apply this hotfix. However, we recommend that you close and reopen the BizTalk Admin Console after the hotfix is installed.

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.
File nameFile versionFile sizeDateTimePlatform
Microsoft.Solutions.BTAHL7.PipelineCommon.dll3.9.583.292864

04-Jun-2014		03:34x86
Microsoft.Solutions.BTAHL7.HL72fDasm.dll3.9.583.2105152

04-Jun-2014		03:34x86

↑ Back to the top

Status

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

↑ Back to the top

References

For more information about BizTalk Server hotfixes, see Information about BizTalk Server hotfixes .

For more information about software update terminology, see Description of the standard terminology that is used to describe Microsoft software updates .

Third-party information disclaimer
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

↑ Back to the top

Keywords: kb, kbfix, kbqfe, kbsurveynew, kbexpertiseadvanced, kbautohotfix, kbhotfixserver

↑ Back to the top

Article Info
Article ID : 2884547
Revision : 1
Created on : 1/7/2017
Published on : 5/18/2015
Exists online : False
Views : 460