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: 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.Make sure that you deploy the required Outbound Map .dll file, and then install the file to the global assembly cache (GAC) by using the following properties:
- OutboundMap Assembly Name
This property must include the full name of the assembly in which the outbound map is hosted. You can locate this information in the properties of the map in the BizTalk Server Admin console. This information describes the assembly and also the complete name that is required for OutboundMap Name.
For example: Outbound, Version=1.0.0.0, Culture=neutral, PublicKeyToken=83f92b3673c9005d - OutboundMap Name
This property must include the full the map name. This includes the namespace. You can locate this information in the properties of the *.btm file (Namespace.TypeName).
For example: Outbound.Map1
Note These properties are applied only if
Direct Synchronous HL7 ACK is set to "True."
You might not require the HL7 Disassembler (DASM) in the HL7 Receive pipeline to automatically generates HL7 acknowledgements. For example, the ACK that is generated by some downstream system is to be handed to an upstream system. In this case, turn off "Route ACK to send pipeline on Request Receive port" for the source party, and set
Use Direct Synchronous HL7 ACK to "False." Then, use the outbound map option that is provided in the receive port.
For Issue 1
You cannot track the ACK that is sent to the upstream system by having
Use Direct Synchronous HL7 ACK set to "True." However, if you want to track the content of the ACK that is transmitted to the upstream system, you can use the same tracking mechanism that was used to track the ACK that was sent by a two-way receive port to the upstream system in the absence of the
Use Direct Synchronous HL7 ACK setting. This assumes that the same map is used in the MLLP Receive location configuration properties and also in the standard Outbound Map feature in the receive port setting that is provided by BizTalk Server.
For Issue 2
After you install the hotfix, the behavior will be based on the Acceptable ACK code that you select in the drop-down list instead of the code that is provided by the downstream system.
If the ACK code is listed under the selected acceptable code, the message processing succeeds and the processing runs again for standard ACK codes that are not listed in the selected
Acceptable ACK Codes and in case of nonstandard ACK codes that are not listed in the selected
Acceptable ACK Codes, message is suspended.
Note If the downstream system returns AA or CA codes, message processing always succeeds regardless of any acceptable ACK code option that is set in the port configuration.
The ACK schema must be modified by adding the acceptable custom ACKs. If the additional custom ACKs are not added to the schema, the pipeline validation fails and returns a “table value not found” error message. Any additional acceptable custom ACKs must be added to the
MSA.1_AcknowledgementCode existing list of ACKs.