FIX: "xlang/s engine event log entry: Exceptions.Types.InterceptorException" error message when you run a BizTalk orchestration after you upgrade BizTalk Server 2006 R2 to BizTalk Server 2009

This article has been archived. It is offered "as is" and will no longer be updated.
Consider the following scenario on a computer that is running Microsoft BizTalk Server 2006 R2 or BizTalk Server 2009:  
  • You use correlations in a BizTalk orchestration.
  • You set the orchestration transaction type to Long Running.
  • You have an orchestration instance that is either active or dehydrated. Additionally, the orchestration is waiting to receive a correlating message.
  • You upgrade BizTalk Server 2006 R2 to BizTalk Server 2009.
  • After the upgrade is complete, the BizTalk orchestration receives the correlating message.
In this scenario, an error that resembles the following is logged in the Application log:

Event Type: Error
Event Source: XLANG/s
Event Category: None
Event ID: 0
Description: xlang/s engine event log entry: Exceptions.Types.InterceptorException Value cannot be null.

Exception type: ArgumentNullException
Source: mscorlib
Target Site: Void Enter (System.Object)

Note This issue does not occur for BizTalk orchestrations that are created after the upgrade.

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

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.

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 Server 2009 installed to apply this hotfix.

Restart requirement

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.

Hotfix replacement information

This hotfix does not replace 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.
File nameFile versionFile sizeDateTimePlatform
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Call stack information

The following stack trace identifies the location in which the exception occurs:
at System.Threading.Monitor.Enter(Object obj)at Microsoft.XLANGs.Mozart.NativeInterceptor.BasicTracking(EventData data, Location loc, Stream trackData)at Microsoft.XLANGs.Mozart.NativeInterceptor.TrackEventHandler(Location loc, EventData data, Stream trackData)at Microsoft.XLANGs.Core.Events.FireEvent(Location location, EventData args, ITrackStreamDispenser trackData)
To obtain the upgrade guide that contains information about how to upgrade to BizTalk Server 2009, visit the following Microsoft Web site: For more information about how to upgrade a BizTalk orchestration, visit the following Microsoft Developer Network (MSDN) Web site: For more information about how to use correlations in orchestrations, visit the following MSDN Web site: For more information about BizTalk Server hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:
2003907 Information on BizTalk Server hot fixes
BizTalk 2009 upgrade XLang InterceptorException kbbiztalk2009cu1fix

Article ID: 980950 - Last Review: 12/12/2015 03:36:25 - Revision: 2.0

Microsoft BizTalk Server 2009 Branch, Microsoft BizTalk Server 2009 Developer, Microsoft BizTalk Server 2009 Enterprise, Microsoft BizTalk Server 2009 Standard

  • kbnosurvey kbarchive kbbtsorchestration kbbiztalk2009presp1fix kbexpertiseadvanced kbautohotfix kbsurveynew kbqfe kbHotfixServer KB980950