Configure Visual Studio 2010 Remote Debugger

Question

I have installed the Visual Studio 2010 Remote Debugger on a Windows Server 2003 (x86) server, and am attempting to connect to it results in the following error:

Answer 1

Here are the steps I took to get remote debugging to work against an ASP.NET app. Not sure if you've done this already, hopefully something might help.

• On my machine (call it DEVMACHINE from now on) I shared out the folder that contained the remote debugger (msvsmon.exe). On my machine, it was located at C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\Remote Debugger\x86. I called the share msvsmon

• On the server, I opened Windows explorer and navigated to \\DEVMACHINE\msvsmon, and ran msvsmon.exe (This opened the Visual Studio Remote Debugging Monitor)

• On DEVMACHINE, I started Visual Studio 2010 and opened the solution that represents the application I'm attempting to debug.

• In Visual Studio, clicked Tools > Attach To Process...

• Entered the server name in the Qualifier field, then double clicked on the w3p.exe process that was in the list.

• I then placed a break point in the location I wanted to start debugging

Couple things to note: The code deployed to the server was a Debug Build, the pdb files were there, along with the binaries. I had full admin rights on the server. No tools were installed on the server, I simply ran the exe that was located on DEVMACHINE. I did not have any firewalls between the DEVMACHINE and the server. And, both DEVMACHINE and the server are on the same domain.

Hope that helps.

Answer 2

Same problem here. My reason was that Trend security was enabled in the local computer, and it was blocking the firewall. I could not stop it because I needed a password, so I just deleted all the Trend processes, and it seemed to work fine. So you could check if some antivirus is enabled that is blocking the access.

I also needed to add devenv.exe to the Allowed Programs in the Windows Firewall in the local computer, and set its policies.

Answer 3

I just ran into connectivity issue. The problem was the Client PC (my desktop) could connect to Remote Host running debug monitor, but the Remote Host could not send data back to my desktop.

Turns out that it was caused by the 'Profile' setup in Windows Firewall. The Firewall rule was being limited to 'Public' profile - but my desktop was connected to the local domain. Changing the setting to 'Domain' ensured the Remote Host could communicate debugging data back to Client desktop.

Check under Windows Firewall -> Inbound Rules -> Microsoft Visual Studio -> Advanced Tab.

Cheers, J

Answer 4

I kept getting the same error listed above, and after trying all of the other answers, the problem turned out to be that DCOM was disabled on my development machine. The problem was solved by enabling DCOM using the instructions from this technet link.

Answer 5

Below is a quick step to set up Visual Studio Remote Debugging Monitor on Visual Studio IDE.

• Open Programs > Microsoft Visual Studio 2010 > Visual Studio Tools > Visual Studio 2010 Remote Debugger Folder.

• A Windows Explorer shows the 32 and 64-bit versions of the Remote Debugging Monitor.

• Copy the respective ver that matches remote server (e.g. x64 machine use X64 folder & x32 machine use X86 folder) to a folder on your machine.

• While at the console on your remote machine, go to the folder and start msvsmon.exe.

• Go to Tools > Options and change the Authentication mode to No Authentication and check the box Allow any user to debug.

• From your development machine, on Visual Studio, go to Tools > Attach to Process.

• Change the Transport to Remote and the Qualifier to the name of your remote server.

• You should now see the executable, which you want to debug on that list. Select the process you want to debug and click Attach.

• You may now debug the code while it is running on the remote server.

• Just remember to turn off Remote Debugging Monitor at the remote server once done.

Please refer below MS link: https://docs.microsoft.com/en-us/visualstudio/debugger/remote-debugging-cpp?view=vs-2017

Answer 6

I am using local DNS so I can test websites before they go live (by editing my hosts file).

I have a specific IP assigned by my router at home and at work.

i.e. dev.example.com is mapped to 192.168.1.123

When my machine changed to a different network without me realizing it could no longer reach the debugger and so I got the error.

Pretty obscure situation I had to get this error, which no amount of rebooting or recycling IIS will fix.