none
Fatal Execution Engine Error Windows 2003 .net 2.0 and wcf RRS feed

  • Question

  • We are using a wcf hosted application in IIS in a windows 2003 environment.

    Now we encountered the following exceptions found in the eventlog:
    first we get :
     .NET Runtime version 2.0.50727.63 - Fatal Execution Engine Error (7A05F093) (80131506)
    And then:
    Faulting application w3wp.exe, version 6.0.3790.1830,
    stamp 42435be1, faulting module mscorwks.dll,
    version 2.0.50727.63, stamp 43d5e353, debug? 0, fault address 0x0000c365.

    The application acts very strange and only after a iisreset everything is normal again.

    we already installed NDP20-KB913384-X86.exe from http://support.microsoft.com/default.aspx/kb/913384 but no luck. 

    It is happening so now and then and I have no idea how to reproduce it.


    Mark Henneman
    Tuesday, March 31, 2009 9:26 AM

Answers

  • You've had a *very* old and unpatched version of .NET, the hotfix is very old as well.  You might find relieve by upgrading to .NET 3.5 SP1.  Other than that, getting FEEE indicates misbehaving client code destroying internal CLR data structures.  Unmanaged code, very hard to diagnose.
    Hans Passant.
    • Marked as answer by Zhi-Xin Ye Monday, April 6, 2009 3:10 AM
    Tuesday, March 31, 2009 12:25 PM
    Moderator
  • A number of people have reported similar issue on Win2003 Server in this thread and on other forums on the internet. I didn't see any solution for this issue though.
    As Hans mentioned, this type of issue is hard to diagnose - see this thread for explanation and for an example what might go wrong.

    If you don't want to install the full .NET 3.5 SP1 package, you can install .NET 2.0 SP2 package which is a subset/prerequisite of 3.5 SP1 package.

    -Karel
    • Marked as answer by Zhi-Xin Ye Monday, April 6, 2009 3:10 AM
    Tuesday, March 31, 2009 3:53 PM
    Moderator

All replies

  • You've had a *very* old and unpatched version of .NET, the hotfix is very old as well.  You might find relieve by upgrading to .NET 3.5 SP1.  Other than that, getting FEEE indicates misbehaving client code destroying internal CLR data structures.  Unmanaged code, very hard to diagnose.
    Hans Passant.
    • Marked as answer by Zhi-Xin Ye Monday, April 6, 2009 3:10 AM
    Tuesday, March 31, 2009 12:25 PM
    Moderator
  • A number of people have reported similar issue on Win2003 Server in this thread and on other forums on the internet. I didn't see any solution for this issue though.
    As Hans mentioned, this type of issue is hard to diagnose - see this thread for explanation and for an example what might go wrong.

    If you don't want to install the full .NET 3.5 SP1 package, you can install .NET 2.0 SP2 package which is a subset/prerequisite of 3.5 SP1 package.

    -Karel
    • Marked as answer by Zhi-Xin Ye Monday, April 6, 2009 3:10 AM
    Tuesday, March 31, 2009 3:53 PM
    Moderator
  • Thanks for all the replay's.
    I did install .net 2.0 sp2 package and it solved the problem.

    Mark


    Mark Henneman
    Thursday, April 9, 2009 6:40 AM