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.
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. :-(
I'm taking the first steps in android development. Started working through this guide https://developer.android.com/training/basics/firstapp/running-app and the error occurred when the program is run on the device.
First of all, my device is not in the list of connected in Android Studio:
adb devices doesnt see my device when Android Studio is running, but if I close Android Studio, adb devices shows my device
When Android Studio starts, it shows an error and logs all the time this error flashes:
I tryed this this solution but it didnt solve my problem:
I dont know, why Android Studio try to connect to weird address localhost/127.0.0.7:5037?
I forgot. I edited /etc/hosts and commented line
#127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
After uncommented the line and restarted the Android Studio, I've solved my problem.
in my case in /etc/hosts I had the following line that i removed
0.0.0.0 localhost
I've catched this error under:
Android Studio 3.1.4
Android Debug Bridge version 1.0.32, Revision eac51f2bb6a8-android
Also i'm working in the office with some active firewall, antiviruses, monitoring etc.
My local host in the "/etc/hosts" was commented.
I solved this issue, but it was only an adb connection problem.
First, you have to enable all features in a device's developer menu
(debug with USB, upload via USB, usb connection type - charge only),
security menu (allow unknown sources);
Second, you have to set an allowance on the device to accept commands
from a current PC. Some devices do not show a dialog. To force this,
open a terminal console in the Android Studio, type in a command
"adb logcat" (this push adb to connect with current device), you
should see a dialog on the device's screen. Choose "Allow". To exit
from logcat command, press ctrl+x/ctrl+c or ctrl+break;
After this, you should see the device in the Studio's logcat drop box as [disconnected];
Open the consloe again and type "adb wait-for-device", this should set a stable connection with device.
It helped me.
I had a similar issue with Android Studio 3.3.1 (MacOS) when I run my app, it could not detect any devices in the Select Deployment Target dialog window after initializing adb. It produced the following error:
Unable to open connection to: localhost/10.0.2.2:5037, due to: java.net.ConnectException: Connection refused
I checked in /etc/hosts, and found the following line:
10.0.2.2 localhost
Commenting out that line solved the issue.
In windows 10 I to need add path of ADB directory to environment PATH. And It helps.
The problem can be due to the fact that it is missing the adb driver for the specific phone, as you can verify from the device manager.
You have to donwload and install it from the manufacturer, if it is available.
In my case, this seems to be still an open issue, but I've finally found the correct driver and installed it, as suggested in the developer documentation, by following the appropriate links (in my case I landed in a xiaomi Chinese page, containing the link to the rar archive of the working driver).
Having done that first, I could finally see an unauthorized device from adb devices (before that, no device was found instead, since it was unrecognized at the operating system level in the device manager) and, eventually, the suggestion from Sergio, typing adb logcat in the terminal, finally prompted the authorization from the device.
Issue solved!
Check if the port is binded to any other connection in your computer. This may be the error which is caused de to ports inavailability.
This Error ConnectException is caused due to SocketException so i will start digging with the port's status.
I am receiving an intermittent (but extremely frequent) error when attempting to debug my web app using Visual Studio 2012 and IE 11 via f5.
The error is a message box: "Unable to start program 'http://localhost:36422/default.aspx'. Access is denied."
Internet explorer opens, but no page is loaded.
If I retry enough times, it will eventually succeed, my app loads and I can debug.
I have noticed via task manager that when the error occurs, the internet explorer process is hanging around after I close it. The number of ie processes continues to build up until I have to kill them.
I am getting a large number of errors in my system event log which may be related (although an entry is not generated every time the error occurs):
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{0C0A3666-30C9-11D0-8F20-00805F2CD064}
and APPID
{9209B1A6-964A-11D0-9372-00A0C9034910}
to the user my user name SID (S-1-5-21-1364137996-2577644926-3768900005-1179) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
A google search of the guid indicates that the application in question is Machine Debug Manager.
I have tried adding the interactive user to the access permissions for Machine Debug Manager using dcomcnfg and rebooting my pc to no effect.
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)