none
.NET Runtime version 2.0.50727.5444 - Fatal Execution Engine Error (74EDEA52) (80131506)

    Question

  • Is there a hot fix for this bug, I have seen an older hotfix for the same bug on an older version of .NET

    http://michaelsync.net/2009/10/31/net-runtime-version-2-0-50727-3603-fatal-execution-engine-error-7a036050-80131506-mscoree-dll

    ----------------------------------------------

    Windows 2008 R2 (All Latest Updates Applied)

    ----------------------------------------------

    Log Name:      Application
    Source:        .NET Runtime
    Event ID:      1023
    Level:         Error
    Description: .NET Runtime version 2.0.50727.5444 - Fatal Execution Engine Error (74EDEA52) (80131506)

    ------------------------------------------

    Faulting application name: QBServerUtilityMgr.exe, version: 20.0.4112.7940, time stamp: 0x4d9b0a09
    Faulting module name: mscorwks.dll, version: 2.0.50727.5444, time stamp: 0x4d4f1425
    Exception code: 0xc0000005
    Fault offset: 0x0002b38e
    Faulting process id: 0x%9
    Faulting application start time: 0x%10
    Faulting application path: %11
    Faulting module path: %12
    Report Id: %13


    Friday, July 01, 2011 4:01 PM

Answers

  • Hi JaminQuimby,

    Thank you for your update.

    Based on my test, Windows6.1-KB979744-v2-x64.msu could be installed on Windows 2008 R2 without SP1.

    I found your log show mscorwks.dll version 2.0.50727.5444 that version is for Windows 2008 SP1 listed in MS11-028(KB2446710) not for Windows 2008 listed in MS11-028(KB2446709). I suggest you to install the latest MS updates or uninstall KB2446710.

    If there are more inquiries on this issue, please feel free to let us know.


    Regards,
    Rick Tan
    • Marked as answer by JaminQuimby Thursday, July 07, 2011 9:31 PM
    Wednesday, July 06, 2011 3:09 AM
    Moderator

All replies

  • Hi Jamin,

    Can you confirm if you are running the x86 (32 Bit) or X64 (64 Bit) version of .net? I have seen this issue before.

    Michael Sync has a great article on this issue located at (http://michaelsync.net/2009/10/31/net-runtime-version-2-0-50727-3603-fatal-execution-engine-error-7a036050-80131506-mscoree-dll)

    Best of Luck!

    Martin

    Friday, July 01, 2011 5:02 PM
  • Windows 2008 R2. x64  it has to do with the built in .NET 2.0 I beleive. The artical post that you have in your thread is the same error, just a older version of .NET 2.0 so I cannot install that Hotfix. 

    Friday, July 01, 2011 6:44 PM
  • Hi JaminQuimby,

    Thank you for your post.

    Please check this blog article and KB2540222, install the latest version of Hotfix 979744 on your server.

    If there are more inquiries on this issue, please feel free to let us know.


    Regards,
    Rick Tan
    Monday, July 04, 2011 8:51 AM
    Moderator
  • Windows6.1-KB979744-v2-x64.msu

    This update is not applicable to your computer.

    NDP20SP2-KB979744-x64.exe

    None of the products that are addressed by this software update are installed on this computer. Click Cancel to exit setup.

     

    I do have Service Pack 1 installed and I assume that HotFix 979744 does not apply.

     

     

    Tuesday, July 05, 2011 3:24 PM
  • Hi JaminQuimby,

    Thank you for your update.

    Based on my test, Windows6.1-KB979744-v2-x64.msu could be installed on Windows 2008 R2 without SP1.

    I found your log show mscorwks.dll version 2.0.50727.5444 that version is for Windows 2008 SP1 listed in MS11-028(KB2446710) not for Windows 2008 listed in MS11-028(KB2446709). I suggest you to install the latest MS updates or uninstall KB2446710.

    If there are more inquiries on this issue, please feel free to let us know.


    Regards,
    Rick Tan
    • Marked as answer by JaminQuimby Thursday, July 07, 2011 9:31 PM
    Wednesday, July 06, 2011 3:09 AM
    Moderator
  • I had to uninstall the Security Update for KB2446710, that was the only 'not solution' thing I could do to fix the issue. I was not going to uninstall SP1 and install KB979744 because SP1 has fixed allot of other issues. I hope they make a hot fix; (another hot fix) to fix this issue with SP1.

    Uninstalling a Security Patch is NEVER a solution but it was the Answer, thanks Rick.

    Thursday, July 07, 2011 9:37 PM