Mscorlib .net Runtime 2.0 Error
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and
Fatal Execution Engine Error .net Runtime
policies of this site About Us Learn more about Stack Overflow the .net runtime version 2.0.50727.5485 - fatal execution engine error company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags fatal execution engine error 80131506 Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes
.net Runtime Version 2.0 Fatal Execution Engine Error
a minute: Sign up Uncatchable .NET runtime 2.0 error - user machine - what next? up vote 3 down vote favorite 1 Situation: I have an application that uses http connections extensively (stream ripping app) and it is supposed to work 24/7. And it does. However, occasionally, it crashes with runtime error that is uncaught anywhere, and dumps following to the
Mscorwks.dll Crash
event log: Event Type: Error Event Source: .NET Runtime 2.0 Error Reporting Event Category: None Event ID: 5000 Date: 13.10.2010 Time: 11:02:30 User: N/A Computer: STREAM01 Description: EventType clr20r3, P1 streamsink.exe, P2 1.0.0.42484, P3 4c880fd9, P4 mscorlib, P5 2.0.0.0, P6 4add54dc, P7 344a, P8 21c, P9 system.io.ioexception, P10 NIL. My question is: how to know what line of code caused the crash. I am deploying .PDBs with the binaries, but... What to do? Target is WIndows XP, Framework is 2.0 EDIT: I have this already implemented: static public void InitializeExceptionHandler(string AppName) { Application.SetUnhandledExceptionMode(UnhandledExceptionMode.CatchException); Application.ThreadException += new System.Threading.ThreadExceptionEventHandler(Application_ThreadException); AppDomain currentDomain = AppDomain.CurrentDomain; currentDomain.UnhandledException+=new UnhandledExceptionEventHandler(currentDomain_UnhandledException); _appName=AppName; } No, it doesn't work! .net exception deployment share|improve this question edited Oct 19 '10 at 15:15 asked Oct 18 '10 at 21:27 Daniel Mošmondor 12.6k83979 1 This is sort of a leak at SO. Tens of thousands of questions that are all different but have the same answer. Implement AppDomain.UnhandledException and log/display/email/print e.ExceptionObject.ToString(). –Hans Passant Oct 18 '10 at 22:11 @Hans: unfortunately, that doesn't help. There are exceptions that are handled, but thi