You have installed Microsoft BizTalk Accelerator for HL7 (BTAHL7) 1.3 on a computer that is running Microsoft BizTalk Server 2006.
You use a BizTalk orchestration to create an HL7 message, and then send the message to a receiving party.
In BTAHL7 1.3 Configuration Explorer, you configure the MSH field to override the MSH3 field for the receiving party.
In this scenario, BizTalk Server 2006 creates the HL7 message successfully. However, BizTalk Server 2006 cannot send the HL7 message to the receiving party. Additionally, the following error is logged in the Application log:
Event Type: Error Event Source: BizTalk Server 2006 Event ID: 5720 Description: A message sent to adapter "FILE" on send port "<Send Port>" with URI "<URI>" is suspended. Error details: There was a failure executing the send pipeline: "BTAHL72XPipelines.BTAHL72XSendPipeline, BTAHL72XPipelines, Version=220.127.116.11, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "BTAHL7 2.X Assembler" Send Port: "<Send Port>" URI: "<URI>" Reason: Value cannot be null.
Note This issue does not occur in messaging scenarios that do not use BizTalk orchestrations.
The issue occurs because of an error in the BTAHL7 assembler.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article.
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, contact 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.
You must have BizTalk Accelerator for HL7 1.3 installed to apply this hotfix. Additionally, before you apply this hotfix, you must install the following two hotfixes that are described in the following Microsoft Knowledge Base (KB) articles. For more information, click the following article numbers to view the KB articles:
935347 FIX: Characters appear as question marks after you handle an input message that contains ISO 8859/1 characters when you use the Microsoft BizTalk Accelerator for HL7 1.3
942769 FIX: Event ID: 5720 may be logged when you use the Message Enrichment Tutorial in BizTalk Accelerator for HL7 1.3
You do not have to restart the computer after you apply this hotfix. However, you must restart the BizTalk Server host instance after you apply this hotfix. 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 other hotfixes.
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.
To work around this issue, use one of the following methods:
Override the MSH3 value in the BizTalk orchestration when the message is created.
Make sure that the MSH segment contains all the MSH fields. This enables BizTalk Server 2006 to override the field that is specified in the MSH Map tab of BTAHL7 1.3 Configuration Explorer.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about how to configure MSH field overrides, visit the following Microsoft Developer Network (MSDN) Web site: