PRB: Interceptor Object Error in XLANG Schedule When You Instantiate .NET Components (323157)



The information in this article applies to:

  • Microsoft BizTalk Server 2000
  • Microsoft BizTalk Server 2002

This article was previously published under Q323157

SYMPTOMS

When you try to run a BizTalk Orchestration schedule that contains at least one COM+ component that is written by using Visual Studio .NET, you may receive the following error message in the BizTalk Server Application event log:
The XLANG Scheduler Engine was unable to create an interceptor 
object for the interface ID shown in the following message.
Probable causes for this are 1) the interface isn't registered 
properly; 2) no type library is provided for the interface; or 
3) the file that contains the interface type information can't be loaded.

The port name associated with this interceptor is: Port2dotNet
Error Code = 0x80029c4a : Error loading type library/DLL.
IID: {0E0CBBB5-AC2B-4FFF-BA24-20427D4F39FC}

XLANG Scheduler Engine Internals Information:
File: d:\bizet\private\sked\src\runtime\techbind\com\combinder\IBindingExecutionContext.cpp
Line: 1073
					
When this error occurs, you cannot run XLANG schedules that contain COM+ components that have been written using Visual Studio .NET on your BizTalk server.

CAUSE

This problem can occur if you call .NET components from within your schedule and the version of Microsoft Data Access Components (MDAC) on your BizTalk server is not MDAC 2.7 or later.

RESOLUTION

Upgrade the version of MDAC on your BizTalk server to MDAC 2.7 or later. To install the latest version of MDAC, visit the following Microsoft Web site:

STATUS

This behavior is by design.

Modification Type:MajorLast Reviewed:6/4/2003
Keywords:kbprb KB323157