Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

VS2013 Professional local 64-bit debugging MSVSMON issue

Every time I attempt to start a local debugging session in VS2013 Professional on a Windows 8 64-bit machine, I receive the following error:

Operation taking longer than expected

"A 64-bit debugging operation is taking longer than expected. This may be caused by incompatibilities with 3rd party networking software. See help for troubleshooting these issues."

followed shortly by:

Error message that I receive when starting a debugging session

"Unable to start program. The Microsoft Visual Studio Debugging Monitor (MSVSMON.EXE) does not appear to be running on the remote computer Please see Help for assistance on configuring remote debugging"

To start the debugging session, I press the "Local Windows Debugger" button:

"Local Windows Debugger" button

Nothing scary there: definitely not remote debugging.

Things I've tried:

  • Installing the Remote Tools for Visual Studio 2013
  • Running these tools whilst attempting to debug.
  • Following the instructions on this SO answer.
  • Turning off my ZoneAlarm firewall completely (although running MSVSMON.EXE manually does not cause it to ask me for permissions... Is it even running a server?)
  • Adding an exception to the Windows Firewall for the monitor
  • Setting MSVSMON.EXE to "No Authentication" mode
  • Checking my "HOSTS" file: Only comments.
  • Restarting

Further symptoms:

  • Only happens when debugging 64-bit software.
  • Happens no matter what language (C++, C# both have the same issue)

Any help in resolving this would be great.

Thanks.

like image 340
AStupidNoob Avatar asked Jan 24 '14 10:01

AStupidNoob


People also ask

What is Msvsmon?

The Microsoft Visual Studio Remote Debugging Monitor (MSVSMON.

Where is Msvsmon EXE located?

In windows explorer, navigate to c:\ and search for msvsmon.exe . This will show you number of locations based on the number of Visual Studio version you have.

How do I debug a remote process in Visual Studio?

You can attach the Visual Studio debugger to a running process on a local or remote computer. After the process is running, select Debug > Attach to Process or press Ctrl+Alt+p in Visual Studio, and use the Attach to Process dialog to attach the debugger to the process.


1 Answers

You can try also to enable incoming UDP 3702

The windows firewall has a rule described as so:

Inbound rule to allow Visual Studio to discover remote debuggers running on the local network [UDP 3702]

Good Luck

like image 70
user1656671 Avatar answered Nov 10 '22 15:11

user1656671