locked
The remote debugger has encountered a serious internal error, and must abort the remote debugging session. Please restart debugging. RRS feed

  • Question

  • Ever since upgrading to Visual Studio 2010, when I'm debugging my application (a few minutes into debugging), I get the following error message "The remote debugger has encountered a serious internal error, and must abort the remote debugging session. Please restart debugging." in th windows event log. The upgrade to 2010 coincided with us also running the application in 64 bit. This is currently happening when I'm debugging locally, but it doesn't mean that the problem doesn't happen remotely as well.

    After that error message i also get the following events

    Faulting application name: msvsmon.exe, version: 10.0.30319.1, time stamp: 0x4ba23831
    Faulting module name: msvsmon.exe, version: 10.0.30319.1, time stamp: 0x4ba23831
    Exception code: 0xc0000005
    Fault offset: 0x0000000000071469
    Faulting process id: 0x2f74
    Faulting application start time: 0x01cb49ff50df3c61
    Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Remote Debugger\x64\msvsmon.exe
    Faulting module path: C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Remote Debugger\x64\msvsmon.exe

    That is quickly followed by my application crashing the following event repeated twice

    NET Runtime version 2.0.50727.4927 - Fatal Execution Engine Error (000007FEF473B4DF) (0)

    After all this, I am unabled to debug into my process again until I restart my instance of Visual Studio

    Wednesday, September 1, 2010 7:56 PM

Answers

  • Hi Mark,

    Thanks for your feedback!

    To generate a dump file, you could use Windows Task Manager (right click a process and select Create Dump File.) Surely, there are other tools can also help you, for example, WinDbg.exe or UserDump.exe, Please take a look at this KB article for an walkthrough on that:
    http://support.microsoft.com/kb/241215

    Thanks


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have any feedback, please tell us.
    Welcome to the All-In-One Code Framework!
    • Marked as answer by liurong luo Thursday, September 30, 2010 2:26 AM
    Monday, September 13, 2010 8:50 AM

All replies

  • Hello,

    I find a similar issue in our connect site. Please see here:
    https://connect.microsoft.com/VisualStudio/feedback/details/510777/the-remote-debugger-has-encountered-a-serious-internal-error-and-must-abort-the-remote-debugging-session-please-restart-debugging?wa=wsignin1.0

    As you can see, this happens when you debug a 64-bit program, however, Visual Studio runs as a 32-bit process. Please vote the thread and generate a dump as required to reproduce.

    Thanks a lot!


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have any feedback, please tell us.
    Welcome to the All-In-One Code Framework!
    • Marked as answer by liurong luo Thursday, September 9, 2010 3:41 AM
    • Unmarked as answer by markoueis Friday, September 10, 2010 9:24 PM
    Friday, September 3, 2010 3:43 AM
  • Is there anything i can do to help diagnose this issue. You mentioned generating a dump... i don't know how to do that? Anything i can do to help better understand what's going on?

    Thanks

    Mark

    Friday, September 10, 2010 9:25 PM
  • Hi Mark,

    Thanks for your feedback!

    To generate a dump file, you could use Windows Task Manager (right click a process and select Create Dump File.) Surely, there are other tools can also help you, for example, WinDbg.exe or UserDump.exe, Please take a look at this KB article for an walkthrough on that:
    http://support.microsoft.com/kb/241215

    Thanks


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have any feedback, please tell us.
    Welcome to the All-In-One Code Framework!
    • Marked as answer by liurong luo Thursday, September 30, 2010 2:26 AM
    Monday, September 13, 2010 8:50 AM
  • Hey Roahn

     

    I get a similar error. The process I am debugging works fine without the debugger attached but when I attach the debugger I get the following in the event log. I do have a dump file that I created using the sysinternals tool procdump. How can I send you the crash dump file

     

    Faulting application name: msvsmon.exe, version: 10.0.30319.1, time stamp: 0x4ba23831

    Faulting module name: SYMSRV.dll, version: 6.12.2.633, time stamp: 0x4b673674

    Exception code: 0xc0000005

    Fault offset: 0x000000000000b857

    Faulting process id: 0x13ec

    Faulting application start time: 0x01cc6813920aa9d6

    Faulting application path: c:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Remote Debugger\x64\msvsmon.exe

    Faulting module path: c:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Remote Debugger\x64\SYMSRV.dll

    Report Id: ec15b006-d406-11e0-b53f-0023ae58471c


    MSFT
    Wednesday, August 31, 2011 7:30 PM