I've been running my Visual Studio 2010 remote debugger as a service for a while now and found the experience to be generally seamless. Every so often, however, things go pear-shaped and Visual Studio throws up it arms when attempting to connect to the remote machine:
Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor named 'my-dev-env'. Invalid access to memory location.
I've found the only way to correct this is by restarting Visual Studio.
Couldn't believe I didn't think about simply restarting VS. Thanks Michael, your suggestion worked brilliantly.
ReplyDeleteThis saved me some troubleshooting time, thanks for sharing :D
ReplyDeleteGood point. Thanks for sharing.
ReplyDeleteWorked like a charm! Thanks.
ReplyDeleteYes, it helps.
ReplyDeleteThank you!
ReplyDeleteWorked excellent, thanks Michael!
ReplyDeleteThank you!!!
ReplyDeleteI really like your blog thanks for sharing. You should update more.
ReplyDeletethank's a lot
ReplyDeleteWorks great. Thanks.
ReplyDeleteHaha I restarted the server and everything struggled for days before finding this post and restarting VS.
ReplyDeletethanks a lot it worked!!
ReplyDeletethank you!!
ReplyDeleteThis fix is certified and approved to work.
-Busy Guy, MCPD EAD
If that doesn't work, restart Windows.
ReplyDeleteThanks :)
ReplyDeleteThanks...this works for VS2012 also.
ReplyDeleteExcellent
ReplyDeleteWith so many experiencing this issue (including myself) has someone submitted this as a formal issue with Microsoft?
ReplyDeletePerfect. Worked for me :) . Can't believe it was that simple.
ReplyDeleteI GET THIS EVERY TIME I TRY TO REMOTE DEBUG!!! SO ANNOYING!!!
ReplyDeleteWorked
ReplyDeleteSome people advice to apply this hotfix:
ReplyDeletehttp://support.microsoft.com/kb/2588507
Thanks worked for me :)
ReplyDeleteIt's wonderful, amazing. I couldn't even imaging that solution could be so easy. I spent few hours trying to find out a workaround.
ReplyDeleteThanks A LOT.
Thanks! Worked for me.
ReplyDeleteLol... Thank you. ;)
ReplyDelete