Databases
StackOverflow2013
Postsdbo
POUnhandled exception that caused the application to crash with "EventType clr20r3, P1 w3wp.exe" in the log, but no details there
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUnhandled exception that caused the application to crash with "EventType clr20r3, P1 w3wp.exe" in the log, but no details there
    text
    copied!<p>On the production server, I can see this event from system Event Viewer when an ASP .NET app crashes:</p> <blockquote> <p>EventType clr20r3, P1 w3wp.exe, P2 6.0.3790.3959, P3 45d691cc,<br> P4 app_web_default.aspx.cdcab7d2, P5 0.0.0.0, P6 4b2e4bf0, P7 4, P8 4, P9<br> system.dividebyzeroexception, P10 NIL.*</p> </blockquote> <p>It belongs to ".NET Runtime 2.0 Error Reporting" category.</p> <p>But I can't find an event which belongs to "ASP.NET 2.0.50727.0" category which can give me this exception a detailed view like this:</p> <pre><code>An unhandled exception occurred and the process was terminated. Application ID: /LM/W3SVC/505951206/Root Process ID: 1112 Exception: System.DivideByZeroException Message: Attempted to divide by zero. StackTrace: at _Default.Foo(Object state) at System.Threading.ExecutionContext.runTryCode(Object userData) at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack) at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state) For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp </code></pre> <p>I have the second event on my dev machine, is it because Visual Studio is installed there? If so, how can I disable this so I can emulate the production environment?</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload