FIX: ExecutionEngineException Error After a Typical Exception Is Thrown (330900)


The information in this article applies to:

  • Microsoft .NET Framework 1.0 SP2
This article was previously published under Q330900

SYMPTOMS

When you use Microsoft .NET COM Interop, and COM interfaces are being marshaled, a typical exception that occurs when the code runs might cause the marshaled interface to be prematurely cleaned up. If this occurs, when you try to use the interface later, the .NET runtime throws an ExecutionEngineException error.

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 fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

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 typical 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
   ------------------------------------------------------------------
   19-Oct-2002   03:35   1.0.3705.370      69,632   Corperfmonext.dll
   19-Oct-2002   14:23   1.0.3705.370   1,953,792   Mscorlib.dll     
   19-Oct-2002   03:34   1.0.3705.370   2,269,184   Mscorsvr.dll     
   19-Oct-2002   03:35   1.0.3705.370   2,269,184   Mscorwks.dll

STATUS

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

MORE INFORMATION

The following is an example of the crash stack of a bad InterfaceMarshaler object: 
(dbc.66c): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=0076006f ebx=00000000 ecx=00154ff8 edx=00000004 esi=016313bc edi=00000000
eip=791d08c1 esp=0012edbc ebp=0012ee10 iopl=0         nv up ei pl nz na po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00010206
mscorsvr!ObjHeader::PassiveGetSyncBlock+18:
791d08c1 8b04c1           mov     eax,[ecx+eax*8]   ds:0023:03c55370=????????

ChildEBP RetAddr  
0012edb8 791f6d5a mscorsvr!ObjHeader::PassiveGetSyncBlock()+0x18 
0012ee10 7920e666 mscorsvr!ObjHeader::GetSyncBlockSpecial()+0x14 
0012ee24 7921b5e8 mscorsvr!GetComIPFromObjectRef()+0x36 
0012ee38 792ea5ba mscorsvr!InterfaceMarshaler::ConvertSpaceComToNative()+0x33 
0012ee40 79267af7 mscorsvr!InterfaceMarshaler::UnmarshalNativeToComByrefInOut()+0x33 
0012eefc 79266a47 mscorsvr!RunML()+0x796 
0012efec 79224971 mscorsvr!ComToComPlusWorker()+0x255 
0012f02c 791cc804 mscorsvr!ComToComPlusWorker_Wrapper()+0x38 
0012f074 79218d5f mscorsvr!Thread::DoADCallBack()+0x5c 
0012f0dc 00f4a0bd mscorsvr!ComToComPlusWorker()+0x6d
Modification Type:MinorLast Reviewed:10/11/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix kbNetFrame100preSP3fix kbQFE KB330900 kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.