android can not run the project, seeking to solve the great God. . . . . . . . . .

Great God seeking to resolve

Or a good run yesterday, today, we would not run

Specific Tip Figure:
<-! Main posts under Banner (D4) -><-! Posts under the main text (D5) ->
Reply:
The adb seems dead, and you try to restart the Eclipse, if not only re-install a new ADT development environment.
An integrated version of the official download, this error occurs rarely.
Reply:
Look like your SDK log path is also a problem, check.
Reply:

reference to the second floor birdsaction reply:

look like a log of your SDK path is also a problem, check.

Path should not have a problem, I can run a single run ADT ah is not running in the project which
Reply:
You see there is no other instance of ADB's pea pod QQ
Reply:

3 error:
The connection to adb is down, and a severe error has occured.
[2010-03-11 09:36:56 - HelloOPone] You must restart adb and Eclipse
.[2010-03-11 09:36:56 - HelloOPone] Please ensure that adb is correctly located at 'D: \ OPhoneSDK_1.5
\ Platform-tools \ adb.exe 'and can be executed.
Solve:
Methods 1.cmd in adb kill-server, then adb-startserver
Method 2 Method 1 does not work, then kill adb.exe in the Task Manager, and then restart Eclipse.
Method 3 Methods 1 and 2 do not work, then check the error in the last sentence: platform-tools if there adb.exe (my mistake is related to the path below in no platform-tools folder
So I chose to create a new folder, and the tools to copy all the files in the platform-tools)
4 summarizes the way in front of others, a situation I encountered was "pea pod" or "mobile assistant" class software takes up adb, stop "pea pod" and the adb adb reboot or in the Task Manager eclipse can be.
5 tried the previous method does not work, I suggest re-install a system, it is best to change the system. Some cattle also said: MS, there are some minor issues [size = large] [/ size]

A method on the network are all tried, and if not, see if you installed the 360 ​​security guards;
2, if there is also installed 360,360 adb.exe process, so the eclipse adb.exe does not start, resulting in adb not connect when debugging. 360 security guards to close the first run, after starting adb.exe, then start the 360 ​​security guards, there would be a problem.

Reply:
adb have problems, check adb port number is not being occupied.
Reply:
The adb kill and then restart the service, if not you can ask me. ,,,
Reply:
Although the fifth floor is the right way to say, but obviously the online copy. This also told LZ a message to the Internet to find themselves having problems before posting faster than here!
Reply:
This case, first inside DDMS restart adb (I still do not work here in general), does not work on the restart eclipse, I always stop in Task Manager directly inside the adb process, or not, it is probably the pea pods, QQ open Is there a process tadb adb look like, stop by.