Error: Remote Debugging Monitor Does Not Appear to Be Running on the Remote Computer
The document is archived and information here might be outdated

Error: Remote Debugging Monitor Does Not Appear to Be Running on the Remote Computer

When trying to do remote debugging, you may get the following error message:

Error: The Microsoft Visual Studio Remote Debugging Monitor (MSVSMON.EXE) does not appear to be running on the remote computer.

This error means that Visual Studio could not find an instance of the Remote Debugging Monitor on the remote computer. The Remote Debugging Monitor is required for remote debugging to work.

If you are trying to connect to an instance of the Remote Debugging Monitor running under a different user account, you need to tell the debugger the name of the instance of msvsmon.exe to connect to (for example: user_name@computer).

To correct this error

  1. Make sure the remote machine has access to the Remote Debugging Monitor.

    1. If you are debugging a Windows client application, create a file share on the Visual Studio machine and run the remote debugger off this file share. Make sure the remote machine has access to the file share.

    2. If you are debugging an ASP.NET application or other server application, run Visual Studio setup on the remote machine and use the Visual Studio 2005 Remote Debugger Configuration wizard to enable the remote debugger service.

    For additional details, see How to: Set Up Remote Debugging.

  2. Start the Remote Debugging Monitor on the remote machine. See How to: Run the Remote Debugging Monitor.

See Also

Show:
© 2016 Microsoft