![]() If you have Visual Studio installed on the same PC/server as the crashing app, attach Visual Studio to the EXE whilst it's running. Īs you are not getting any useful information at the time of the crash, an alternative approach is to attach a debugger to the crashing EXE. There's were no events around it for hours and there were Info level not Error like this one.įaulting application, version 0.0.0.0, stamp 4ca5d33d, faulting module mscorwks.dll, version 7.3607, stamp 4add5446, debug? 0, fault address 0x0010724e.įor more information, see Help and Support Center at. Net 3.5 on a Window Server 2003 vm slice.įull event description below. Net runtime failure/bug and has nothing to do with my code.ĭoes anyone know what caused this? Is there a. and when I looked in the Windows Event Viewer Application log it contained an error for the programs process saying '.NET Runtime 2.0 Error' Type: Error EventID: 1000. the process appears to have been killed by someting. I have a new program which has been running 24/7 for over 2 weeks now but last night it crash/went down with no Fatal log exception in my log4net file.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |