Failed to parse the output of 'adb version'?

Question

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?

I am running Win7 and it is working fine here - hence not a win7 problem but rather a configuration problem with your system. Did you check that the add.exe is located at C:\Users\Mohit\Documents\AndroidSDK\tools\adb.exe ? — jax, Feb 14 '10 at 08:16

score 25 · Answer 1 · answered Jul 16 '11 at 06:21

25

turned off COMODO Defense+ module and all worked....

answered Jul 16 '11 at 06:21

Cool Khan

361
1
3
4

Indeed it was COMODO's fault in my case – ol0 Sep 15 '12 at 19:08
1

omg, after more then half a day re-installing, testing etc ... damn COMODO and thanks Cool Khan!! – Menion Asamm May 18 '13 at 14:16
it was the behavior blocker in my case that did evil, disabling it when starting Eclipse works – xorinzor Jun 04 '13 at 16:09
1

Add the adb.exe to trusted files. It will work like a charm. No need to turn off comodo. – Ahamed Jan 22 '14 at 19:24

score 20 · Answer 2 · edited Jan 22 '14 at 19:23

20

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

edited Jan 22 '14 at 19:23

Ahamed

39,245
13
40
68

answered Jan 24 '12 at 15:00

John Rumpel

4,535
5
34
48

+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. – Owen B Jan 23 '14 at 20:47

score 12 · Accepted Answer · answered Dec 09 '10 at 13:42

12

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

answered Dec 09 '10 at 13:42

LTEHUB

1,638
1
14
17

score 3 · Answer 4 · answered Feb 12 '13 at 06:30

3

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.

answered Feb 12 '13 at 06:30

user2044187

107
1
1
10

I tried pretty much everything else I could find on the subject of adb.exe hanging/freezing, nothing else worked. Thanks. Hope it keeps working! – PolyMesh Apr 21 '14 at 16:50

score 2 · Answer 5 · answered Jan 31 '11 at 06:15

2

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.

answered Jan 31 '11 at 06:15

Ram

21
1

3

There'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. – Dominic Tancredi Mar 20 '11 at 23:22

score 2 · Answer 6 · answered Jun 30 '11 at 14:28

Two options to solve this problem on windows:
Option 1:

Close the eclipse, if it is running.
Run the command prompt.
Go to the tools location of the android sdk.
run 'adb kill-server'
then run 'adb start-server'.
start the eclipse.

Option 2:

Open the task manager.
kill the adb process.
start the eclipse.

Problem should be solved.

score 1 · Answer 7 · answered Jul 27 '11 at 02:18

1

What it work for me and this was because I move from one eclipse to another is to re install SDK and then re install ADT again, remove completly from eclipse ADT and re install.

answered Jul 27 '11 at 02:18

user456862

11
1

score 0 · Answer 8 · answered Jul 31 '13 at 22:36

0

force to start sdk manager several times (try directly from the file explorer). when you could do that comodo may send a mesage. allow the issue. then start again the sdk manager and update. update eclipse then.

answered Jul 31 '13 at 22:36

hieudev

1
1

score 0 · Answer 9 · answered Feb 14 '10 at 08:26

0

As illustrated by this thread, you may need to kill an exisiting abd process, or unblock the 5037 port (remnants of previous adb start attempts).

Try closing Eclipse, issuing a 'C:\Users\Mohit\Documents\AndroidSDK\tools kill-server' command from terminal and retrying.
If that still doesn't work, you could try opening Activity Monitor to see if there are any existing adb processes running, and kill them.

Hi, it's OK now, I'saw with the nestat - a command line that theer was several processus on the 5037 port. The port wich serves for the emulator.
Thanks

answered Feb 14 '10 at 08:26

VonC

1,262,500
529
4,410
5,250

Well 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) – Mohit Deshpande Feb 14 '10 at 17:14
@Mohit: since `netstat -o` does include the process id (PID) in its output, you could try and kill any process linked to that port. – VonC Feb 14 '10 at 19:11
Weird, port 5037 is not listed. The closest thing to it would be the 5040 port. – Mohit Deshpande Feb 14 '10 at 22:58
@Mohit: depending on your configuration, the port number might be different. A tool like a Process Explorer (http://technet.microsoft.com/fr-fr/sysinternals/bb896653.aspx) can show you if the `PID` associated with that port number is a `abd` one. – VonC Feb 15 '10 at 04:48
`netstat` will not list directly `abd`. Did you mean your Process Explorer does not display any `abd` process? – VonC Feb 15 '10 at 15:09

Failed to parse the output of 'adb version'?

9 Answers9

Linked