Failed to parse the output of 'adb version'?
Solution 1
Yes i had the same problem after i had did the update,
however, i have just fixed it :) TO FIX THE PROMBLEM:
in folder: \android-sdk-windows\ go to folder \platform-tools ; copy the files and paste in to folder \tool
Restart the Eclipse
Solution 2
turned off COMODO Defense+ module and all worked....
Solution 3
If you have comodo internet security installed, you dont have to shut this feature down:
- run comodo settings
- defense+
- list active processes
- add adb.exe to trusted processes
- restart server: run "adb kill-server" "adb start-server"
EDIT: For user of Comodo 6.x
- Open Comodo
- Click Tasks Icon at right top
- Click Advanced Tasks
- Click Open Advanced Settings
- Select Security Settings --> File Rating --> Trusted files from left panel
- Click on the upward arrow icon at the bottom
- Click Add --> add the adb.exe
there you go :) Hope this helps
Solution 4
I messed with all the solutions provided above, but I found another one-
Try launching eclipse with administrator privileges
RUN AS ADMINISTRATOR
hope it'll do the job.
Solution 5
After installing 2.3 SDK I got adb inside D:\AndroidSetup\android-sdk- windows\platform-tools directory. I had set this path in environment variable and my problem is solved.
Mohit Deshpande
I am a researcher at The Ohio State University in the field of computer vision and machine learning. I have worked as a mobile apps instructor for Zenva and current work as a writer for Zenva in machine learning.
Updated on July 25, 2022Comments
-
Mohit Deshpande almost 2 years
I am running Windos 7 and Eclipse 3.5 and I don't know why I keep getting this error. When I try run the program it gives me:
[2010-02-13 23:09:41 - HelloAndroid]The connection to adb is down, and a severe error has occured. [2010-02-13 23:09:41 - HelloAndroid]You must restart adb and Eclipse. [2010-02-13 23:09:41 - HelloAndroid]Please ensure that adb is correctly located at 'C:\Users\Mohit\Documents\AndroidSDK\tools\adb.exe' and can be executed.
I even tried runing Eclipse and adb.exe as admin. What is going on? How can I fix this and start making Android apps?
-
Mohit Deshpande about 14 yearsWell I tried to kill and start the server. So I guess the problem is the blocked 5037 port. So how do I unblock it? (I am running Windows 7 Pro)
-
VonC about 14 years@Mohit: since
netstat -o
does include the process id (PID) in its output, you could try and kill any process linked to that port. -
Mohit Deshpande about 14 yearsWeird, port 5037 is not listed. The closest thing to it would be the 5040 port.
-
VonC about 14 years@Mohit: depending on your configuration, the port number might be different. A tool like a Process Explorer (technet.microsoft.com/fr-fr/sysinternals/bb896653.aspx) can show you if the
PID
associated with that port number is aabd
one. -
VonC about 14 years
netstat
will not list directlyabd
. Did you mean your Process Explorer does not display anyabd
process? -
Dominic Tancredi about 13 yearsThere's a file in /tools called "adb_has_moved.txt" that explains this issue and says you need to update the PATH vars to include /platform-tools. Ram's right.
-
ol0 over 11 yearsIndeed it was COMODO's fault in my case
-
Menion Asamm almost 11 yearsomg, after more then half a day re-installing, testing etc ... damn COMODO and thanks Cool Khan!!
-
xorinzor almost 11 yearsit was the behavior blocker in my case that did evil, disabling it when starting Eclipse works
-
Ahamed over 10 yearsAdd the adb.exe to trusted files. It will work like a charm. No need to turn off comodo.
-
Owen B over 10 years+1 for checking Comodo, dammit! What's annoying is that i'd already exited Comodo from the tooltray, so had foolishly assumed it couldnt be affecting me. Restarted, added to the defense+ list and we're good.
-
PolyMesh about 10 yearsI tried pretty much everything else I could find on the subject of adb.exe hanging/freezing, nothing else worked. Thanks. Hope it keeps working!