Hotfix rollup for Miscellaneous issues for BizTalk Server 2013

Symptoms

Issue 1:

This hotfix adds support for MSH7 datetime type in HL7 v2.7 in Microsoft BizTalk 2013 Accelerator for HL7 (BTAHL7).

Issue 2:

An invalid ORU^R01 message can be processed successfully.

Issue 3:

If BizTalk server receives an HL7 batch that contains an FHS segment, you receive an error message that resembles the following:

Issue 4:

Consider the following scenario:

• You are using Microsoft BizTalk 2013 Accelerator for HL7 (BTAHL7).

• You are using MLLP receive adapter and HL7 receive pipeline in a two-way receive port.

• You use the MLLPSEND utility to send messages. For example: MLLPSEND /SB 11 /EB 28 /CR 13 /p 12000 /f "c:\labs\ADT^A03-Good.txt /twoway /repeat 100."

• You stop the SSO service that stops all of BTS related processes when the MLLPSEND utility is executing.

In this scenario, all the messages that contain "Message Status = Queued (awaiting processing)" and "Service Status = Active" before starting the host instance. However, when you restart the SSO service and BizTalk host instance, everything except ACK (CA) messages are not processed and remain in active. The ACK shows with a "Message Status = Consumed" and "Service Status = Active."

Issue 5

Consider the following scenario:

• You are using Microsoft BizTalk 2013 Accelerator for HL7 (BTAHL7).

• You process an invalid MSH3 message whose source party does not exist.

In this scenario, you may find that neither ACK nor NAK is returned, thus the upstream system just sits there waiting until it times out.

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=supportNote 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.

Note For Issue 4, in HL7 2013, for the ACK or NAK to be generated following registry key need to be created with the following value: Set ReturnErrorForInvalidMSH3 registry key to 1 to ensure ACK or NAK is generated, use this method:

• Create a registry entry of type DWORD and name it "ReturnErrorForInvalidMSH3" in one of the following registry sub-keys:
  For 32-bit (x86) operating system:
  
  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BizTalk Accelerator for HL7
  
  For 64-bit (x64) operating system:
  
  HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\BizTalk Accelerator for HL7

Notes:

• Make sure to restart the host instance once the above registry is set.

• Application can subscribe to the failed messages with the following filter condition:
  BTAHL7Schemas.ParseError = True.

• Set the pipeline to "Pass Through" for the port that is subscribed to the failed messages.

More Information

Status

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

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.