Related
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.
I have a couple of Java projects in Eclipse. I can build the project and also run the application from Eclipse. However, when I right click on a method of a class and select "Open Call Hierarchy", I get the "The resource is not on a build path of a Java project." error message. I have all of the src files in the Source tab of the Java Build Path properties window.
Try this,
Calling eclise with eclipse.exe -clean -refresh forces Eclipse to rebuild the index. After that the feature worked again.
Closing and re-opening the project.
If your eclipse version is 2019-03,then this was a bug(https://bugs.eclipse.org/bugs/show_bug.cgi?id=545293). Try to upgrade your eclipse or install a newer version. For me installing a newer version(latest version Eclipse 2019-09) solved the problem.
im just trying to run a test project, but i cant understand why it return this errors, its the same computer configuration
Firewall OFF
Eclipse Kepler SR1 32bits (the same in the other computer)
JRE7 32bits
JDK7 32bits
Maven 3.2.1
JBoss from Eclipse Market
i just imported the zip but look the errors:
http://i.stack.imgur.com/lphI3.png
where it ask for the vraptor-jpa, the version in this pom is the same that is working in this project in other machine, why it has a lot of errors for the SAME THING?
solved some problems by removing the reference to a old .jar and deleting the .m2 folder, not i ended with this:
http://i.stack.imgur.com/gRFll.png
looks like your .classpath has some invalid reference to jar (which doesn't exist), open your <PROJECT_ROOT>/.classpath file and correct invalid references or you can do it with eclipse interface, right click > properties > java build path > fix those invalid entries
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?
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
Solved :
Quit eclipse
GO to your workspace and delete .metadata folder
Now open eclipse with same Workspace path ( You will see as a new workspace )
Now right click import > General > Existing Projects into Workspace > next > Select root directory -> browse to your current workspace and press OK.
Now you will all see your all projects and then hit OK again.
Voila, same projects with same workspace no migration or reference problem.
After trying everything else, this solves my issue.
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 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.
I deleted the entire .metadata folder, and it worked for me.
The best way is to delete all the *.snap files from /.metadata/.plugins/
Here's what I did to solve this:
I removed workspace/.metadata
run eclipse as an administrator.
In my case my JAVA_HOME was pointed to jdk9 after pointing JAVA_HOME to jdk8 resolved my issue.
Hope it helps someone.
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.
C:\path\to\eclipse\eclipse -clean
Then change the working project directory to something different. It should work after that.
This instruction works 100% for me:
Rename the Eclipse workspace name
Start Eclipse (it will start successfully with empty workspace)
Exit it and change workspace name to previous state(if ask to replace some files, press no)
Start Eclipse again and Re import projects in current workspace
Enjoy!
Sounds simple but just delete/uninstall eclipse and install it again.
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.
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.
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 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:
Take backup of original Workspace folder
Delete the original Workspace (from the Google Drive folder)
Start Eclipse (works fine now)
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.
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.
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/
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. :) ]
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.
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
For STS on MacOS, i followed the following steps:
Go to the STS directory from terminal:
cd /Users/karan.verma/Documents/sts-bundle/STS.app/Contents/MacOS
Start STS
./STS
STS started, but all my imported projects were removed.
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.
It worked for me when I went to WorkSpace\.metadata\.plugins\org.eclipse.e4.workbench and then remove the *.xmi files.
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.
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.
In my case, error was due to Java 14 , which is not an LTS, downgraded it to java 8 and it worked.
It happened to me after I rename the file folder. I Try to delete my workspace or .metadata or .manager folder, and not work.
Then I download the program again and I choose the complete download. It is 337.511 KB and in zip File. But I place it in Flashdisk. I open the zipfile then I run eclipse.exe. It work. Then I import all my work file. It work back again show in Project Explorer.
I close eclipse. Then I click eclipse icon in desktop ( I didn't delete the program). Now It work fine.
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.
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.