Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SBS 2008 .NET Runtime 2.0- Fatal Execution Engine Error (80131506)

Status
Not open for further replies.

btechAU

Technical User
Mar 17, 2004
3
AU
Hi All,

I think the .net framework (2.0) has somehow been corrupted on one of our SBS 2008 servers. Now we can't open most MMC-based tools such as SBS console, Event Viewer and some Exchange services won't start.

The errors are:

NET Runtime Event ID 1023
.NET Runtime version 2.0.50727.3623 - Fatal Execution Engine Error (000007FEF62B841A) (80131506)

Application Error Event ID 1000
Faulting application console.exe, version 6.0.5601.8538, time stamp 0x4d24e3fe, faulting module mscorwks.dll, version 2.0.50727.3623, time stamp 0x4d8c11a2, exception code 0xc0000005, fault offset 0x00000000005adfc2, process id 0x%9, application start time 0x%10.

.NET Runtime Event ID 1023
.NET Runtime version 2.0.50727.3623 - Fatal Execution Engine Error (000007FEF62B841A) (80131506)

Application Error Event ID 1000
Faulting application mmc.exe, version 6.0.6001.18000, time stamp 0x47919524, faulting module mscorwks.dll, version 2.0.50727.3623, time stamp 0x4d8c11a2, exception code 0xc0000005, fault offset 0x00000000005adfc2, process id 0x%9, application start time 0x%10.

.NET Runtime Event ID 1023
.NET Runtime version 2.0.50727.3623 - Fatal Execution Engine Error (000007FEF62B841A) (80131506)

Application Error Event ID 1000
Faulting application w3wp.exe, version 7.0.6001.18000, time stamp 0x47919ed8, faulting module mscorwks.dll, version 2.0.50727.3623, time stamp 0x4d8c11a2, exception code 0xc0000005, fault offset 0x00000000005adfc2, process id 0x%9, application start time 0x%10.

We've tried to repair .NET 3.5 SP1 (as it includes 2.0 SP2) as well as uninstall it and reinstall it. Also ran sfc /scannow as .net is part of the o/s. No luck with any of that.

As this is an SBS 2008 server, I didn't want to try anything drastic such as forcibly cleaning up .net 2 and reinstalling it …

Any suggestions much appreciated!
 
Just wanted to let anyone who might come across this know that installing Windows 2008 Server SP2 fixed the issue.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top