Sometimes I am getting an error when I try to start debugging using VS 2005. A message box comes up saying:
"Microsoft Visual Studio 2005 Remote Debugging Monitor (MSVSMON.EXE) failed to start. Verify that the remote debugger is properly installed."
If I retry starting a debug session, it usally starts up.
Why is this happening
And since, I assume, Visual Studio 2005 installed the remote debugger, how in the heck am I supposed to verify that the remote debugger is properly installed Am I supposed to know what registry settings, services, or other software need to be present Just what am I supposed to "verify"
I did a search of my program files directory and found an msvcmon.exe under the Microsoft Visual Studio (6.0) directory and another under the Microsoft Visual Studio .NET 2003 directory. I found nothing under the Microsoft Visual Studio 8 directory. Should there be one there
VS 2005 unable to start debugging because MSVSMON.EXE failed to start.
ValenTientje
I managed to type "s" two out of three times including the "Subject" line. Come to think of it, that's a better batting average than VS 8 when it comes to starting the remote debugger to debug a 64 bit program!
I did not say I could not find the remote debugger. Just that I cannot verify it is installed correctly as program installation varies greatly depending on the program being installed. Without the msi database for the program, I am hardly in a position to do any verification. The program, msvsmon.exe, is in the remote debugger/x64 directory under my program files (64-bit) folder. Perhaps I should wonder why the IDE is trying to start a "remote" debugger when I am debuggging a project on my machine.
I have run depends.exe on the exe. Depends is not ready for prime-time when it comes to examining a 64 bit exe or dll. It tells me there are a number of errors due to different cpu types being found and missing entry points and missing modules. None the less, when the debug command does start a debugging session, msvsmon.exe is running as I can see it in the task mananger, sans "*32".
And yes, I am debugging 64 bit programs on the 64-bit edition of XP pro running on a 64 bit AMD processor.
Since I have been debugging 64 bit programs since VS 8 RTM and this problem just started showing up in the last few days, I am about to assume that one of the automatic updates has caused the problem and perhaps I should reinstall.
india7
Interesting. What kind of project is this Is this x64 Windows
As for the 'Verify' error messages, good question. That is the problem with error messages for situations that shouldn't happen -- we can't be specific as to what is wrong because we don't know. Regardless, if this only happens sometimes, it doesn't sound like a setup problem.
BTW: You need to look for 'msvsmon.exe' not 'msvcmon.exe'