Failed to parse the output of 'adb version'?

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 - He开发者_Go百科lloAndroid]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?

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

If you have comodo internet security installed, you dont have to shut this feature down:

1. run comodo settings
2. defense+
3. list active processes
4. add adb.exe to trusted processes
5. restart server: run "adb kill-server" "adb start-server"

EDIT: For user of Comodo 6.x

1. Open Comodo
2. Click Tasks Icon at right top
3. Click Advanced Tasks
4. Click Open Advanced Settings
5. Select Security Settings --> File Rating --> Trusted files from left panel
6. Click on the upward arrow icon at the bottom
7. Click Add --> add the adb.exe

there you go :) Hope this helps

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

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.

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.

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

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

Option 2:

1. Open the task manager.
2. kill the adb process.
3. start the eclipse.

Problem should be solved.

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.

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

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.