Link to home
Start Free TrialLog in
Avatar of codingbeaver
codingbeaverFlag for United States of America

asked on

ASP.NET Fatal execution engine error

Server: Windows Server 2008 x64 IIS 7
ASP.NET Framework 3.5 SP1
Web application settings:
.NET Framework 2.0
Enable 32-bit Applications: True
Managed Pipeline Mode: Classic

Sometimes the application hangs with errors in event log as follows:
.Net Runtime 1023:
.NET Runtime version 2.0.50727.3619 - Fatal Execution Engine Error (71CC7772) (80131506)

Application Error 1000:
Faulting application w3wp.exe, version 7.0.6001.18000, time stamp 0x47919413, faulting module mscorwks.dll, version 2.0.50727.3619, time stamp 0x4cc50595, exception code 0xc0000005, fault offset 0x00107219, process id 0x%9, application start time 0x%10.

Can someone help me to figure out what caused the problem and how to fix it?

Thanks,
ASKER CERTIFIED SOLUTION
Avatar of disrupt
disrupt
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of codingbeaver

ASKER

@disrupt,
The Debug Diagnostic Tool 1.1 has not been tested on Windows Server 2008, and I would not dare to try it because mine is a production server and many transactions are processed everyday.

@HainKurt,
Again, this is a production server with many transactions being processed everyday, and I am afraid the Hotfix may break the server. I will give it a try during the next sever maintenance time.

In the meantime, is there any other suggestion?
http://msdn.microsoft.com/en-us/windows/hardware/gg463016#ERC
(i dont blame u for not trying on production box)

I believe it's coming from the Dynamic IP Restrictions Module
I haven't got a chance to try the tools you all suggested because the app is in production now, but it gives me some in-depth knowledge of the error. If the error becomes too serious, I will have to try the above tools to debug it.

Thanks,