Visual Studio 2012 A remote operation is taking longer than expected

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 b

Answer 1

I think you should try this:

• Run cmd.exe as administrator.
• Type in and run the following two lines of command:

netsh winsock reset catalog

netsh int ip reset reset.log hit

• It may say that a reboot is required, but actually that is not necessary.
• Try to debug your application again, the problem should be solved.

EDIT: Sorry for not providing an explanation for this before. The answer actually came from a Chinese forum and the original author didn't explain it much. But he did say that it's because Visual Studio is a 32bit program which may have problem accessing network under 64bit Windows 7, and the aforementioned solution resets the network connection therefore solves the problem. Hope this helps.

Answer 2

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

Answer 3

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 4

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 5

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 6

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