Wednesday, 9 March 2011

VS Remote Debugger: Invalid access to memory location

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.

VS-invalid-access-memory

I've found the only way to correct this is by restarting Visual Studio.

If you found this post helpful, please support my advertisers.

29 comments:

  1. Couldn't believe I didn't think about simply restarting VS. Thanks Michael, your suggestion worked brilliantly.

    ReplyDelete
  2. This saved me some troubleshooting time, thanks for sharing :D

    ReplyDelete
  3. Good point. Thanks for sharing.

    ReplyDelete
  4. Worked like a charm! Thanks.

    ReplyDelete
  5. Yes, it helps.

    ReplyDelete
  6. Worked excellent, thanks Michael!

    ReplyDelete
  7. I really like your blog thanks for sharing. You should update more.

    ReplyDelete
  8. thank's a lot

    ReplyDelete
  9. Works great. Thanks.

    ReplyDelete
  10. Haha I restarted the server and everything struggled for days before finding this post and restarting VS.

    ReplyDelete
  11. thanks a lot it worked!!

    ReplyDelete
  12. thank you!!

    This fix is certified and approved to work.

    -Busy Guy, MCPD EAD

    ReplyDelete
  13. If that doesn't work, restart Windows.

    ReplyDelete
  14. Thanks...this works for VS2012 also.

    ReplyDelete
  15. With so many experiencing this issue (including myself) has someone submitted this as a formal issue with Microsoft?

    ReplyDelete
  16. Perfect. Worked for me :) . Can't believe it was that simple.

    ReplyDelete
  17. I GET THIS EVERY TIME I TRY TO REMOTE DEBUG!!! SO ANNOYING!!!

    ReplyDelete
  18. Some people advice to apply this hotfix:
    http://support.microsoft.com/kb/2588507

    ReplyDelete
  19. Thanks worked for me :)

    ReplyDelete
  20. It's wonderful, amazing. I couldn't even imaging that solution could be so easy. I spent few hours trying to find out a workaround.
    Thanks A LOT.

    ReplyDelete
  21. Thanks! Worked for me.

    ReplyDelete
  22. Lol... Thank you. ;)

    ReplyDelete
  23. Thanks for sharing use interview questions on .Net technology. While preparing for my job interview, your article helped me a lot to sharpen my skills and do well in my interview. One of trainer from leading dot net training institutes in Chennai suggests me about your site.

    ReplyDelete

Spam comments will be deleted

Note: only a member of this blog may post a comment.