The remote debugger may be running under a different user account. This message may occur for several reasons:Ī DNS issue is preventing the connection. The remote computer exists, but Visual Studio could not connect to the remote debugger. The requested name was valid, but no data of the requested type was found To get the correct version of the remote debugger, see Remote Debugging. The remote debugger version does not match Visual Studio. Make sure the firewall is not blocking your request, especially if you are using a third-party firewall. This message may occur for several reasons: Visual Studio could not connect to the remote debugger. There is no server by the specified name running on the remote computer Otherwise, try restarting Visual Studio with Administrator privileges, and then try again.Īn internal error occurred. If you are trying to connect using a host name, try an IP address instead.Ĭheck the application log on the server (Event Viewer on Windows) for more detailed information to help resolve the issue. If you are using Attach to Process to debug: If you are debugging an Azure App Service app, try following instructions in Remote debug ASP.NET Core on Azure to connect to Azure App Service. Connection with the remote endpoint was terminated If these values are correct and the message mentions Windows Authentication mode, check that the remote debugger is in the correct authentication mode ( Tools > Options). In the Attach to Process dialog box or in the project properties, make sure that the remote computer name and the port number matches the name and port number shown in the remote debugger window. If these steps do not resolve this error, see The remote machine is not reachable.Ĭonnection request was rejected by the remote debugger This will show processes if you are connected under a different user account. If you are attaching to the process and you connect successfully but don't see the process you want, select the Show processes from all users check box. The computer name must be the following format: Make sure that you enter a valid computer name and port number in the Attach to Process dialog box or in the project properties (To set properties, see these steps). The debugger was unable to resolve the specified computer name The debugger cannot connect to the remote computer. A security package specific error occurred.The Visual Studio Remote Debugger on the target computer cannot connect back to this computer.The requested name was valid, but no data of the requested type was found.There is no server by the specified name running on the remote computer.Connection with the remote endpoint was terminated.Connection request was rejected by the remote debugger.The debugger cannot connect to the remote computer.Here are a few of the more common error messages that are appended to the main error message: Usually, a more specific message is included in the error string and that may help you identify the cause of the problem or search for a more exact fix. The Unable to Connect to the Microsoft Visual Studio Remote Debugging Monitor message is generic. If you need more help, see Developer Community for ways to contact Microsoft. If you believe you have received this message because of a product bug, please report this issue to Visual Studio.
0 kommentar(er)
