This topic has not yet been rated - Rate this topic

Remote Debugging Errors and Troubleshooting

Visual Studio 2010

Visual Studio 2012
Visual Studio 2008
.NET Framework 3.0
Visual Studio 2005
Visual Studio .NET 2003

This topic applies to:

Edition	Visual Basic	C#	F#	C++	Web Developer
Express
Pro and Team

You may encounter the following errors when attempting to debug remotely.

Error: Access Denied On Callback
Cannot Open File "G:\<filename>" on Remote Machine
Error: An unexpected DCOM error occurred trying to contact the remote computer. Access is denied
Error: The Microsoft Visual Studio Remote Debugging Monitor on the remote computer is running as a different user
Error: Unable to Automatically Step Into the Server
Error: Workgroup Remote Logon Failure
Error: The Visual Studio Remote Debugger service on the target computer cannot connect back to this computer
Error: The Microsoft Visual Studio Remote Debugging Monitor (MSVSMON.EXE) does not appear to be running on the remote computer.
Unable to Connect to the Microsoft Visual Studio Remote Debugging Monitor
Error: Unable to initiate DCOM communication
Error: Remote computer could not initiate DCOM communications
Error: Firewall on Local Machine
Error: Firewall on Remote Machine
Error: Firewall No Authentication
Error: RPC Requires Authentication
Error: Unable to connect to the machine <name>. The machine cannot be found on the network.

Other Resources

Remote Debugging Setup

Did you find this helpful? Yes No

Not accurate

Not enough depth

Need more code examples

(1500 characters remaining)

Community Content Add

FAQ

Error "Unable to start debugging / Access is denied"

What about the error "Unable to start debugging / Access is denied"? User acct on local machine is different from user acct on remote.

MSVMON is really very useful, but getting it to work is a PAIN. The docs don't explain how to decide which options to use, and the error messages are so vague you can't tell what's wrong.

History

12/10/2011
VoiceOfExperience