Visual Studio 2012 A remote operation is taking lo

Question

I'm running Visual Studio 2012 on Windows 8 64bit. I have a 64 bit project that is in source control and I'm trying to run it at home on my Windows 8 pc. The application builds successfully however the remote debugger doesn't work at all.

It says "A remote operation is taking longer than expected". I understand why its remote, being that 32 bit Visual Studio needs to access msvsmon.exe to debug through 64 bit applications but I've never seen this happen on a local machine where the source code has been checked out.

I tried reinstalling Visual Studio 2012, playing with ports (4016) as well as running as admin. Checked that VPN wasn't an issue by uninstalling the client.

I am now out of ideas. I tried creating a brand new local project to test and set it as 64 bit but the operation still does not succeed.

Any ideas or suggestions? Is this a known issue with Visual Studio 2012 on Windows 8?

Answer 1

Just my two cents,

I have experienced this issue twice now and it turns out after all of the suggestions I tried, it was BitDefender on my local machine that was doing this. So my fix for this problem is to try adding in exceptions to the local security software into the firewall and AV parts of it. Tell it to ignore the msvsmon.exe and devenv.exe altogether and see what difference that makes.

Otherwise try ripping it off altogether and see if the it lets you debug your solution.

You can see here for more info: http://forum.bitdefender.com/index.php?showtopic=37028

I installed the latest BitDefender version and all was fine for me.

Answer 2

The only answer I have gotten to work with VS2012 is to go into the Project properties > Compile > Target CPU and set the option to "x86".

This also seems related to this question: Can't start debugger in VS2012 RC They submitted this to Microsoft Connect as well. Seems to be a Visual Studio problem...

best of luck.

Answer 3

The solution to this problem is:

Navigate to C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\Remote Debugger Open x64 folder and rename the msvsmon.exe file to msvsmon_old.exe Now, navigate to x86 folder and copy msvsmon.exe and paste it into x64 folder. Restart the Visusl Studio 2012 IDE, and now try attching to process during debugging

Answer 4

What worked for me was uninstalling a program called "sendori"

Answer 5

I am working with VS2012 (Windows7, 64-bit PC). When I selected DEBUG - Attach to Process... I did see a messagebox saying "A 64-bit debugging operation is taking longer than expected". I downloaded I free trial version of VS2010 and noticed that in VS2010 it worked fine. So, I copied the files msvsmon.exe and msvsmon.exe.config from VS2010 (C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Remote Debugger\x64 and C:\ ... \x86) into the same maps in VS2012. Now it is working VS2012. Hope this helps you too. Good luck.

Answer 6

Solution for me in VS 2015. I had a public dns entry mapped to my local iis and the web/debug tab of the project:

<app>.<domain>.co.uk

Just had to add that to the hosts file as a local host:

127.0.0.1 <app>.<domain>.co.uk

Thus VS no longer thinks the host is a remote machine.