Reputation: 8176
I have worked today on a project, which had no errors, and after a sort break, when I re-opened eclipse, I got the following error:
I have tried searching for a solution, but the error is to long in length to find any results. I even downloaded the new 17 revision, but it didn't help.
Upvotes: 0
Views: 135
Reputation: 25757
So lets start by verifying the current version of ADT installed. Just in case:
In the new dialog you will see the ADT version. If this is NOT 17 then the error message does not lie and even though you may have tried to upgrade to version 17 it clearly has not. If it has then I would suggest a complete re-install of ADT and the SDK. You can follow the docs here http://developer.android.com/sdk/eclipse-adt.html#installing
One reason the update may have failed before you start pulling it all apart is that you may need to run eclipse as an administrator. I also find that SDK updates via the SDK manager have to be done as an administrator too.
When going from Eclipse to the SDK Manager I sometimes find that Eclipse has not started it with admin rights even though Eclipse has them. Therefore the update process then fails. I find it best to start the SDK manager with admin rights yourself, and then update the SDK manually and check the error log for any issues (normally the download works but then fails to copy the files for me if I am not in administrator mode).
EDIT/UPDATE:
Have you checked the ADT settings in Eclipse, especially the setting for SDK Location
? Does it point to your up to date copy of the SDK? If it is having trouble opening the SDK manager then it could be the SDK is broken after attempting an update. I would uninstall it completely then download a fresh copy.
Upvotes: 1