Eclipse won't start, log error says: ObjectNotFoundException: Tree element

Question

Last night my machine restarted while Eclipse Galileo was open. No big deal, right?

This morning, I started my machine and tried to open Eclipse. Instead of opening, I see this: alt text

The error log suggests that there is some kind of problem caused by exiting with unsaved changes.

How can I get Eclipse to open and ignore those unsaved changes? I can't even open a text file that is not part of this project with Eclipse? There must be a way to reset this state.

EDIT:

I have tracked down the problem to a single file. When I delete this file below, Eclipse opens but my projects are missing.

.metadata\.plugins\org.eclipse.core.resources\.snap

I do use the subversion plugin, but I don't think that is the problem. Here is what the error log says ( abbreviated ):

!SESSION 2010-08-17 10:13:01.718 -----------------------------------------------
eclipse.buildId=M20100211-1343
java.version=1.4.2_06
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_CA
Command-line arguments:  -os win32 -ws win32 -arch x86

!ENTRY org.eclipse.core.resources 2 10035 2010-08-17 10:13:02.656
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.

!ENTRY org.eclipse.osgi 4 0 2010-08-17 10:13:02.671
!MESSAGE An error occurred while automatically activating bundle org.eclipse.core.resources (33).
!STACK 0
org.osgi.framework.BundleException: Exception in org.eclipse.core.resources.ResourcesPlugin.start() of bundle org.eclipse.core.resources.
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:806)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:755)
...

Caused by: org.eclipse.core.internal.dtree.ObjectNotFoundException: Tree element '/reports/src/com/lang/reports/OnlineReport.java' not found.
    at org.eclipse.core.internal.dtree.AbstractDataTree.handleNotFound(AbstractDataTree.java:257)
...

Root exception:
org.eclipse.core.internal.dtree.ObjectNotFoundException: Tree element '/reports/src/com/lang/reports/OnlineReport.java' not found.
    at org.eclipse.core.internal.dtree.AbstractDataTree.handleNotFound(AbstractDataTree.java:257)
...

!ENTRY org.eclipse.osgi 4 0 2010-08-17 10:13:02.703
!MESSAGE Application error
!STACK 1
java.lang.NoClassDefFoundError: org/eclipse/core/resources/IContainer
    at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:114)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)

!ENTRY org.eclipse.osgi 2 0 2010-08-17 10:13:02.765
!MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists:
!SUBENTRY 1 org.eclipse.osgi 2 0 2010-08-17 10:13:02.765
!MESSAGE Bundle org.eclipse.jdt.apt.core_3.3.202.R35x_v20091130-2300 [103] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2010-08-17 10:13:02.765
!MESSAGE Bundle org.eclipse.jdt.apt.pluggable.core_1.0.201.R35x_v20090925-1100 [104] was not resolved.
!SUBENTRY 2 org.eclipse.jdt.apt.pluggable.core 2 0 2010-08-17 10:13:02.765
!MESSAGE Missing required bundle org.eclipse.jdt.apt.core_0.0.0.
!SUBENTRY 2 org.eclipse.jdt.apt.pluggable.core 2 0 2010-08-17 10:13:02.765
!MESSAGE Missing imported package org.eclipse.jdt.internal.compiler.tool_0.0.0.
!SUBENTRY 2 org.eclipse.jdt.apt.pluggable.core 2 0 2010-08-17 10:13:02.765
!MESSAGE Missing imported package org.eclipse.jdt.internal.compiler.apt.dispatch_0.0.0.
!SUBENTRY 2 org.eclipse.jdt.apt.pluggable.core 2 0 2010-08-17 10:13:02.765
!MESSAGE Missing imported package org.eclipse.jdt.internal.compiler.apt.model_0.0.0.
!SUBENTRY 2 org.eclipse.jdt.apt.pluggable.core 2 0 2010-08-17 10:13:02.765
!MESSAGE Missing imported package org.eclipse.jdt.internal.compiler.apt.util_0.0.0.
!SUBENTRY 1 org.eclipse.osgi 2 0 2010-08-17 10:13:02.765
!MESSAGE Bundle org.eclipse.jdt.apt.ui_3.3.200.v20090930-2100_R35x [105] was not resolved.
!SUBENTRY 2 org.eclipse.jdt.apt.ui 2 0 2010-08-17 10:13:02.765
!MESSAGE Missing required bundle org.eclipse.jdt.apt.core_[3.2.0,4.0.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2010-08-17 10:13:02.765
!MESSAGE Bundle org.eclipse.jdt.compiler.apt_1.0.201.R35x_v20090925-1100 [106] was not resolved.
!SUBENTRY 2 org.eclipse.jdt.compiler.apt 2 0 2010-08-17 10:13:02.765
!MESSAGE Missing imported package org.eclipse.jdt.internal.compiler.tool_0.0.0.
!SUBENTRY 1 org.eclipse.osgi 2 0 2010-08-17 10:13:02.765
!MESSAGE Bundle org.eclipse.jdt.compiler.tool_1.0.100.v_981_R35x [107] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2010-08-17 10:13:02.765
!MESSAGE Bundle org.eclipse.jdt.junit4.runtime_1.1.0.v20090513-2000 [116] was not resolved.
!SUBENTRY 2 org.eclipse.jdt.junit4.runtime 2 0 2010-08-17 10:13:02.765
!MESSAGE Missing required bundle org.junit4_[4.4.0,5.0.0).
!SUBENTRY 1 org.eclipse.osgi 2 0 2010-08-17 10:13:02.765
!MESSAGE Bundle org.hamcrest.core_1.1.0.v20090501071000 [184] was not resolved.
!SUBENTRY 1 org.eclipse.osgi 2 0 2010-08-17 10:13:02.765
!MESSAGE Bundle org.junit4_4.5.0.v20090824 [186] was not resolved.
!SUBENTRY 2 org.junit4 2 0 2010-08-17 10:13:02.765
!MESSAGE Missing required bundle org.hamcrest.core_1.1.0.
!SUBENTRY 1 org.eclipse.osgi 2 0 2010-08-17 10:13:02.765
!MESSAGE Bundle com.collabnet.subversion.merge_2.1.0 [208] was not resolved.

`java.vendor=Sun Microsystems Inc.` I think this may be the root cause! :) — pavanlimo, Aug 17 '10 at 17:38
try starting eclipse with another workspace and see if this works. — theomega, Aug 17 '10 at 17:39
No can do. Can't open another workspace. Can't open a text file not associated with any project. I'm stuck in limbo. — jeph perro, Aug 17 '10 at 17:42
Anyone know where the project state is kept? I don't see anything in the .metadata folder — jeph perro, Aug 17 '10 at 17:49
@pavanlimo Today it's `java.vendor=Oracle Corporation` and things didn't change — Lorenz Meyer, Dec 31 '13 at 13:20

score 143 · Answer 1 · edited Jan 22 '13 at 13:28

143

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.

edited Jan 22 '13 at 13:28

bluish

26,356
27
122
180

answered Oct 31 '11 at 21:48

Krishna

4,892
18
63
98

2

Worked without losing projects or tasks :) Eclipse Juno (2013). Thanks! – BurninLeo Apr 08 '13 at 09:42
2

Deleting the .snap or all .snap files recursively didn't fix it for me. – jfritz42 May 17 '13 at 16:06
This worked pretty nice on Version: Indigo Service Release 1 Build id: 20110916-0149 on OSX. Thanks go to Krishna and bluish. – retromuz Aug 20 '13 at 05:02
Awesome tip, man! This did it, without affecting the workspace. I had tons of config, so can't afford to reset the workspace. Thanks! – asgs Aug 27 '13 at 04:56
1

i was lost, now i am home :D thanx – Shoshi Jan 11 '14 at 13:37
1

@Krishna: thanks this solution for me but I just dont understand why did it occur in the first place! can u please explain? – Aarish Ramesh Mar 24 '14 at 06:14
Worked for me without loosing my Workspace. The only thing to do was Refreshing my projects to sync the Workspace with filessystem. My env: RHEL 7, Oracle JVM 7, JBDS 7.1 – Rafael Soares - tuelho Nov 07 '14 at 13:42
Removing the `.metadata/.plugins/org.eclipse.jdt.core` directory resolves too – Rafael Soares - tuelho Jun 02 '15 at 19:15
Deleting the .snap file from .metadata.plugins\org.eclipse.core.resources worked for me. Eclipse Luna then loaded ok and still had all its projects. Didn't have to make any other changes. – striker77 Dec 06 '15 at 10:48
2

This also worked with Eclipse Neon, though .snap was in /.metadata/.plugins/org.eclipse.core.resources/.root – Antonio Malcolm Dec 10 '16 at 20:39
For me, on neon on RH, I had file org.eclipse.core.resources/14.snap. What is that all about? Worked anyway, thanks. – wmorrison365 Jun 15 '17 at 16:56
This removed my projects and basically made me have to start from scratch, so a downvote from me. – Matt Aikens Sep 28 '20 at 17:41

pavanlimo · Accepted Answer · 2017-07-18T22:51:26.923

95

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.

edited Jul 18 '17 at 22:51

answered Aug 17 '10 at 17:58

pavanlimo

4,122
3
32
47

2

Thanks, this helped me. I was at least able to restart eclipse after I deleted the .snap file in .metadata. Unfortunately I lost all my projects. In the end I had to re-checkout all my projects from subversion. But at least I am up and working again. – jeph perro Aug 19 '10 at 16:27
1

Got exactly the same here, damn. – Frank Meulenaar May 07 '11 at 06:05
Just happened to me - right in the middle of integration testing. Lost the server setup etc etc etc – Steve De Caux May 19 '11 at 13:39
11

I think the correct answer should be the one below. Above resets your whole workspace, below in the other hand keeps everything you did as it is. – retromuz Aug 20 '13 at 05:04
worked great. I couldn't open an existing workspace. I deleted my .metadata directory, then just re-imported the existing projects into the workspace. – GothamNite May 16 '14 at 02:36
2

Why was this the accepted answer. Completely borked my install, and I have spent the next few hours fixing it. – wobbily_col Aug 11 '14 at 12:27
1

Could you please update the answer to explain that it removes all your project setups? If you are in a hurry and not so experienced with Eclipse you get very frustrated when all your configuration is gone. Still your solution solves the problem, but with an undesired effect. So you still get an upvote. – muthee Apr 20 '15 at 05:21
thanks... i was stuck in appcelerator not working with the same error – cosmoloc Jul 15 '16 at 07:07
Edited my answer to include krishna's answer, so that other people don't reset their workspace. If OP is reading this, please mark krishna's answer as accepted instead of this. – pavanlimo Jul 18 '17 at 22:56
Thanks, the recommended solutions helps. My eclipse Mars.2 Release (4.5.2) didn't start beforehand. – ulyssis2 Aug 14 '19 at 06:05

score 15 · Answer 3 · answered May 30 '12 at 12:25

15

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.

answered May 30 '12 at 12:25

trappedIntoCode

804
8
13

1

This worked for me. Was a pain to re-create my projects but the other answers didn't help me. – jfritz42 May 17 '13 at 16:07
this worked for me. I re-imported my projects so I didn't have to re-create them. Everything is as before – james Sep 25 '16 at 22:41
Did not work for me. Had to delete .metadata folder. – Aniket Thakur Nov 15 '17 at 05:51
In my case (Jaspersoft Studio 5.5.1 final) it made all projects disappear from the Project Explorer, except the default one (and I don't know how to open them). – Pere Feb 03 '22 at 08:51

score 5 · Answer 4 · edited Jan 27 '14 at 06:40

5

Deleting .snap file worked perfect for me.

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

edited Jan 27 '14 at 06:40

Aniket Kulkarni

12,825
9
67
90

answered Jan 27 '14 at 06:22

softarchsolutions

129
2
1

score 2 · Answer 5 · answered Jan 14 '16 at 03:01

2

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.

answered Jan 14 '16 at 03:01

Sanjaya Karunarathna

23
3

score 1 · Answer 6 · answered Aug 02 '14 at 19:41

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...

I had to do this too, just deleting .snap didn't fix it. I'm using Luna SR1 (4.4.1). — Martin Charlesworth, Jan 12 '15 at 10:04

score 1 · Answer 7 · answered Aug 19 '14 at 18:24

1

This also works when you receive this error from Information Design Tool (IDT) (Business Objects BI4).

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\

answered Aug 19 '14 at 18:24

Alicia Seffernik

11
1

Deleting (or renaming) the .snap file helped in deed (without losing the whole workspace!!!). Thanks! – Frederic Leitenberger Feb 10 '15 at 10:38
I found the file here: `C:\workspace\.metadata\.plugins\org.eclipse.core.resources\.snap` - which is the same path, except the path shown above is missing some backslashes and the workspace is in a different location ... – Frederic Leitenberger Feb 10 '15 at 10:45

score 1 · Answer 8 · answered Oct 19 '20 at 06:26

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.

answered Oct 19 '20 at 06:26

Javier Sánchez

56
2

Tried this with eclipse neon. Didn't work for me. – RayCh Apr 01 '21 at 08:50

score 0 · Answer 9 · answered Feb 28 '15 at 09:50

0

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

answered Feb 28 '15 at 09:50

Yin

43
6

score 0 · Answer 10 · answered Aug 28 '15 at 16:44

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 · Answer 11 · answered Oct 15 '15 at 17:09

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 · Answer 12 · answered May 16 '16 at 10:15

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.

answered May 16 '16 at 10:15

Bharath

11
3

score 0 · Answer 13 · edited Dec 05 '16 at 09:31

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.

edited Dec 05 '16 at 09:31

unicorn2

844
13
30

answered Dec 05 '16 at 07:09

Rohan P

41
3

score 0 · Answer 14 · answered Mar 04 '20 at 07:19

0

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

answered Mar 04 '20 at 07:19

rachana

1

Eclipse won't start, log error says: ObjectNotFoundException: Tree element

14 Answers14

Linked

Related