I want to use the remote debugger for VS2017.
But every time I started it on my VS machine I got the following error message:
"Could not launch debugger. Check the Debug settings.."
Do you have any hint, where can I get more information about the problem, like remote debgger not started, Proxy problem, settings... ?
Or how I can fix it ?
I setup the remote debugging connection for VS2017 on two Windows 10 machines.
On the remote debugging machine I started the tool by execution of msvmon.exe (by sharing the folder location on the machine, on which VS2017 is running).
It seems to run without any error, since a window was open with displays the machine name and the Port.
I copied then this information in the Remote Server Name field for the Visual studio debugger. I tried it with and without port number).
I also copied the debugger application to the same folder of the remote debugging machine, as it is on the VS machine.
After that I started the Remote Debugging session and the error message is shown.
Thank you very much!!
I could solve the issue. The problem was that the remote command parameter was not set. :-(
Related
I had a Windows 2008 Server which was being used as Application server that has recently been upgraded to Windows 2012 -> Windows Server 2016 -> Windows Server 2019.
All of the applications under IIS work, but one. I am trying to figure out what is wrong. I have installed Visual Studio 2019 Remote Debugging tool on the server and trying to attach to the erroneous project under IIS.
I have the Remote Debugger running
but when I try to attach to remote process the Application pool and user names do not show up in the "Attach to process" window.
Since I can not see the details I can not connect to my application and debug. I am sure that "Show processes from all users" is checked.
I know that if the application does not run on the server it does not show up in this list, but I have called other applications under the site which are running but they don't appear either.
Try run the remote debugger under the different user account:
You can stop the remote debugger and restart it with the account you are using on the local computer.
You can start the remote debugger from the command line with the /allow parameter: msvsmon /allow username#computer
You can add the user to the remote debugger's permissions (in the
remote debugger window, Tools > Permissions).
If you can't use the methods in the preceding steps, you can allow
any user to do remote debugging. In the remote debugger window, go to
the Tools > Options dialog. When you select No Authentication, you
can then check Allow any user to debug. However, you should use this
option only if you have no choice, or if you are on a private
network.
My development workstation is running VS2012 Update 1. The OS is Windows 7 Professional Service Pack 1 x64. I have a laptop running Windows 8 onto which I've installed the VS2012 Remote Debugger. I've started msvsmon and it's quietly sitting in the system tray or what passes for it on Windows 8.
I have set up a breakpoint in VS2012 at a location where I need to do some debugging. In VS2012, I click on Debug | Attach to Process... I get the dialog showing the list of processes running on my machine. I change the machine name to the name of the Laptop.
I am having two different problems:
Problem 1:
With Windows Firewall running, VS2012 connects to the remote debugger server. I see the list of the processes running on the Laptop. I choose the one I want to debug and click Attach. I get "Unable to attach to process. The RPC server is not available."
What's going on here?
Problem 2:
I turn off Windows Firewall on my desktop. When I try to connect to the process running on the laptop, it connects and loads all of the symbols. So far so good. Once all of that is finished, I perform the action that would cause my breakpoint to be hit. The process on the remote machine freezes, but so does VS2012. I've sat here as long as 10 minutes waiting with no change. At that point, I kill msvsmon on the remote machine and my program goes away with it, but VS is still locked up.
Any ideas??
I have faced a similar issue in VS 2013 showing the message "Unable to attach to process. The RPC server is not available".
I have resolved this by un-checking the "Use Managed Compatibility Mode" option from Debug > Options and Settings > General Tab.
I followed the instructions in this link: http://msdn.microsoft.com/en-us/library/bt727f1t.aspx to install the remote debugger (2012) on my server where the application is running in hope to debug it remotely from my dev machine running visual studio 2012.
I cannot even get as far as viewing the list of processes to attach to on the remote machine. I keep getting "Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor named [name]. Invalid access to memory location".
I have managed to successfully connect a few times but then the attach fails immediately then I cannot connect again.
This is causing huge issues for me as I cannot remote debug anything. I must be missing something glaring. Please someone give me a solution.
I've found the only way to correct this is by restarting Visual Studio.
Worked for me. I found it at this blog post about invalid access and remote debugging.
It turns out the one thing I missed was to tell Visual Studio where to find the .pdb symbols relating to the remote process. To do this go to Tools -> Options -> Debugging then in the Symbol (.pdb) locations add the remote location to the pdb files.
To clarify, I was attaching fine but could not break into code. Now I can. Be aware though that there are other hurdles before you get to my stage where I was attaching to the process successfully but could not catch a breakpoint.
I recently had someone else report this and debugged the issue on their machine. The "Invalid access to memory location" errors are due to an issue in Windows, it can be addressed with this hotfix.
I have had this problem in VS 2012, 2013, 2015 and 2017. Based on other answers it is likely that the problem is related to running a 32 bit version of Visual Studio on a 64 bit PC. Sometimes, as others have recommended, restarting Visual Studio fixes the problem but the best solution I've found so far is to start Visual Studio without a solution, open Debug -> Attach to Process, change the Connection Target to the remove server and wait for the process list to load. Then Cancel, do not attach yet. Load your desired solution and then come back to Attach to Process and the remote process list will still be loaded. Connect to your desired process and everything should work properly from then on.
I've installed Remote Tools for Visual Studio 2012 on a remote computer in the same domain.
I can ping and telnet connection to the defined port.
I'm trying to find the server when I open the "attached to process" dialog and the VS doesn't find it.
(I tried entering both its IP and Name)
Any idea?
I faced same issue. I was pressing on "Find..." button and there searching for the computer, that always gave me "Found 0 connection". It looks like a VS2012 bug.
However when I've entered computer name (IP address also worked for me) and port in the "Qualifier" field and then pressed "Refresh" button far below - only then the connection was established and the list of processes was displayed.
The format of the text in the "Qualifier" field was COMPUTER-NAME:PORT (e.g. WIN2012-TEST:4016) as well as IP-ADDRESS:PORT (e.g. 192.168.1.1:4016), both worked. The port was the one that is displayed in the Tools -> Options of the Remote Debugging Monitor running on the target machine.
I encountered the same error message, but ended up finding that it was a different issue that the one OP encountered.
My problem was that remote debugging tools are not cross-version-compatible (at least to some extent). In my case, VS 2013 could not connect to the 2015 Remote Debugging tools. I admit, I kind of expected it to work, but I'm not terribly surprised. It wasn't until I explicitly typed in the machine and port that I received an actionable error message.
I had the same option, neither the Find button nor the Refresh button could help me (Visual Studio 2013 and remote debugging 2013), I even tried computer name and IP address with port.
It worked out when I selected "Show processes from all users" and it loaded All processes.
I guess there's a delay with this tool and you might need to do some work around to fix this.
I'm trying to open my debugger for an Android project. The emulator opens fine, but the debugger is hanging and thus never fully loads. I keep getting this message, that never goes away:
"Attempting to connect debugger to 'com.example.android.myApp' on port 8616" (The connection never completes).
I am using Linux Ubuntu 10.10.
Thank you all for your help. :)
Matt
set the following flad in your AndroidManifest.xml in the tag application
android:debuggable="true"
Note following Article: Eclipse Android: Could not open Selected VM debug port (8700)
This aswell: Could not open Selected VM debug port (8700)