[java] An error has occured. Please see log file - eclipse juno

Whenever I start up Eclipse Juno, it gives me an error saying:

An error had occured. Please see the log file:

C:\Program Files\eclipse\configuration\1362989254411.log.

Some websites say to uninstall jdk and install it back again. I did that, but it didn't work. I think it was because on their website, the error is happening IN the workspace. Mine is on the program files folder, which is in the computer.

It happened after updating it. Should I downgrade. If so, how? If I can't downgrade, what should I do?

Here's what I did to solve this:

• I removed workspace/.metadata
• run eclipse as an administrator.

I was getting the same error while opening the eclipse. to solve that I checked the log file inside the metadata folder. where I found that there is version mismatch of Java. so I have changed the VM inside my eclipse ini file.

-vm /opt/jdk1.8.0_191/jre/bin

Hope this will also help to solve your problem.

Sounds simple but just delete/uninstall eclipse and install it again.

My OS architecture is 64-bit so downloaded Eclipse Oxygen 64-bit version and got this error. Tried various solutions posted here but didn't help. Then downloaded Eclipse Oxygen 32-bit version and it works well.

i found the solution. i have installed 2 versions of jre sdk 1.3 and jre7 so i uninstall the older version sdk1.3 then it works.

For me it was down to a locking/permissions bug on

(path to Eclipse IDE)\configuration\org.eclipse.osgi.manager.fileTableLock

See here

Spring Tool Suite 4 (64 bit for Windows Server 2016)

Version: 4.2.2.RELEASE Build Id: 201905232009

based on Eclipse

Version: 2.2.500.v20190307-0500 Build id: I20190307-0500

wouldn't launch and a pop up dialog appeared saying:

launch error has occurred see log file null

(This became apparent from the latest text log file in the folder (path to Eclipse IDE)\configuration)

!ENTRY org.eclipse.osgi 4 0 
2019-06-19 18:41:10.408
!MESSAGE Error reading configuration: C:\opt\sts-4.2.2.RELEASE\configuration\org.eclipse.osgi\.manager\.fileTableLock (Access is denied)
!STACK 0
java.io.FileNotFoundException: C:\opt\sts-4.2.2.RELEASE\configuration\org.eclipse.osgi\.manager\.fileTableLock (Access is denied)
...

I had to go and tweak the permissions via File Explorer (Full access).

It appeared as if the IDE was doing nothing for a while.

The splash screen for Spring Tool Suite (based on Eclipse) eventually disappeared and the IDE started up again.

Now everything is back working correctly again.

For me the problem was that I installed Java sdk 1.9 before installing eclipse. deleting it and installing Java sdk 1.8 instead fixed it. Also, if you are using mac, try

export JAVA_HOME=$(/usr/libexec/java_home)

and then

echo $JAVA_HOME

your should get something like

/Library/Java/JavaVirtualMachines/jdk1.8.0_144.jdk/Contents/Home

C:\path\to\eclipse\eclipse -clean

Then change the working project directory to something different. It should work after that.

In my case I didn't want to remove eclipse because in corporate world we can't control everything. Also deleting some files from workspace .matadata could not help. So below hack that I found with trial and error worked for me perfectly :

Go to this path: C:\....\eclipse-Luna\configuration\org.eclipse.core.runtime\

now delete .manager completely.

Start eclipse again and woilaa.. it will run normally.

[In my case, I use eclipse luna. I once abruptly closed the PC when eclipse was open. Then eclipse was not able to start on the next system restart. So keep in mind to close eclipse properly. :) ]

In my mac machine, I checked whether I installed two java versions or not. I got this error. Because i installed two java at a time.

User -> Library -> Java -> JavaVirtualMachines -> version 1.8.0 and version 11.0.1 has been installed.

I removed version 11.0.1. Now its working fine.

The issue is due to the availability of more than one eclipse versions. I tried removing both installations and started with a clean install and it worked. Also, make sure after the install point to a new workspace.

If nothing works, then try uninstalling and then reinstalling Eclipse. This is how i just fixed this problem after trying everything suggested on this forum.

Delete the .metadata folder from workspace and start the eclipse and now again import all project in same workspace, this worked for me.

In my case my JAVA_HOME was pointed to jdk9 after pointing JAVA_HOME to jdk8 resolved my issue. Hope it helps someone.

In my case, error was due to Java 14 , which is not an LTS, downgraded it to java 8 and it worked.

I have got the same error after removing eclipse and installing it again.

Deleting the .metadata directory and running eclipse -clean does not work for me, but the following works for me:

sudo cp /usr/lib/jni/libswt-*3740.so ~/.swt/lib/linux/x86_64/

if you have a 32 bits based system do:

sudo cp /usr/lib/jni/libswt-*3740.so ~/.swt/lib/linux/x86/

For STS on MacOS, i followed the following steps:

1. Go to the STS directory from terminal:

   cd /Users/karan.verma/Documents/sts-bundle/STS.app/Contents/MacOS

2. Start STS

   ./STS

STS started, but all my imported projects were removed.

This instruction works 100% for me:

1. Rename the Eclipse workspace name
2. Start Eclipse (it will start successfully with empty workspace)
3. Exit it and change workspace name to previous state(if ask to replace some files, press no)
4. Start Eclipse again and Re import projects in current workspace

Enjoy!

Try deleting following file from workspace.

YOUR_WORKSPACE/.metadata/.plugins/org.eclipse.core.resources/.snap

Or try launching it from console.

C:\path\to\eclipse\eclipse -clean

Deleting metadata folder might not work in this case. Or eclipse -clean command. Or reinstall eclipse might not solve this.

Instead try deleting other java versions you might have in your machine.

Check what you have right now using this:

/usr/libexec/java_home -V

Delete other java versions which you don't want, following below command:

sudo rm -rf /System/Library/Java/JavaVirtualMachines/java-version.jdk

This should resolve your issue.

It worked for me when I went to WorkSpace\.metadata\.plugins\org.eclipse.e4.workbench and then remove the *.xmi files.

I deleted the entire .metadata folder, and it worked for me.

The reason may be that you are trying to use old version of Eclipse for new version of Java. I've downloaded the latest Eclipse (which is Oxygen) and it worked for me.

Solved :

1. Quit eclipse
2. GO to your workspace and delete .metadata folder
3. Now open eclipse with same Workspace path ( You will see as a new workspace )
4. Now right click import > General > Existing Projects into Workspace > next > Select root directory -> browse to your current workspace and press OK.
5. Now you will all see your all projects and then hit OK again.
6. Voila, same projects with same workspace no migration or reference problem.

After trying everything else, this solves my issue.

I got the same error when I was using Texas Instrument's Code Composer Studio which is built on eclipse. It happened when I changed my Workspace folder to be inside the Google Drive folder. Deleting files from YOUR_WORKSPACE/.metadata/.plugins/org.eclipse.core.resources/ did not work for me.

The following worked for me:

1. Take backup of original Workspace folder
2. Delete the original Workspace (from the Google Drive folder)
3. Start Eclipse (works fine now)
4. Restore the Workspace backup to a non Google Drive folder

However deleting and restoring the Workspace folder is not advisable since it can have other complications. But I was desperate.

None of the current answers worked for me. On CentOS, I had to delete the .eclipse folder from home directory. Then eclipse launched just fine!

I had 2 version of JDK installed - JDK 7 and JDK 8. Initially it worked even when both the versions were there and was able to use Git and Gradle and up the Spring Boot Application.

Then after system restart/sleep, workspace prompt did not come up.

Uninstalled JDK 7 and it prompts for workspace,now.

The best way is to delete all the *.snap files from /.metadata/.plugins/