Unable to start debugging - Visual Studio 2012

Question

"Unable to start debugging 'C:\Windows\System32\WWAHost.exe'. The Microsoft Visual Studio Remote Debugging Monitor (MSVSMON.EXE) does not appear to be running on the remote computer. This may be because a firewall is preventing communication to the remote computer. Please see Help for assistance on configuring remote debugging."

Searched for similar posts, but didn't found one. If duplicate just inform. I am not trying to connect to any remote machine. Just testing on my local machine. Is there any way to solve this issue. (I'm using Windows 8 Enterprise 64-bit, just a javascript project)

Solution 1

Problem solved. Installed Remote tools update from here and working fine. Thanks for responding. Closing the topic.

Solution 2

I had the same problem. I fixed it by changing properties/compile/target platform to x86 instead of Any CPU. It solved the problem in my case. Hope it helps.

Solution 3

This happened to me just now when I had a website set up in IIS for mydomain.com, and set my project's start up url (Local IIS) to mydomain.com, and then launched the project before remembering to add a record in the host files for the domain:

127.0.0.1 mydomain.com

This got me for a good hour before I remembered I never set the record. Adding the record fixed it right away.

Solution 4

Windows 7 x64, VS 2012

In my case, the Remote Debugging Monitor component was installed and the app was clearly configured to debug locally in settings. This was a WinForms app upgraded from VS 2008, .NET 3.5.

Turns out it was the Windows Firewall. By directly running:

C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\Remote Debugger\x64\msvsmon.exe

A firewall dialog appeared where I could allow msvsmon.exe to run. After a VS 2012 re-start, debugging (locally) was fine!

View more solutions

Comments

[Matt Harrington]

If you're not trying to remotely debug, I'm not sure why the remote tools update would have helped you, but I'm glad you have it working.

[Chaithanya]

Don't know why it is asking for them. But now it's ok.

[ChrisF]

The link is broken. This is why link only answers are bad. Can you please update the answer with the relevant information included in the answer.

[Chaithanya]

Link is not broken. It points to "Remote Tools for Visual Studio 2012 Update 2". Just installed it and the problem is solved.

[parliament]

Wow, this actually got me twice and my own answer rescued me lol make sure you have your host entries uncommented!

[shawn.mek]

?? What does that even mean. Could you expound on 'I somehow realised that the file which was highlighted had changed and when I was trying to debug was not the MVC app project'? Thanks.

[freedomn-m]

"file highlighted" probably refers to the start-up project (it's bold/highlighted in the solution/projects window) (right click, 'Set as StartUp Project')

[Liam Swinney]

Yeah apologies for the lack of clarity with 'file highlighted' but @freedomn-m is correct, it was the start up project

[Davide Lettieri]

Solved for me on VS2013R2

[Marc Wittmann]

I guess going to debug options -> check remote debugging with a made up host (-> saving) and then uncheck remote debugging (-> saving) would have helped too. Sometimes the setting is just messed up.

[Bryan]

Are you going to the properties of the startup project? I don't have a Debugging section in those properties. We're still getting this error, and so far nothing we've tried works, and we have tried all of the solutions in this post, and on other SO posts, and other forums also.

[Colin Basnett]

I'm pretty sure this fix only applies to startup projects.

[Marc Johnston]

This worked for me ... not happy that I have to set the platform to x86 only though. :(