FIX: Event IDs 5812, 5743, and 5754 are logged when you use BizTalk Accelerator for HL7 2.0 or Microsoft BizTalk Accelerator for HL7 1.3

Considering the following scenario:

• You use the Microsoft BizTalk Accelerator for HL7 2.0 or Microsoft BizTalk Accelerator for HL7 1.3 to create an MLLP send port to receive acknowledgements (ACK).
• In the Transport Advanced Options settings for this port, you enable the "Ordered delivery" option and the "Stop sending subsequent messages on current message failure" option.
• The MSA1 field of the acknowledgement contains a value other than AA or CA.

In this scenario, messages start to queue up, and an event message that resembles the following message is logged in the Application log:

Event Type: Error
Event Source: BizTalk Server 2006
Event Category: BizTalk Server 2006
Event ID: 5812
Description:
The ordered delivery send port: "<Send Port Name>" has stopped processing messages. To rectify the issue please use Biztalk Management Console to find the failed message corresponding to the Send Port Instance ID:"{GUID}" to further diagnose the issue. After fixing the error, please resume the send port instance.

Notes

• You can enable an MLLP static one-way port to receive acknowledgements by specifying the "Solicit Response Enabled" option as Yes, and by specifying an Acknowledgement type in the BizTalk Accelerator for HL7 Configuration Explorer. See the "More Information" section in this article for a link to detailed instructions. The functionality that is documented in this hotfix is available only when you use a static one-way port for which the "Solicit-Response enabled" option is specified as True.
• Depending on your settings in the Acceptable ACK Codes property of the MLLP Send Port Configuration dialog box, you may see the following warning logged in the Application log:

  Event Type: Warning
  Event Source: BizTalk Server 2006
  Event Category: BizTalk Server 2006
  Event ID: 5743
  Description:
  The adapter failed to transmit message going to send port "<Send Port Name>" with URL "<URL>". It will be retransmitted after the retry interval specified for this Send Port. Details:"Acknowledgement type Error was received".

• If this retry attempt fails, and if the acknowledgement that is returned contains an invalid MSA1 field, you receive an error message in Application log that resembles the following message:

  Event Type: Error
  Event Source: BizTalk Server 2006
  Event Category: BizTalk Server 2006
  Event ID: 5754
  Description:
  A message sent to adapter "MLLP" on send port "<Send Port Name>" with URI "<URI>" is suspended. Error details: Acknowledgement type Reject was received MessageId: <GUID> InstanceID: <GUID>

• If the downstream system does not send an acknowledgement message, another attempt is made to resend the message according to the Transport property options (retry count and retry interval) that are specified in the send port. You receive entries in the Application log that resemble the following entry:

  Event Type: Error
  Event Source: BizTalk Accelerator for HL7
  Event Category: None
  Event ID: 8451
  Description:
  Unable to receive ACK from network due to error "MLLP Send adapter timed out while receiving the ACK.".

  Event Type: Warning
  Event Source: BizTalk Server 2006
  Event Category: BizTalk Server 2006
  Event ID: 5743
  Description:
  The adapter failed to transmit message going to send port <send port name> with URL "localhost:18000". It will be retransmitted after the retry interval specified for this Send Port. Details:"MLLP Send adapter timed out while receiving the ACK."

• If no acknowledgement is received after the message attempt is made, the message becomes suspended in the Group Hub of the Microsoft BizTalk Server Administration console. You receive entries in the Application log that identify the port name and the suspended message (event ID 5812 and 5754).

This problem occurs because the BizTalk Accelerator for HL7 treats only the AA and CA codes for MSA1 as valid. Any other MSA1 code is rejected.

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 the BizTalk Accelerator for HL7 1.3 or BizTalk Accelerator for HL7 2.0 installed to apply this hotfix.

Restart requirement

You might be prompted to restart your computer after you apply this hotfix. If you are not prompted, you must restart BizTalk services. For more information about this procedure, refer to the Readme.txt file that is included in the hotfix package.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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.

BizTalk Accelerator for HL7 1.3

BizTalk Accelerator for HL7 2.0

Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.After you apply this hotfix, we provide support for additional ACK codes in addition to AA and CA. These codes are AE, AR, CR, and CE. After you apply this hotfix, these additional MSA1 codes are accepted as valid, and no additional processing is provided to handle these codes.

To work around this problem, you can disable the "Ordered delivery" option and the �Stop sending subsequent messages on current message failure" option on the send port if these options are not required to maintain order.

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

After you apply this hotfiix, a new "Acceptable ACK Codes" setting becomes available in the Transport properties of the MLLP Send Port Configuration dialog box. For compatibility, the default setting is AA and CA. The following code setting options are available for the properties:

• AA and CA
• AA, CA, AE, and CE
• AA, CA, AR, and CR
• All ACK codes

This setting controls the message processing when the following settings are specified:

• Solicit - Response Enabled: Yes
• Ordered delivery: Enabled
• Stop sending subsequent messages on current message failure: Enabled

For more information about how to set up a send port for receiving acknowledgements, visit the following Microsoft Web site:
http://msdn.microsoft.com/en-us/library/bb945754.aspx
For more information about MLLP send adapter processing, visit the following Microsoft Web site:
http://msdn.microsoft.com/en-us/library/bb945744.aspx
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: