"An exception System.ExecutionEngineException has occurred" error message when you use multiple asynchronous events

This article has been archived. It is offered "as is" and will no longer be updated.
When you use multiple asynchronous events such as remoting events in your application, you may receive the following error message:
An exception System.ExecutionEngineException has occurred
The call stack looks similar to the following:
(a90.a7c): Access violation - code c0000005 (first chance)First chance exceptions are reported before any exception handling.This exception may be expected and handled.eax=00000000 ebx=00000000 ecx=0000000f edx=ffffffef esi=00149d54 edi=00000080eip=791bc44d esp=0012e450 ebp=0012e450 iopl=0         nv up ei ng nz ac pe nccs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000292mscorwks!ArrayList::GetPtr+f:791bc44d 8b4804           mov     ecx,[eax+0x4]     ds:0023:00000004=????????0:000> kpn # ChildEBP RetAddr00 0012e450 791bc474 mscorwks!ArrayList::GetPtr01 0012e45c 7921de49 mscorwks!SystemDomain::GetAppDomainAtId02 0012e468 791f5ab8 mscorwks!AppDomainStack::GetNextDomainOnStack03 0012e47c 791f5aee mscorwks!ApplicationSecurityDescriptor::CheckStatusOf04 0012e4c8 791f5a49 mscorwks!COMCodeAccessSecurityEngine::SpecialDemand05 0012e4f8 791f5a6a mscorwks!Security::DoDeclarativeActions06 0012e50c 088fcccb mscorwks!DoDeclarativeSecurity
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: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 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 tool in Control Panel.
   Date         Time   Version       Size       File name          Platform   ------------------------------------------------------------------------   30-Jul-2003  02:06  1.1.4322.929     77,824  Corperfmonext.dll  X86   30-Jul-2003  02:03  1.1.4322.929    311,296  Mscorjit.dll       X86   31-Jul-2003  06:33  1.1.4322.929  2,093,056  Mscorlib.dll       X86   30-Jul-2003  01:57                   10,748  Mscorlib.ldo   30-Jul-2003  02:05  1.1.4322.929  2,498,560  Mscorsvr.dll       X86   30-Jul-2003  02:06  1.1.4322.929  2,486,272  Mscorwks.dll       X86
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Identyfikator artykułu: 825709 — ostatni przegląd: 12/08/2015 04:02:25 — zmiana: 3.3

Microsoft .NET Framework 1.1

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbhotfixserver kbqfe kbnetframe110sp1fix kbnetframe110presp1fix kbfix kbbug KB825709
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)