[Miscellaneous] A bloodshot case caused by pods-about ADB server didn 'Tack

Preface:

Finally, I went back to the blog Park and continued my technical blog journey. In fact, during this time, I experienced many things, changed my job, and started WP7 and Android development, for a developer who jumps from Windows Mobile, he has experienced many twists and turns. Today, I will record this annoying one: ADB server didn't ack ~~~~~ (You can search in Google ......)

Problem reproduction:

I wrote a lot this afternoon.CodeAfter you click the run button, eclipse reports an error to me:

[15:22:19-ADB] ADB server didn't ACK

[15:22:19-ADB] * failed to start daemon *

However, it was okay yesterday, so Google, keywords: ADB server didn't ACK, a lot of results, nothing more than the following:

• Restart eclipse
• Restart your computer
• Add Environment Variables
• ......

Try all of them one by one, but it still doesn't work. So do I !!!

Dark flowers:

During reading the post, one of the peers who are forced by the masses mentioned:

If Port 5037 is occupied, the following prompt will appear ......

As a result, it seems like a lifeline is found. First, enter the following command in the command line to check who is occupying the port 5037:

Netstat-a-o 5037

Then we get the following result, which is actually occupied:

So what process is this 4792 on my machine? OK. Then enter the following command to find out the culprit:

Tasklist/fi "pid eq 4792"

Then, amount ...... I'm depressed ...... It's actually a famous pea pod:

End:

Now, I have finished the process, restarted eclipse, and clicked run,ProgramAs before, the simulator is automatically opened and loaded. Although this problem is not very serious, most people have not encountered this problem on the Internet, so it is recorded here, hoping to help you.