COM Interop cannot properly deal with a disconnected stub

Retired KB Content Disclaimer

View products that this article applies to.

This article was previously published under Q325699

Expand all | Collapse all

SYMPTOMS

When you call to an earlier COM component from managed code, you may experience an InvalidCastException exception if the activated COM component idles for more than nine minutes. The following is a typical stack for this exception:

Exception: Caught exception:
System.Reflection.TargetInvocationException:
Exception has been thrown by the target of an invocation. --->
System.InvalidCastException:
QueryInterface for interface xxx failed.
at yyy
--- End of inner exception stack trace ---
at System.Reflection.RuntimeMethodInfo.InternalInvoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean isBinderDefault, Assembly caller, Boolean verifyAccess)
at System.Reflection.RuntimeMethodInfo.InternalInvoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean verifyAccess)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.Reflection.MethodBase.Invoke(Object obj, Object[] parameters)
at yyy in zzz.cs:line nn

(Where xxx is the target interface name, yyy is target method name, and then zzz is the source module that implements the interface.)

Back to the top

CAUSE

After several successful calls, the server stub runs down. This occurs after about nine minutes of idle time. The SafeQueryInterface call returns with an HRESULT data type of 0x80010114. 0x80010114 means that

The requested object does not exist

. However, interoperability with COM (COM interop) did not correctly handle the HRESULT: 0x80010114.

Back to the top

RESOLUTION

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next .NET Framework service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. The English version of this fix has the file attributes (or later) 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
   ---------------------------------------------------------
   29-Aug-2002  01:47  1.0.3705.354  2,269,184  Mscorsvr.dll
   29-Aug-2002  01:48  1.0.3705.354  2,265,088  Mscorwks.dll

Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Back to the top

MORE INFORMATION

For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:

265173 (http://support.microsoft.com/kb/265173/EN-US/ ) The Datacenter Program and Windows 2000 Datacenter Server Product

For more information about how to install multiple hotfixes with one restart, click the following article number to view the article in the Microsoft Knowledge Base:

296861 (http://support.microsoft.com/kb/296861/ ) How to install multiple Windows updates or hotfixes with only one reboot

Back to the top

APPLIES TO

Microsoft .NET Framework 1.0 Service Pack 2

Back to the top

kbhotfixserver kbbug kbfix kbnetframe100presp3fix kbqfe KB325699

Back to the top

Retired KB Content Disclaimer

This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.

Back to the top