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 still need help to get your problem resolved, contact Azure Support.If you believe you have received this message because of a product bug, please report this issue to Visual Studio. Set the correct account for the terminal services: Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\services\termservice' -name "ObjectName" "NT Authority\NetworkService" -Type String -force Set the size of the token to its maximum value: Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters' -name "MaxTokenSize" 65535 -Type DWord -force Set the following registry key value to ignore the profile loading error: Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server' -name "IgnoreRegUserConfigErrors" 1 -Type DWord -force Set-Acl -Path " HKLM:\SOFTWARE\Microsoft\SystemCertificates\Remote Desktop\Certificates " -AclObject $NewAcl $NewAcl.SetAccessRule($fileSystemAccessRule) $fileSystemAccessRule = New-Object -TypeName -ArgumentList $fileSystemAccessRuleArgumentList $fileSystemAccessRuleArgumentList = $identity, $fileSystemRights, $type $identity = "BUILTIN\Remote Desktop Users" If this permission is not granted, run the following commands to grant Read access to the Remote Desktop Users group: $NewAcl = Get-Acl -Path " HKLM:\SOFTWARE\Microsoft\SystemCertificates\Remote Desktop\Certificates" After each step, restart the VM, and check whether the problem is resolved.Ĭheck whether the Remote Desktop Users group has the Read permission for the following key: Get-Acl -Path "HKLM:\SOFTWARE\Microsoft\SystemCertificates\Remote Desktop\Certificates" | Format-List For more information,see How to use remote tools to troubleshoot Azure VM issues.Īfter you connect to the VM by using PowerShell, follow these steps to troubleshoot the issues. If the Azure Serial Console does not work, connect to the VM by Remote PowerShell. Then, connect to the VM by using the Azure Serial Console, and start a PowerShell session. This token (also called an authorization context) includes the security identifiers (SID) of the user together with the SIDs of all of the groups that the user belongs to.īefore you begin troubleshooting, back up the OS disk. Windows builds the token to represent the user for authorization. This situation occurs if the user belongs to many Active Directory (AD) groups and nested AD groups.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |