We Keep Coding

Eclipse failing to open

My Eclipse IDE keeps failing to open. I've updated my java to the latest version, I've got the newest Eclipse Version. I'm running x64 Windows, it seems like the Error log is trying to use x32, but I've installed a x64 version of Eclipse. I tried re-installing the x64 version and it still didn't work.
In the Pastebin I've linked is the contents of the Log.
http://pastebin.com/An5CRq3e
EDIT: I'm using x64-bit version of Java

The same happened to me: without renaming my workspace I just deleted the corrupted org.eclipse.core.resources folder in the workspace ($ECLIPSE_WORKSPACE/.metadata/.plugins/) and then Eclipse started successfully again.
Yes, I had to re-import all my projects (as Existing Projects) into the workspace.
Refs: Eclipse forum

Thank you for copying/pasting the log - definitely helpful!
This line looks significant:
Caused by: org.eclipse.core.internal.resources.ResourceException: Incompatible file format. Workspace was saved with an incompatible
SUGGESTIONS:
From a command prompt:
cd into your Eclipse directory
type eclipse -clean -clearPersistedState
Rename (or delete) any old workspaces to force Eclipse to create a new workspace

Yes I have also removed org.eclipse.core.resources folder from my Eclipse workspace :
workspace\.metadata\.plugins\org.eclipse.core.resources
And also run the command in command prompt:
>eclipse.exe -clean -clearPersistedState
After doing this Eclipse should work without any problem.
OR
Open a new workspace.

Here is what worked for me :
Rename your workspace
Open eclipse / talend or any software based on eclipse that give you the error
-- it will recreate a new workspace automacilly
Copy your projects' folders from your old workspace to new workspace
in eclipse(or your software based on eclipse) just reimport your projects from folder
done

Error message displayed when opening Eclipse: "An error has occurred. See the log file null"

I use Windows 10 and jre1.8.0_51. I don't know why when I start Eclipse it always displays an alert message "An error has occurred. See the log file null."
And I cannot open Eclipse thereafter. I tried to search Google and have no best solution. I uninstalled JRE and installed it again, but it still produces the same problem.

Try to launch it from the console like:
C:\path\to\eclipse\eclipse -clean
Also you try to can delete the file to fix the problem permanently as suggested here. Command would be something like below for windows.
del YOUR_WORKSPACE/.metadata/.plugins/org.eclipse.core.resources/.snap

I ran into the same problem. When I try running eclipse as Administrator, the problem went away.

Had same issue.
To resolve it : Go to Eclipse directory -> Open CMD -> eclipse -clean
worked well.

I had the same issue with Windows 10. Give full control to your user in security settings on the eclipse and workspace folders.
I also found the read only property was set on the eclipse and workspace folders, which I unset.
The log file can be found in the eclipse\configuration folder.

I deleted .metadata from the workspace and ran the eclipse as run as administrator and it worked for me.

I found that running Eclipse (STS 3.9) as administrator worked, which is a permissions issue. Giving the required users read/write/execute permissions to the config and workspace folders did the trick (they couldn't write previously).

I too came across the same error.
My log file says :
Java.io.FileNotFoundException: C:\Eclipse\eclipse-jee-luna-SR2-win32-x86_64\eclipse\configuration\org.eclipse.osgi.manager.fileTableLock (Access is denied)
So, i copied entire eclipse in another folder and it worked for me.
So, for me the problem was write access, because eclipse need write across configuration folder, in my case eclipse was unzipped by some other user and i didn't have the access.

I encountered the same problem, and then I found out that, the eclipse distribution works fine with JDK 8. I previously ran JDK 10 and I got this error. Uninstalling JDK 10 and installing JDK 8 fixed the issue for me.
Hope this helps!!

Make sure your eclipse launch folder does not have read only property/attribute
My eclipse resides at below location and If I right click ->properties- checked attributes were read only. I unchecked read only and restarted eclipse. Issue was resolved.
C:\Users\Ashish\Downloads\eclipse-jee-mars-2-win32-x86_64 (1)\eclipse

Here I'm just share, if you can not copy file .metadata on mac because that file invisible (JUST on Mac issue), try this step:
compress your file .metadata backup
copy file .zip
paste file .zip to path/workspace
double click file .zip
done :-)

Open the eclipse.exe with the right mouse button and open with admin rights and that's it!

I had the same problem and deleting the file .metadata/.plugins/org.eclipse.core.resources/.snap and try it should work

Uninstall Java JDK
Reinstall JDK 8
Run Eclipse as administrator

Remove the .snap file from <WORKSPACE-DIRECTORY>\.metadata\.plugins\org.eclipse.core.resources

The mentioned solutions didn't work for me under Windows OS.
I just deleted .manager from eclipse\configuration\org.eclipse.core.runtime and from eclipse\configuration\org.eclipse.osgi and the issue was fixed.

Delete the .metadata folder in eclipse. That should resolve the issue. The .metadata folder is recreated by eclipse once it is able to launch successfully.

I too got the same error in My Windows 10 pc while using Eclipse 2020 version
Just delete the .metadata folder and then try to run eclipse again it will solve the problem and run fine. .Metadata folder will get created once again by itself as we open eclipse.

I uninstalled JRE and installed it again, but it still produces the same problem.
Turns out that my version of eclipse doesn't work with jdk17 (installed it using Amazon Corretto 17). So uninstalled Amazon Corretto 17 (automatically uninstalls jdk17 as well) and installed jdk11 using Amazon Corretto 11.
Thankfully worked for me! What I tried was similar to what you tried, but worth trying anyway.

Re-install Eclipse or add vm path in your eclipse.ini file.
-vm
C:/<Your Path>/jdk1.8.0/jre/bin/javaw.exe
Note: Change javaw.exe path according to your system

Make sure your java version is compatible with your eclipse version!
An easy solution that worked for me. Deleting the .metadata did not result. I was using eclipse MARS 2.0 but set my JAVA_HOME to java 17. However, Mars does not support java 17. As soon as I swapped it back to java 14 eclipse launched again.

Eclipse doesn't start in Ubuntu 14.04

I have a problem trying to launch Eclipse in Ubuntu 14.04. Splash picture pops up, then blinks, turns white - and nothing happens until kingdom come.
I have tried Luna, Kepler and 3.8 (from Ubuntu repository). EE and SE editions - both the same. I have also tried to launch them with different (oracle) vm - 1.7 and 1.8.
And yes, I have tried the -clean and simple workspace removal.
This is the only thing it says in console:
org.eclipse.m2e.logback.configuration: The
org.eclipse.m2e.logback.configuration bundle was activated before the
state location was initialized. Will retry after the state location
is initialized.
Java VM works fine - I can launch (for example) IDEA or java\javac commands.
Any suggestions?

The answer is already here, but it's in the comments. So I re-post it as answer:
check your 2nd screen. Workspace dialogue may be there.

Try this:
1) Remove .snap from:
.metadata\.plugins\org.eclipse.core.resources\.projects\<project>\.markers.snap
If you can't find it manually try this:
find /.metadata/.plugins/org.eclipse.core.resources/.projects -name "*.snap" -exec rm -f {} \;

It Generally happen when eclipse is closed unexpectedly.
Heres things you can do.!
1)Save and Delete .metadata from workspace folder.
2) Try Re-installing Eclipse.
This solution worked for me. :)

If you don't have any pending changes and have pushed your project already on your repo, you can also try deleting the project folder where eclipse opens a project path automatically.
When you run eclipse again, it will work again.
Unfortunately, deleting metadata didnt work for me. Also I don't have any extra monitor so deleting my project folder was my last resort.

java.lang.Object cannot be resolved in Eclipse

When I installed the latest installment in Mac OSX - the Mountain Lion - I experienced some problems getting Eclipse to work I also lost most of my Android developer files (but I still have my projects). I suspect this is due to the choice of removing the /Developer and move the XCode and other Apple developer tools (I placed my Android tools here).
I have now installed the latest version of Eclipse and the problem still seems to be around. There are errors in all my projects and I get an error message prompting:
The type java.lang.Object cannot be resolved. It is indirectly referenced
from required .class files
I tried to check the Java class-path both in Eclipse and in my terminal and these seems to be OK. java and javac both run in my terminal and there is a valid path to the java source files in Eclipse (Under Preferences, Java, Installed JREs). That being said I'm not an expert in Eclipse so there may be that I have misunderstood how this problem ought to be solved. Anyone here with similar problems or who know the cure?

Make sure that you have a valid JRE or JDK defined in the Java Build Path of your project. Right-click on your project, select Properties... and then Java Build Path.

I had this problem moving a Maven project from Eclipse to RAD. I had a JSP file that worked in Tomcat and JBoss, but threw a NullPointerException in WebSphere on the form definition during the compile.
Anyway, after transforming the Maven project into an Ant project (mvn ant:ant), I imported the Ant project into RAD and got this error. The fix:
Open the Java Build Path, selecting the Libraries tab.
Find the JRE System Library and remove it.
Add the JRE System Library.
Goofy, but it works. It must reset some property in a file. I don't know if the problem is the older version of Eclipse or RAD.

After updating my Android SDK to make Appcelerator Titanium happy, I started getting "java.lang.Object cannot be resolved" for my Android projects in (non-Titanium) Eclipse.
I updated all dependencies in Eclipse, and the error healed after a restart of Eclipse.

I had that error almost every time I launched Eclipse for the first time; if I close and then re-open Eclipse, the error is gone.
I found this solution useful, though (I've copied here to protect the link, credit goes to the original author):
In Eclipse go to Windows -> Preferences -> Java -> Installed JREs.
Select the currently active JRE/JDK and press the Edit button.
Select the rt.jar and change its position in the list of JRE system libraries (e.g. press the Up button once).
Confirm all changes, clean and rebuild the workspace.
The next time you face the problem reposition the rt.jar again (or reset the order by pressing the Restore Default button).

please select your installed system jre version from java build path.

Try the following and problem will go away
Close the project and reopen it.
Clean the project (It will rebuild the buildpath hence reconfiguring with the JDK libraries)
OR
Delete and Re-import the project and if necessary do the above steps again.

This is an annoying Eclipse Bug which seems to bite now and then. See http://dev-answers.blogspot.de/2009/06/eclipse-build-errors-javalangobject.html for a possible solution, otherwise try the following;
Close the project and reopen it.
Clean the project (It will rebuild the buildpath hence reconfiguring with the JDK libraries)
OR
Delete and Re-import the project and if necessary do the above steps again.
The better cure is to try NetBeans instead of Eclipse

I got this error and what I had to do was remove the JRE from the Window/Preferences/Java/Installed JREs and re-add it. This somehow cleared up eclipse's cache and rebuilt the project successfully. To get rid of the error in the file-editor I also had to close it and open the file once again.

My problem was that I had in Eclipse: Window / Preferences... and then in the tree on the left Java / Installed JREs: C:\Program Files\Java\jre7
I changed to: c:\Program Files (x86)\Java\jre7
It solved my problem.

I had the same issue and none of the above solutions worked for me.
Then I realized than the library (libs) folder was missing in the project. Once i added the libs folder and the corresponding Jar file, the issue was resolved..

If your project specific (or if not applicable, workspace default) JDK/JRE is being referenced correctly and you've just begun to get this issue out of the blue: restart Eclipse.
Unfortunately, "restart Eclipse" is one of the standard troubleshooting steps when a project won't build. Eclipse even has a dedicated entry under the File menu.

I had to add the JDK under the build path. After adding the correct build path it worked.

I just had to restart eclipse, and the error went away. Strange.

I solved this by pointing my eclipse to the jre available in jdk.

This error caused by invalid sdk is pointing in your project.properties file of your project.
project.properties -> target=android-19 . change to version which is installed in your eclipse.The error will be gone.

I had the same issue after moving from JRE7 to JDK7. Finally I had to remove the JRE7 configuration from the Eclipse preferences and then add the following two lines to the eclipse.ini file.
-vm
C:\Program Files\Java\jdk1.7.0_55\bin\javaw.exe

I had this problem, and I understood that Eclipse has automatically imported a core reference, instead of the reference for the project I needed.
Deleted the import, and rearranged it, and everything worked fine.

Same problem facing Me
Project->properties->Android
And select the api level and also go in java build path and check some external jar file path if we already add in it.update the jar file path

On "The type java.lang.Object cannot be resolved. It is indirectly referenced
from required .class files":
I found my project had 2 meta-inf.java files in 2 different directories with the same 'module ' on line one (a copy/paste error).
Once this was corrected, I cleared the meta-inf.java file with the issue, rebuilding it line by line, guided by Eclipse, until I had a working module configuration.

How do I prevent Eclipse from hanging on startup?

I am using Eclipse 3.3 ("Europa"). Periodically, Eclipse takes an inordinately long time (perhaps forever) to start up. The only thing I can see in the Eclipse log is:
!ENTRY org.eclipse.core.resources 2 10035 2008-10-16 09:47:34.801
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.
Googling reveals someone's suggestion that I remove the folder:
workspace\.metadata\.plugins\org.eclipse.core.resources\.root\.indexes
This does not appear to have helped.
Short of starting with a new workspace (something which I am not keen to do, as it takes me hours to set up all my projects again properly), is there a way to make Eclipse start up properly?

This may not be an exact solution for your issue, but in my case, I tracked the files that Eclipse was polling against with SysInternals Procmon, and found that Eclipse was constantly polling a fairly large snapshot file for one of my projects. Removed that, and everything started up fine (albeit with the workspace in the state it was at the previous launch).
The file removed was:
<workspace>\.metadata\.plugins\org.eclipse.core.resources\.projects\<project>\.markers.snap

try:
cd to <workspace>\.metadata\.plugins\org.eclipse.core.resources
remove the file *.snap (or .markers in Indigo)

In my case (Juno) I had to do this:
find $WORKSPACE_DIR/.metadata/.plugins/org.eclipse.core.resources/.projects \
-name .indexes -exec rm -fr {} \;
That did the trick.
Initially I thought it was a problem with Mylyn (I experienced these freezes after I started using its generic web connector), but the problem appeared even after uninstalling the connector, and even deleting the .mylyn directories.
Edit: I also managed to restart eclipse by deleting just one file:
rm $WORKSPACE_DIR/.metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi
That worked fine, without any indexes involved. Only the workbech, which I personally don't mind that much.

You can try to start Eclipse first with the -clean option.
On Windows you can add the -clean option to your shortcut for eclipse. On Linux you can simply add it when starting Eclipse from the command line.

This one works for me:
Another, and a bit better workaround which apparently works:
Close Eclipse.
Temporary move offending project somewhere out of the workspace.
Start Eclipse, wait for workspace to load (it should).
Close Eclipse again.
Move the project back to workspace.
Source: Eclipse hangs while opening workspace after upgrading to GWT 2.0/Google app engine 1.2.8

I used eclipse -clean -clearPersistedState and that worked for me.
Warning: This may remove all projects from the workspace.

I had a similar problem with a rather large workspace in 3.5 and no .snap-files anywhere to be seen. "Windows -> Preferences -> General -> Startup and Shutdown -> Refresh workspace on startup" seems to be a workspace-related setting and so I couldn't change it for the workspace that was causing the hang.
Running eclipse with the command line parameter -refresh and then changing the setting seems to do the trick.

I also had luck with removing the *.snap files. Mine were located in a different directory than mentioned in the posts (below).
<eclipse workspace>/.metadata/.plugins/org.eclipse.core.resources/.projects
Consequently, the following unix cmd did the trick:
find <eclipse_workspace>/.metadata/.plugins/org.eclipse.core.resources/.projects -name "*.snap" -exec rm -f {} \;

I tried all of the answers in this thread, and none of them worked for me -- not the snap files, not moving the projects, none of them.
What did work, oddly, was moving all projects and the .metadata folder somewhere else, starting Eclipse, closing it, and then moving them all back.

Since I don't have a .snao or .prefs file in .metadata.plugins\org.eclipse.core.resources folder (running on OS X), what did the trick for me was copy the .project folder to old.project, start Eclipse, and check
Windows -> Preferences -> General ->
Startup and Shutdown -> Refresh
workspace on startup
as proposed by matt b. After that, I closed Eclipse, renamed the folder old.projects back to .projects and after that everything worked fine again.

I did this:
cd to .metadata.plugins\org.eclipse.core.resources
remove the file .snap
Noticed the Progress tab was doing something every few seconds..it seemed stuck
Exit eclipse (DO NOT FILE|RESTART HERE OR YOU HAVE TO GO BACK TO STEP 1 AGAIN)
Open eclipse again.
Using -refresh or -clean when starting eclipse did not help.

On Mac OS X, you start Eclipse by double clicking the Eclipse application. If you need to pass arguments to Eclipse, you'll have to edit the eclipse.ini file inside the Eclipse application bundle: select the Eclipse application bundle icon while holding down the Control Key. This will present you with a popup menu. Select "Show Package Contents" in the popup menu. Locate eclipse.ini file in the Contents/MacOS sub-folder and open it with your favorite text editor to edit the command line options.
add: "-clean" and "-refresh" to the beginning of the file, for example:
-clean
-refresh
-startup
../../../plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
--launcher.library

Check that the Workspace Launcher hasn't opened on your TV or some other second monitor. It happened to me. The symptoms look the same as the problem described.

Windows -> Preferences -> General -> Startup and Shutdown
Is Refresh workspace on startup checked?

I just had problems with Eclipse starting up. It was fixed by deleting this file:
rm org.eclipse.core.resources.prefs
I found in .settings

UFT causing issues with RDz (Eclipse based) after install
These suggestions will allow to work around this situation even with the environment variables in place and with corresponding values.
Note: Conflicting application will not be recognized in a java context because it is being excluded from the java support mechanism.
Impact: Excludes Add-ins support from hooking to conflicting application executable via Windows Registry Editor
Requirement: The application must be started by an EXE file, except Java.exe/Javaw.exe/jpnlauncher.exe
Instructions:
a. Locate the executable filename of the application conflicting with add-in(s) support. Either use the Task Manager or the Microsoft Process Explorer.
b. Open Windows Registry Editor.
c. Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Mercury Interactive\JavaAgent\Modules
For 32bits applications on Windows x64: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Mercury Interactive\JavaAgent\Modules
d. Create a DWORD value with the name of the conflicting software executable filenmae and set the value to 0.

Removing *.snap (mine is *.markers), --clean-data or move workspace folder seems all did not work for me.
As my eclipse stopped working after I installed and switched my keyborad input to HIME, I went back to fctix and it worked.

I had no snap files. Going through the help menu installation list, at least 90% of my plugins had the uninstall button deactivated so I could not handle it through there. Under startup/shutdown most of plugins were not listed. Instead, I had to manually remove items from my plugins folder. Wow, the startup time is much faster for me now. So if everything else does not work and you have plugins that are disposable, this could be the ultimate solution to use.

Unfortunately, none of these solutions worked for me. I ended up having to create a new workspace, then imported the existing projects into the new workspace. Unfortunately, you lose your preferences when doing so (so, remember to export your settings anytime you change them!)

I had a very similar problem with eclipse (Juno) on Fedora 18. In the middle of debugging an Android session, eclipse ended the debug session. I attempted to restart eclipse but it kept haning at the splash screen. I tried the various suggestions above with no success. Finally, I checked the adb service (android debug bridge):
# adb devices
List of devices attached
XXXXXX offline
I know the android device was still connected but it reported it offline. I disconnected the device and shut down the adb service:
# adb kill-server
Then I waited a few seconds and re-started the adb service:
# adb start-server
And plugged my android back in. After that, eclipse started up just fine.

no need to delete entire metadata file. just try deleting the .snap file from org.eclipse.core.resources on your workspace folder
ex. E:\workspaceFolder\.metadata\.plugins\org.eclipse.core.resources

Watch out for zero-byte .plugin files in the {WORKSPACE-DIR}/.metadata/.plugins folder. I just deleted one in there and it fixed my freezing issues.

In my case similar symptoms were caused by some rogue git repository with a ton of junk system files.
Universal remedy, as mentioned above, is to use Process Monitor to discover offending files. It's useful to set the following 2-line filter:
Process Name is eclipse.exe
Process Name is javaw.exe

I had a similar problem after I updated eclipse on Mavericks. Eventually I found that in the eclipse plugins directory the com.google.gdt.eclipse.login jar had version numbers at the end. I removed the version number from the name and it all started fine :)

Also look at http://www.lazylab.org/197/eclipse/eclipse-hanging-on-startup-repair-corrupt-workspace/
99% Recommended Solution works.... (i.e. Removing .snap file) But if it did not worked then we have to try to remove indexes folder and further workbench folder.

This may help
In your eclipse,
1) Go to Help
2) Click Eclipse marketplace
3) search - optimizer
install "optimizer for eclipse"

In Ubuntu eclipse -clean -refresh worked for me for Eclipse 3.8.1

It can also be caused by this bug, if you're having Eclipse 4.5/4.6, an Eclipse Xtext plugin version older than v2.9.0, and a particular workspace configuration.
The workaround would be to create a new workspace and import the existing projects.

Well, I had similar behaviour while starting eclipse over X11. I forgot to tick the enable X11 forwarding in my putty.

In my case deleting the .metadata folder of the workspace worked. I am using Eclipse Luna service Release 2.