Consider the following scenario. You call a Health Level 7
(HL7) disassembler (DASM) inside an orchestration to validate the HL7 messages.
In this scenario, the following event ID may be logged in the Application log:
Event Type: Error
Event Source: XLANG/s
Event
Category: None
Event ID: 10015
Description:
Uncaught exception
(see the 'inner exception' below) has suspended an instance of service
'MyComponent.Orchestration(41196fda-20c8-80af-e759-66642661634d)'.
The
service instance will remain suspended until administratively resumed or
terminated.
If resumed the instance will continue from its last persisted
state and may re-throw the same unexpected exception.
InstanceId: {GUID}
Shape name: ConstructOutMessage
ShapeId: {GUID}
Exception thrown
from: segment 2, progress 6
Inner exception: The part 'BodySegments' of
message 'MultipartMessage' contained a null value at the end of the construct
block.
Exception type: NullPartException
Source:
Microsoft.XLANGs.Engine
Target Site: Void
ConstructionCompleteEvent(Boolean)
The following is a stack trace that
identifies the location where the exception occurred
at
Microsoft.XLANGs.Core.Part.ConstructionCompleteEvent(Boolean
fKillUnderlyingPart)
at
Microsoft.XLANGs.Core.XMessage.ConstructionCompleteEvent(Boolean
killUnderlyingPartWhenDirty)
at
MyComponent.Orchestration.segment2(StopConditions stopOn)
at
Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s, StopConditions
stopCond, Exception& exp)
For more information, see Help and
Support Center at http://go.microsoft.com/fwlink/events.asp.
Cause 1
An orchestration always wraps the
System. String type as an XML document. In this case, the orchestration adds
extra characters to simulate the XML format. However, the HL7 DASM does not
recognize the extra characters when the input parameter reaches the HL7 DASM
that is called inside an orchestration.
Cause 2
By design, the HL7 DASM generates the ZSegment part of IBase
message that is a string type. However, the XLANG engine that processes the HL7
DASM output message is looking for the XML type. Therefore, this behavior
results in an XLANG exception. Additionally, event ID 10015 is logged in the
Application log.
Hotfix information
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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
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.
Prerequisites
You must have BizTalk Accelerator for HL7 1.3 installed to
apply this hotfix.
Restart requirement
You do not have to restart the computer after you apply this
hotfix.
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.
Collapse this tableExpand this table
| File name | File version | File
size | Date | Time | Platform |
|---|
| Finalmessagecomponent.cs | Not
applicable | 3,744 | 08-Mar-2007 | 23:57 | Not
applicable |
| Messagedecoder.cs | Not
applicable | 4,122 | 08-Mar-2007 | 23:56 | Not
applicable |
| Microsoft software license terms.rtf | Not
applicable | 150,868 | 30-Mar-2007 | 06:44 | Not
applicable |
Cause 1
To fix Cause 1, the Messagedecoder.cs file is released in this
hotfix. The Messagedecoder.cs pre-processor component removes the extra
character that is added by the orchestration. This occurs before the component calls any disassembler
that should receive a string data type as an input parameter.
Cause 2
Because of the HL7 DASM restriction, you have to modify the HL7
DASM output message before it comes back to the orchestration. In this case,
the Finalmessagecomponent.cs file is released in this hotfix to fix Cause 2.
You can use the Finalmessagecomponent.cs post-processor components to convert
the string output into the XML format and to modify the ZSegment message part.
After you have the pre-processor components and the post-processor
components implemented and compiled, you can create a custom pipeline component
to manage the string data types correctly when you call the HL7
DASM.
Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section.