.Net Runtime 2.0 Error, Event ID 5000
Running an application based on .Net framework 2.0 fails. The following error is logged in the Application Log:
"Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 5000
Date: 01/01/2008
Time: 14:28:13
User: N/A
Computer: T1MSG
Description: EventType clr20r3, P1 adcopc.exe, P2 0.0.0.0, P3 4407bfd1, P4 mscorlib, P5 2.0.0.0, P6 4333ab80, P7 bd0, P8 59, P9 system.formatexception, P10 NIL."
Cause
This problem occurs because the default policy for unhandled exceptions has changed in the Microsoft .NET Framework 2.0. By default, the policy for unhandled exceptions is to end the worker process.
In the .NET Framework versions 1.1 and 1.0, unhandled exceptions on managed threads are ignored. Unless you attached a debugger to catch the exception, you would not realize that anything was wrong.
ASP.NET uses the default policy for unhandled exceptions in the .NET Framework 2.0. When an unhandled exception is thrown, the ASP.NET-based application unexpectedly quits.
This behavior does not apply to exceptions that occur in the context of a request. These kinds of exceptions are still handled and wrapped by an HttpException object. Exceptions that occur in the context of a request do not cause the worker process to end. However, unhandled exceptions outside the context of a request, such as exceptions on a timer thread or in a callback function, cause the worker process to end.
Resolution
See Unhandled exceptions cause ASP.NET-based applications to unexpectedly quit in the .NET Framework 2.0.
