I was working on an Android project and after restarting the computer, eclipse won't run.
It's throwing the .metadata.log file error.
Go to ~\.metadata\.plugins\org.eclipse.core.resources
You will find .snap file. Just delete it.
Relaunch Eclipse.
It will work perfectly.
Try using a new workspace. To force the workspace window prompt you need to change the settings in <Eclipse_root_dir>\configuration\.settings\org.eclipse.ui.ide.prefs and set SHOW_WORKSPACE_SELECTION_DIALOG to true.
Source: Eclipse Community Forums
You don't have to delete your .metadata folder because in this way it's going to delete your preferences about your workspace. However delete snap files that exist inside your .metadata folder as well as the .lock files.
Also after you do this don't forget to do a clean start of eclipe
./eclipse -clean
I have also some issues while running Eclipse (with Mercurial and Aptana Plugins).
If you want to find out what is causing this problem backup .metadata folder and "incrementally" delete folders in <your_workspace_folder>/.metadata/plugins/. If you delete some folder and Eclipse will run you'll knew that this is the problem.
For Mercurial I delete workspace\.metadata\.plugins\org.eclipse.core.resources\snap
and for Aptana workspace\.metadata\.plugins\org.eclipse.core.resources\.safetable
If you don't care if your preferences get lost simply delete .metadata folder and run Eclipse again - it'll create new .metadata folder.
You can do a binary search in this folder (each time use a different subset of plugins) to find which folder causes the problems.
For me, deleting the folder "...\workspace.metadata.plugins\org.eclipse.e4.workbench" fixed it.
Just delete ~ WorkSapce \ .metadata.plugins\org.eclipse.e4.workbench folder . Then relaunch the Eclipse. It works for me.
I had the same problem. I deleted /.metadata but I could not solve this problem. If you are installing Eclipse with Java 9, you may not be able to solve this problem by just deleting .metadata or log folders.
Here is what I did. I extracted and install eclipse in /opt/eclipse on Ubuntu 16.04. My java version was 9 and Eclipse version was oxygen 4.7.0.
I added "--add-modules=ALL-SYSTEM" at the last line of my eclipse.ini file. Then, I solved this problem. Since the Eclipse SDK uses that aren't in the java.base modeul, I needed to add this line in eclipse.ini file. See this URL: https://wiki.eclipse.org/Configure_Eclipse_for_Java_9. I hope this help to others. It was easy to fix but it took me for while to find this solution.
This link solved my issue: https://wiki.eclipse.org/Eclipse.ini#-vm_value:_Mac_OS_X_Example. I followed the Mac Example. I located the file eclipse.ini. I then selected "Get info" and change ".ini" to ".txt". This allowed me to edit the text in the file. I then went to finder, went to Macintosh HD -> Library -> Java -> JavaVirtualMachines -> jdk1.8.0_144.jdk -> Contents -> Home -> bin. Then I opened the eclipse.txt file with the general Text Editor. This is the path I then copied into the text file eclipse.txt right under "-vm" like this "/Library/Java/JavaVirtualMachines/jdk1.8.0_144.jdk/Contents/Home/bin". I then hit command save. Then I selected "Get info" on the eclipse.txt file and changed the ".txt" to ".ini" and replied yes I'm sure to use ".ini" when a little pop up box came. Then I exited out of finder and relaunched eclipse with success!
For those who have the .metadata/.log error, just install the java jdk-8u144 and its done.
None of this worked for me, I used java 8.221 and Eclipse Oxygen. So I tried this.
I edited eclipse.ini and before -vmargs put
-vm
C:\Program Files\Java\jdk1.8.0_221\bin\javaw.exe
And it started working
Src: https://www.eclipse.org/forums/index.php/t/1089060/
Navigate to android-sdks (mine is at C:\Users\azeuner\android-sdks\platform-tools) then click on platform-tools, then click on adb.exe this will refresh eclipse. It worked for me !
Related
I have installed Eclipse Neon 4.6.2 and it launches with below error
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.
And the Eclipse screen disappears.
I had the same problem. Later I found the root cause for it in my case.
If you have two java version running in your system (eg jre1.7 and jre1.8), and one of them gets updated (e.g jre 8) and overwrite the other one (which uses the jdk) then this issue might occur.
Better remove one of the java and try to open the eclipse, it might work.
I deleted .metadata (folder) from my eclipse workspace then the problem got resolved.
Note that the .metadata folder will be hidden in workspace. So just go to your eclipse workspace and execute the command:
rm -rf .metadata
Also note you want to export your existing projects from the workspace once eclipse started
Can anyone help me with this error:
java was started but returned exit code = -805306369
C:\Windows\System32\javaw.exe
-jar C:\Program Files\Java\eclipse-jee-helios-SR2-win32-x86_64\eclipse\plugins\org.eclipse.equinox.launcher_1.11.1.R36x_v20101122_1400.jar
Just had this issue, for me it was a corrupted workspace osgi cache. The solution was to run eclipse with the -clean parameter as
eclipse.exe -clean
After some time, eclipse required to clean up, the workspace selection dialog popped up and I could start eclipse normally again.
The -clean parameter is documented in the eclipse help
My problem was a corrupted workspace the solution was from Rob's link:
http://spacetech.dk/eclipse-failed-java-was-started-but-returned-exit-code-805306369.html
I started getting the same error "exit code = -805306369" just out of no where.
Eventually I looked at the Eclipse logs at the <workspace_directory>/.metadata/.log and realized that my Source Control plugin (Perforce in my case) was unable to connect and the eclipse was stuck.
This was because my eclipse was piggy back(depending) on the client connection that I have with my Perforce windows client and my Perforce client was not connected to the server. I connected my Perforce client and the eclipse started working normal.
this happens when mostly workspace is corrupted..... cooler solution is just to switch the workspace to safer location(new location).... and just import the project from previous workspace... princess can still be saved....
For me , Just change your Workspace to another one
I got this error, when workspace already setted up. Since the java virtual machine cannot be created. try command: java -version
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
I restarted my machine, and it solved my problem.
One of the class file in my project was corrupted. The name of a class file was too long and I was not able to delete or rename it, so I rename the folder containing it and then I was able to delete the project and that solved my problem.
Now i know that my workspace was corrupted, it solved my problem.
Go to your workspace and rename it.
Start your eclipse and by default it will create a workspace.
Go to File -> Switch Workspace, choose your original workspace.
I wasn't able to disable "Automatically find new updates and notify me." The option was not there on the Install/Updates page. Perhaps eclipse workbench has changed since that answer was written.
However, running eclipse with the -clean option in my old workspace did the trick for me. The way to do that in windows is to first find the directory where eclipse.exe lives. You can go to the start menu and in the "search menus and files" bar, type eclipse. You should see the purple globe icon pop up under "Programs." Hover your mouse over it and it will tell you the directory it exists in.
Then... open "computer" or some other window from the start menu and from there navigate to the window where eclipse is. Click your mouse in the bar at the top where the directory is displayed (somewhere not on the text). That directory will highlight. Now type cmd. A black command window will open and you will be in the directory where eclipse is. At the command prompt (drum roll) type eclipse.exe -clean
eclipse will start. Make sure it is asking to go to your corrupted workspace and click OK.
Wait for it and soon you will know if your workspace has been uncorrupted. Yay!
“java was started but returned exit code = -805306369” caused by Eclipse´s currupted workspace, I solved my problem with this 4 steps:
1) claose the eclipse.
2) Kill the adb from task manager.
3) Start your eclipse and by default it will create a workspace or start with new workspace.
4) Go to File -> Switch Workspace, choose your original workspace.
In my case, it is a work laptop, so pretty secure SOE
64 bit Win 7.
Unzipped Eclipse MARS onto a folder on "C" drive
Install failed consistently with Java error code -805306369
Created a separate folder on 'C' drive for workspace, granted
everyone full-control and that fixed it!!
I got same issue when opening files using shortcut - Ctrl+Shift+R.
I got it resolved by disabling "Automatic Updates".
Steps to disable automatic update in eclipse (helios): Windows >> Preference >> Install/Update >> Automatic Updates. Disable "Automatically find new updates and notify me".
How I managed to get mine working. I used a combination of the solutions above. It works for me.
Step 1: Change your workspace to some other names e.g. change it from workspace to workspace1.
Step 2: Access your eclipse and stop automatic updates (provided that you could access after changing your workspace)
Step 3: Exit your eclipse with workspace1
Step 4: Start your eclipse with former workspace by entering eclipse.exe -clean (if you are using others then use e.g. MuleStudio.exe -clean)
In conclusion, using a combination of solutions such as changing workspace, stop automatic updates and -clean work for me. Try it yourself.
I've been getting this error message when I want to create a new project in NetBeans. There are two old answers for this question, Project Folder already exists and is not empty- Error in netbeans and Netbeans error: Project Folder already exists and is not empty. Not only they are addressed for NetBeans 7, but also they didn't work.
I tried:
deleting project directory,
deleting userdir under C:\Users..\AppData\Roaming\NetBeans,
deleting cache under C:\Users..\AppData\Local\NetBeans,
uninstalling and installing 8.0.2
updating JDK to 8.40
but none of them worked!
I really appreciate if you'd suggest a solution. Thanks already!
SOLVED: I uninstalled NetBeans from C directory and installed it to the D directory. Then while creating a new project I choose a directory under D. It works fine now!
There is a 99% chance that this is caused by your antivirus application.
You can check on allow file modification for NetBeans in your antivirus application.
I have Bit-defender total security 2018, so if you have it follow me:
Open Bit-defender
On protection tab click on (View features >)
Either you disable (Safe Files) or allow access for NetBeans.
By the way I think Bit-defender is blocking applications to access files on the C drive if I'm not mistaken, so that's probably why it worked for you when you put it on the D drive...
Go to Program Files, delete the NetBeans folder and reinstall it.
Go to C:\Program Files (x86) and delete NetBeans Folder And try to install it again
This might be because of your antivirus. I got the same problem sometime back.
I then switched off the DataLocker option in my antivirus app, after this the problem didn't recur.
I had the same problem when i was messing around with some templates, after undoing the edits and saving the error message stopped occurring.
When netbeans says project folder already exists, it isn't a total error. It still creates the project, it just ran into an error while re-creating one of the template files. If you have the original tab still open, all you have to do is undo to the point before you ruined some template.
Uninstalling and re-installing will fix the problem but i hope this knowledge helps.
I am using Android SDK Tools 23.0.2 with Android API 20 (L preview).
I have been having this error for some time:
parseSdkContent failed
.androidjava.lang.ExceptionInInitializerError
and I have looked at many other similar questions and tried their solutions to no avail.
They recommended deleting the /.android file in the user directory where my workspace is saved and restarting Eclipse. However this did not work for me.
parseSdkContent failed Could not initialize class android.graphics.Typeface
Android SDK Content Loader failing with NullPointerException
This error seems to be affecting my java code's ability to recognize the XML files it references. When I reference variables to components in the XML file, it does not recognize its existence, even though everything seems to be set up correctly.
Please let me know if any more information is needed.
I'd add a comment, but my rep isn't high enough...
Anyway, deleting .android folder worked for me. Your wording suggests you deleted then restarted Eclipse. Try:
Stop/Exit out of Eclipse
Delete .android
Restart Eclipse
I was using the 64 bit version of Eclipse ADT from this link https://dl.google.com/android/adt/adt-bundle-windows-x86_64-20140702.zip
and it was giving me issues on Windows 7 64 bit
I have now downloaded 32 bit version of Eclipse ADT from this link https://dl.google.com/android/adt/adt-bundle-windows-x86-20140702.zip
and now its working perfectly.
It might help others too.
I used the "switch workspace" option and created a completely new workspace. This new workspace gives me no problems.
I'd add a comment, but my rep isn't high enough... (just copied and paste here)
I was in the same problem and using Eclipse Luna + ADT Plugin, what I did was:
Exit Eclipse.
Delete .android folder from my home directory.
Delete .metadata folder from my workspace directory.
Also in my workspace deleted a folder called .remote (I don't remember exactly what was it's name, just deleted it).
Open eclipse, complete the ADT dialog, setup the Android SDK path, and check for eclipse updates.
If updates were done better you restart Eclipse before continuing.
Import my existing projects, (or create a new one).
Open a layout file (xml) to see if the error is gone.
Good luck!
I decided to update my JDK to Java 8, and installed to the default location of C:\Program Files\Java\jdk1.8.0 with a jre subdirectory.
I wasn't sure how Android Studio worked out the JDK location, so I decided to launch it and see. I got the following message:
Failed to complete Gradle execution.
Cause:
Supplied javaHome is not a valid folder. You supplied: C:\Program Files\Java\jdk1.7.0_45
I updated my JAVA_HOME environment variable (both for system and user) to point to the new path, and tried adding it to my PATH variable as well, but every time I attempt to build in Android Studio I get the same message. The quoted path is nowhere to be found in my environment variables though, so where is it getting it from and how can I change it?
Thanks
The problem was my project's JDK location. From the Android Studio Project tool window, I right clicked on the root directory, selected 'module settings', and set the JDK location. Everything's fine now.
I don't know why or how this problem occurred but this answer got me over the hump. On macOS rm -rf ~/.gradle to wipe out the cache then restart Android Studio. I tried everything else up to and including reinstalling the JDK and Android Studio. Wiping out the .gradle directory is the only thing that worked.
Try to delete all .iml files and .idea, and re-import the project from Gradle. Worked for me (provided you have everything else set up).
This error happens when you switch from Intellij to Android Studio, or the other way around, and load the same project. Looks like their project model is not compatible.
For Android Studio 1.1.0, after right-clicking on the project:
Select Open Module Settings
Select SDK Location at top left
Type text into JDK Location: box
I ran into the same issue. My jdk was upgraded from a 1.8.0_172 to 1.8.0_202. And I kept getting the mentioned error although I changed to the right jdk, in the module configurations. What confused me was the fact that the API version was stamped with the old *_172 version in the dropdown of available project sdk's. I found the reason for this to be an old obsolete entry in the dropdown that referenced the old *172. After deleting this entry, the APi versions was magically stamped with the new version.
Note to self: Remember to sanitize your projects when new versions come along
I was also seeing this same problem. For me the fix was in 'Run/Debug Configurations' (Run > Edit Configurations...)
The 'Gradle project' value was set to the build.gradle file location, and this should've been set to the Gradle project object in IDEA, click the folder looking icon not the '...'.
I'm in 1.0.2 and after I clicked OK, it immediately opened a dialog to allow me to specify the location for my project, no longer requiring navigation of the menus to edit the project JDK path.
Definitely strange that during install, it says the JAVA_HOME environment variable is set to a path that doesn't contain the JDK. After spending time fixing it (downloading the full 64 bit JDK), I create my first project and get the same thing. Because it's not using the environment variable that it hinges on during setup.
Odd behavior.
For some reason I failed using all the above answers, so what I did is to delete (actually moved, so that I could go back in case something goes wrong) the ".idea" folder from the project. Then I opened the IDE again, and it went fine.
Getting this in 2021? Try to to rm -rf ~/.gradle and restart Android studio.