Consider the following scenario in Microsoft BizTalk Server 2006 R2 or BizTalk Server 2009:
You use the Call Orchestration shape in an orchestration to call another orchestration.
You specify an out orchestration parameter in the Call Orchestration Configuration dialog box.
The caller orchestration receives an incoming message, and then the shape returns the called orchestration.
In this scenario, the called orchestration instance is suspended. Additionally, an error message that resembles the following is logged in the application event log:
Event Type: Error Event Source: XLANG/s Event Category: None Event ID: 10034 Description: Uncaught exception (see the 'inner exception' below) has suspended an instance of service '<service name>'. 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: <instance ID> Shape name: <Shape name> ShapeId: <Shape ID> Exception type: NullReferenceException Source: Microsoft.XLANGs.Engine Target Site: Void SetXPath (System.String, System.Object, Microsoft.XLANGs.RuntimeTypes.ValueFormatter, Boolean) The following is a stack trace that identifies the location where the exception occured.
This problem occurs because of an error in the XLANG engine in BizTalk Server 2006 R2 or BizTalk Server 2009.
Cumulative update information
For BizTalk Server 2009, the hotfix that resolves this issue is included in Cumulative Update 1 for BizTalk Server 2009.
For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2429050 Cumulative update package 1 for BizTalk Server 2009
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 the problem described in this article. 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.
You must have the German version of BizTalk Server 2006 R2 installed to apply this hotfix.
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace other hotfixes.
The German 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.
Fix for German version of BizTalk Server 2006 R2
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 the call orchestration shape, visit the following Microsoft Developer Network (MSDN) Web site: