This documentation is archived and is not being maintained.

Error: Unable to Attach to the Process. There is no Msvcmon on the Remote Machine Running Under the Current User Context

When trying to do remote debugging using TCP/IP, you may get the following error message:

Unable to attach to the process. There is no msvcmon on the remote machine running under the current user context.


This message means one of three things:

  • If you are debugging using the TCP/IP transport, the user who started msvcmon is not the user who is running Visual Studio.
  • If you are debugging using the default DCOM transport and attaching to a remote native application:
    • The remote machine is running Windows 95, Windows 98, or Windows Millennium Edition, and the user logged into the remote machine is not the user who is running Visual Studio.
    • - or -
    • You are trying to attach to a native C++ application through a remote terminal server session running under another user account.


Run Remote Debug Monitor (msvcmon.exe) on the remote machine using the –anyuser option:

msvcmon -tcpip -anyuser
Note   The –anyuser option allows anyone who has network access to connect to the machine for remote debugging, which could pose a serious security risk.

For more information, see Setting Up Remote Debugging.

See Also

Remote Debugging Errors and Troubleshooting | Remote Debugging Setup | Adding Debugger Users and Configuring DCOM