自 SDK API 9 升级以来 DDMS 抛出 ADB 错误
我今天升级到 Gingerbreak 2.3 SDK，并在尝试运行 DDMS 时开始收到此错误：
获取adb版本失败：无法运行程序“adb”：CreateProcess error=2，系统找不到指定的文件。
我该如何解决这个问题？运行 Windows 7，64 位。
I upgraded to Gingerbreak 2.3 SDK today and started receiving this error when I try to run DDMS:
Failed to get adb version: Cannot run program "adb": CreateProcess error=2, The system cannot find the file specified.
How can I fix this? Running Windows 7, 64bit.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
看来 adb.exe 现在位于 SDK 的 platform-tools 文件夹中。我必须将 platform-tools 文件夹添加到我的 我的环境变量中的路径。
It seems that adb.exe is now in the SDK's platform-tools folder. I had to add the platform-tools folder to my PATH in my Environment Variables.
昨天我尝试使用新的 2.3 SDK 和相关的 ADT 来升级我完美运行的 Android 开发系统。升级后，我无法让 Eclipse 正确编译我的项目，也无法从 Eclipse 访问 Android SDK 和 AVD Manager。 Eclipse 似乎丢失了 Android SDK 的安装位置。我会给它文件夹的名称，但随后它可能会返回说找不到.../tools/adb.exe。是的，我知道 adb.exe 已移动。但请注意，错误是在旧位置寻找它。就好像我没有新的 ADT，但我检查了一遍又检查了一遍，然后我就做到了。我认为新的 ADT 由于某种原因没有正确安装，和/或我没有正确检查它的版本。
当我四处寻找解决方案时，每个人都指出 adb 已移动并且类路径需要更改。但在这种情况下并没有真正相关的类路径。只需要在 Eclipse 中设置 Android SDK 的路径即可。我什至尝试了将 adb.exe 复制回工具文件夹的技巧。那时，Eclipse 可以找到 Android SDK，但随后出现了其他一些问题，所以我放弃了这个漏洞。
不管怎样，我最终把 eclipse 和 Android SDK 文件夹都扔掉了，然后重新开始。现在效果很好。我确信有更好的解决方案，但我厌倦了搞乱它。
我现在是 2 for 4 使用 Android SDK 和 AVD Manager 进行升级。
希望这对某人有帮助。
更新：经过进一步审查，我似乎把我的 stackoverflow 主题搞混了，因为 OP 从未提到过 Eclipse。
I tried to upgrade my perfectly working Android dev system yesterday with the new 2.3 SDK and associated ADT. After the upgrade, I couldn't get Eclipse to compile my project correctly, nor could I access the Android SDK and AVD Manager from Eclipse. Eclipse seems to have lost track of where the Android SDK was installed. I would give it the name of the folder, but then it could come back saying it couldn't find .../tools/adb.exe. Yes I know adb.exe moved. But notice that the error was looking for it in the old spot. It's like I didn't have the new ADT, but I checked and rechecked and I did. I'm thinking that the new ADT didn't install correctly for some reason, and/or I wasn't checking it's version properly.
When I searched around for a solution, everyone pointed out that adb moved and that the classpath needed to change. But there isn't really a relevant classpath in this situation. There is just a path to the Android SDK that needs to be set in Eclipse. I even tried the trick were I copied adb.exe back to the tools folder. At that point, Eclipse could find the Android SDK, but then some other problem that crept up so I gave up on that hole.
Anyway, I ended up blowing away my eclipse and Android SDK folders and starting over. Now it works fine. I'm sure there's a better solution, but I was sick of messing with it.
I'm now 2 for 4 on using Android SDK and AVD Manager to do an upgrade.
Hope this helps someone.
Update: Upon further review, I seem to have my stackoverflow topics mixed up since the OP never mentioned Eclipse.
我遇到了同样的问题，它的工作原理是这样的。首先运行 adb.exe ，然后打开 ddms.bat
I had the same problem and it works like this . First run adb.exe , after open ddms.bat