score:85

Accepted answer

recommended: delete <workspace-directory>\.metadata\.plugins\org.eclipse.core.resources\.snap. this will not reset your workspace and your other projects won't get deleted (as answered by krishna).

not recommended: alternatively, delete the the whole <workspace-directory>\.metadata directory from your workspace and restart.this will reset your workspace and delete all your existing projects in it.

score:0

solution: delete .metadata folder in your last workspace. reason: maybe you force shutdown/restart your computer, while your eclipse still running.

score:0

just a little tip that might help people avoid an issue that i encountered.

in my case there were multiple workspace directories on my machine. when i ran the mvn sonar:sonar goal then it created its own workspace directory, placed the snapshot (.snap files) in there, and changed a setting to tell maven to look there for changes first. however, this was not my workspace that i was using, so the snapshot was never being updated with my changes. so when maven used that snapshot it could not find the files in their old locations. so i had to eliminate that workspace to resolve the issue. this worked because maven then looked in the next workspace on its list, my workspace, for the snapshot instead of the one added (but never updated) by the sonar goal.

so you might need to search your entire hard drive for *.snap files to see if there is more one workspace being used on your machine.

score:0

check your environment variables _java_option path. i had hp uft installed on my system and i set _java_option to ignoreme_java_option for both system and environment variable. after reboot, eclipse showed the same error " check log file". removed the ignoreme and eclipse no issues. this could be another possibility that could be looked at to fix the eclipse.

hope this helps.

score:0

i also had the same problem, this happens when you force shutdown/restart your computer, while your eclipse still running. deleting .metadata folder worked for me. delete all the metadata and then import your project from that same workspace.

score:0

rather deleting whole .metadata folder, which in turns delete your projects from workspace, try to find the .snap files and delete them. .snap files are the snapshot of workspace's temporary instance which will be saved on clean & close of workspace.

score:0

delete all the *.snap files in the path workspace-directory>.metadata.plugins\org.eclipse.core.resources

score:1

had similar problem.

log file said exception was caused by corruption in the project tree -- a very vague description.

deleting individual files and directories in /.metadata/.plugins/org.eclipse.core.resources didn't work for me. i had to delete the entire /.metadata/.plugins/org.eclipse.core.resources directory. i lost the entire project tree but not the projects. they were still in the workspace and just needed to be imported back into eclipse. i also did not lose the large numbers of plugins configured for working java, android, php, c++, j2ee, etc.

this is the second time i encountered a project tree related corruption. the first time i deleted the .metadata altogether and then spent a very long time putting back all the plugins and projects. the direction the other answers here were useful in zeroing in on just the org.eclipse.core.resources directory. seems deleting the whole directory just results in only needing to reimport all the projects.

your mileage may vary...

score:1

this also works when you receive this error from information design tool (idt) (business objects bi4).

  1. delete .snap file from this directory.
    please note that you will lose all your local projects. hopefully your modifications have been recently saved to a repository.

directory - c:\users\xxxxuser.name.businessobjects\bimodeler_14\workspace.metadata.plugins\org.eclipse.core.resources\

score:1

for anyone interested, i had the exact same problem and deleting the file .metadata/.plugins/org.eclipse.core.resources/.snap did the trick for me.

score:1

use the clean option

i had this error. i start eclipse with "clean" option and that worked for me.

eclipse.exe -clean

eclipse starts and all projects ok.

score:5

deleting .snap file worked perfect for me.

  1. delete .snap file from the directory - workspace.metadata.plugins\org.eclipse.core.resources.
  2. import the workspace (existing projects into workspace - do not copy folders into workspace again).

score:14

ran into this error.

there was no .snap file in my .metadata folder.

i had to delete this:

<workspace>/.metadata/.plugins/org.eclipse.core.resources/.root/d+.tree

d+=> some number.

then i had to re-import the projects and re-assign the working sets. i preferred it over opening a new workspace and redoing settings.

score:139

for this issue i had to delete the .snap file located in the directory :

<workspace-directory>\.metadata\.plugins\org.eclipse.core.resources

after deleting that file, i was able to start my eclipse with no problem.


Related Query

More Query from same tag