Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Remote debugging uses Distributed Component Object Model (DCOM) to communicate between the local and remote computers in the following situations.
- Debugger compatibility options labeled as Native only or Managed only are checked. These options are located in the Tools > Options pane under the All Settings > Debugging > General section and other sections, as applicable.
- Debugger compatibility options labeled as Native only or Managed only are checked under Tools > Options in the Debugging > General section.
- The debugger Native Compatibility Mode or Managed Compatibility Mode option is checked. These options are located under Tools > Options > Debugging > General.
You're debugging managed C++ (C++/CLI) code.
In earlier versions of Visual Studio, when the Enable native Edit and Continue option is checked in the Tools > Options > Debugging page.
Some non-Microsoft debugging scenarios.
This error occurs when the Visual Studio process can't authenticate itself (or the supplied credentials are deemed insufficient) to the remote debugger process over DCOM. One or more of the following workarounds might resolve the issue:
Turn off the Native Compatibility Mode and Managed Compatibility Mode options.
In earlier versions of Visual Studio, turn off the Enable native Edit and Continue option.
Reboot both computers.
If remote debugging requires entering credentials, check the option to save the credentials.