I've been unable to get Visual Studio, running on my development machine, to successfully deploy to a Surface Book on my local network. Error message is included below. On the Surface Book I've installed Remote Tools for Visual Studio, and set up Developer Mode. VS on my development machine shows me the SB, and allows me to select if from a list of deployment targets, including it's Authentication type, but deployment fails.
There is a "pair" option on the SB, which I haven't been able to make work & I'm not sure if it's necessary. In addition, I saw a post saying this option (local network) was no longer supported. Is it still supported, and if so, any idea what I'm doing wrong?
Error Message:
Error DEP6957: Failed to connect to device '10.0.0.179' using Universal Authentication. Please verify the correct remote authentication mode is specified in the project debug settings. COMException - Error HRESULT E_FAIL has been returned from a call to a COM component. [0x80004005]
To remote debug a uwp app, we should install the corresponding version Remote Tools for Visual Studio, before we can deploy the app to the remote device, we should configure the Remote Debugger tool. See the Run UWP apps on a remote machine in Visual Studio for details.
For your this issue, it should be you select the Windows authentication mode in your Visual Studio as the follow image, but you don't have access to the credentials of the signed-in user of the target machine. In your VS, you should use the credentials of the signed-in user of the target machine to deploy your app when the VS popup the permission window. See the Authentication modes to learn the differences.
On the other hand, you can also try to use the None authentication mode to remote deploy your app as the following steps.
Firstly, in the Visual Studio Remote Debugger of the target device, select Tools=> Options to configure the options Window as bellow,
Then in your Visual studio, right click your UWP project=> properties=> Debug to cofigure it as None authentication mode.
The answer from Breeze Liu was very helpful, and got me most of the way to the solution. The final step that I was missing was to add my account to the Remote Debugger's permission list. It's found at Remote Debugger>Tools>Permissions. I had to add my account on the target machine to the list of "permitted" debuggers.
Related
I'm trying to use remote debugging to test an application on a Surface Hub. On my local machine, I'm using VS 2017. Both the local Windows 10 machine and the Surface Hub are running Creator's Update (15063). The Surface Hub and the local machine both have "Developer Mode" enabled.
I've set the authentication to Universal and put the Hub's IP address in as the remote machine name. When I press the Debug button, the Hub puts up a dialog with this:
C:\ProgramData\DeveloperTools\VSRemoteTools\x64\coreclr\CoreCLR.
dll is either not designed to run on Windows or it contains an error. Try
installing the program again using the original installation media or
contact your system adminsitrator or the software vendor for support.
Error status 0xc0000428.
And on my local machine I get this:
DEP0100: Please ensure that target device has
developer mode enabled. Could not obtain a
developer license on 10.10.1.17 due to error
80004005.
Googling around I found that 0xc0000428 is usually a digital signature issue.
I'm aware that I can package up the app and install test certificates and stuff. But I'm hoping there's a way to get VS 2017's debugger to work the way the documentation says it is supposed to.
This is an known bug that got introduced in Visual Studio 15.3 update (CoreCLR did not get signed with certificates required by Surface Hub). It is also tracked here: https://developercommunity.visualstudio.com/content/problem/107166/visual-studio-153-isnt-able-to-remote-deploy-uwp-a.html
It should be fixed in next Visual Studio update.
I want to use Remote Debugger in Visual Studio 2015 to attach to my site. When I try "Attach Debugger" the azure return:
The following error occurred while launching remote debugging: Unable to connect to the Microsoft Visual Studio Remote Debugger name 'XXXX'. Windows authentication was unable to establish a secure connection to the remote computer.
In azure portal I set remote debugging and select VS 2015.
These errors might be related to Local Policies > Security Options > Network Security: LAN manager authentication level. It needs to be set to “Send NTLMV2 response only”. Once this is set then the PC was able to open RemoteApp applications without problems.
To set local policies go to command prompt and type secpol.msc or Administrative Tools > Local Security Policy
Maybe your application is not enabled to use remote debugger.
To enable remote debugger in app service:
Go to Azure management portal
Select your app
Go to settings
Go to Debugging
Enable Remote Debugging
Select your visual studio debugger versión
As much as it pains me to provide this as a solution, have you tried closing and re-opening Visual Studio? (In particular if you were able to connect at one point and it stopped working.) This has solved this issue for me on multiple occasions.
Changing my network connection appeared to solve this for me. To do this, I:
Open Networking and Sharing Center
Change adapter settings
Disable the currently-active network adapter (ethernet in my case)
Enable another network adapter (WiFi in my case)
After that, Visual Studio debugged the app service.
I am trying to debug a webservice remote on Microsoft Azure. The service is running in a web role.
I have configured remote debugging in the publish settings an can attach the debugger to the web role. Also, when I have selected the correct process, the debug symbols are loaded correctly and breakpoint's tool tips say that the breakpoint is hosted in "WallSHost.exe" which is the remote process.
What I would like to do, is to run a local client software which I am developing and step into the server code from there. When I step into the according service client call (F11), I get the above error message, saying (for the sake of Google in plain text here):
Unable to automatically step into server. Connecting to the server
machine 'xyz.cloudapp.net' failed. The Microsoft Visual Studio Remote
Debugging Monitor (MSVSMON.EXE) does not appear to be running on the
remote computer. This may be because a firewall is preventing
communication to the remote computer.
I have tried to disable the firewall on my (the client) machine with no effect. Has anybody seen that before or can tell me how fix this problem?
A quick checklist
deployed cloud service is a debug build
a debug build is selected from Build Configuration list (in publish wizard)
'Enable Remote Debugger For All Roles' is checked
no changes to code since deployment
Hello i have a problem with remote debugging in Visual Studio (v12)
I Created windows azure account i published application to the cloud.
Then i connected to this account through remote desktop. Address of remote computer is f.e Iron.app.net
Then i downloaded there and run remote debugger. I started msvsmon.exe and it created server named:
RD0015555E2:555
And now i would like to remote debugging in my host.
i know i must attach to process. And i do it.
From Visual Studio: Debug->attach to process->Qualifier:RD0015555E2 and it cannot resolve host name.
i also tried Iron.app.net but then it shows error that it seems that msvsmon is not installed.
I dont know what should i type into Qualifier (as remote machine)?
Remote debugging is tricky to configure Windows Azure Cloud Services. Other options that you have are:
Intellitrace (in case you've got Visual Studio Ultimate)
Intensive (verbose) pro-active code instrumentation (logging) from the beginning.
Profiling Cloud Service
Chose either, and watch your logs/traces.
Or deep dive into Remote Debugging Cloud Services. I would, however use Remote Debugging as a final option, when everything else does not work and does not help me. Typically most of the issues that would pop in the cloud will also pop in when debugging locally. And if role is just recycling, you will not be able to attach debugger at all.
I have a c++ program running on a remote machine.
I'd like to debug it from my machine.
I've installed remote debugging services (msvsmon.exe ) on the server.
Firewalls are not active not in the client nor in the server.
The program is running on the server (.pdb file is also there).
In the client I open the project in VS2010 , I go to debug->attach to process.
In the qualifier field I copy the value of the server name in msvsmon.exe.
When I hit enter, I get an error prompt saying :
"Unable to connect to Microsoft Visual Studio Remote Debugging Monitor named Administrator#TESTER1, the requested name is valid, but no data of the requested type was found"
In the server, the Authentication mode in msvsmon.exe is set to Windows Authentication.
Any help will be much appreciated.
Regards,
Omer.
Take a look at:
How to: Set Up Remote Debugging from Microsoft
Remote debugging with Visual Studio 2010 from CodeProject
In your case, take note of the suggestions regarding native debugging and windows authentication.
In my experiences with remote debugging a machine that is on my local network, I bypass windows authentication and setup the remote msvsmon.exe to allow anyone to connect to port 4015. So, then in the 'Attach to Process' dialog I select Transport > Remote (Native only with no authentication) and for the Qualifier I enter TESTER1:4015 or TheIPAddress:4015 if the name of the PC cannot be resolved.