FIX: You receive a “NullPartException” error message when you use nested orchestrations in BizTalk Server 2004

This article has been archived. It is offered "as is" and will no longer be updated.

When you use nested orchestrations in Microsoft BizTalk Server 2004, you may receive an error message that is similar to the following:
Uncaught exception terminated service Orchestration.Sample(fb6ac667-e6e6-b899-a292-7c0cfbf0507a), instance b5ee312c-7d00-4fb9-b5b6-b0785cae3947

The part partname of message SomeMessage contained a null value at the end of the construct block.

Exception type: NullPartException
Source: Microsoft.XLANGs.Engine
Target Site: Void CheckNonNull()
This problem occurs if all the following conditions are true:
  • You are using the Call shape in one orchestration to call into a second orchestration.
  • The second orchestration has an OUT parameter that is message String strMsg.
  • The second orchestration is in a different assembly than the first orchestration.

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.


No prerequisites are required.

Restart requirement

After you install this hotfix, you must undeploy, rebuild, and then redeploy the solution.

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 tool in Control Panel.
   Date         Time    Version      Size      File name   ---------------------------------------------------------------   18-Oct-2004  19:53   3.0.5353.0  1,017,856  Xlangscompiler.dll  
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Article ID: 887692 - Last Review: 01/17/2015 09:12:30 - Revision: 2.5

  • Microsoft BizTalk Server 2004 Enterprise Edition
  • Microsoft BizTalk Server 2004 Standard Edition
  • Microsoft BizTalk Server 2004 Partner Edition
  • Microsoft BizTalk Server 2004 Developer Edition
  • kbnosurvey kbarchive kbautohotfix kbbtsorchestration kbbiztalk2004presp1fix kbbug kbfix kbhotfixserver kbqfe KB887692