Article ID: 330900 - Last Review: October 11, 2005 - Revision: 2.4 FIX: ExecutionEngineException Error After a Typical Exception Is ThrownThis 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.
RESOLUTIONA 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
(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 STATUSMicrosoft 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:
| Article Translations
|

Back to the top
