I just append
-vm
C:\Program Files\Java\jre6\bin\javaw.exe
in eclipse.ini then I try to start eclipse again and got this error. Give me how to solve or link that actually solve it.
this is my eclipse.ini
-startup
plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.1.R36x_v20100810
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize 256m
--launcher.defaultAction
openFile
-vm
C:\Program Files\Java\jre6\bin\javaw.exe
-vmargs
-Xms40m
-Xmx384m
Thank you
I had the same error when configuring eclipse.ini to use JRE6. Turns out I caused this error by incorrectly configuring eclipse to use the 64 bit JVM while running a 32 bit version of eclipse 3.7.
The correct configuration required the eclipse.ini -vm argumument to use "C:/Program Files (x86)/" instead of "C:/Program Files/".
Make sure that the JVM version (32/64 bit) you use matches the eclipse version (32/64 bit).
It may just be the way the error shows (and not how it is written in the eclipse.ini file), but there is text in Eclipse.ini (Specifying the JVM) that says the following:
The -vm option and its value (the path) must be on separate lines.
The value must be the full absolute path to the Java executable, not just to the Java home directory.
The -vm option must occur before the -vmargs option, since everything after -vmargs is passed directly to the JVM
Look at the second line of the message box. There you can see which java runtime in fact is started. Mine was suddenly C:\ProgramData\Oracle\Java\javapath\javaw.exe. This happened after I have installed a "chrome java updater" (Chrome browser moaned: 'your java is outdated, you have to update...').
Before this "chrome java update" my eclipse (luna jee x64) started without error. Looking closer to the background I detected following: the chrome java updater (notabene started from an Oracle site) added C:\ProgramData\Oracle\Java\javapath in front of the env var PATH. It contains three symbolic links to the newest java 8 JRE installation in (x86) program folder -> hence to a 32 bit java JRE. Oracle replaces with Java8 the old technique having the symlinks in system32 (64bit) resp. SysWOW64 (32bit).
Meanwhile I learned. Whatever java installer you have executed last (the *.exe) leads windows to remember that java flavour (32b or 64b), with the result that after an update the links in C:\ProgramData\Oracle\Java\javapath point to a java installation of the remembered flavour. If you have a 64b eclipse installation and encounter the described error: just re-install the newest 64b JDK. After that the java updates do no more link to a 32b version. And eclipse 64b will start correctly without the entry in eclipse.ini .
You need to check if your PC has a 64-bit or 32-bit operating system, then same goes for your JDK (64-bit/32-bit) and also for Eclipse (64-bit/32-bit).
Make sure they are all the same; if not, you need to download the one that matches your bitness.
For Eclipse:
Added this two lines in eclipse.ini
Second line represents the JDK location of the javaw.exe file.
-vm
C:\Program Files\Java\jdk1.7.0_60\bin\javaw.exe
Note: place -vm lines before -vmargs, otherwise default location is taken.
For STS
Change the same as above in STS.ini
I just hit this too. Turns out that at least for me, this was due to trying to use a win64 version of the JRE with a win32 Eclipse. I seems that win32 Eclipse requires a win32 Java (what is called -586 in the list of Java installers from Oracle/Sun).
The reason I was using both is that I was trying to pinpoint a bug that only manifested itself in 64-bit Eclipse, so I needed a 32-bit to compare to.
Once I installed BOTH the "x64" (win64) and "i586" (win32) versions of the JRE on my machine, things work fine and no error 13. You can apparently have both installed at the same time.
The error means it's the wrong JVM version for that version of Eclipse. The link has more details:
http://www.ehow.com/how_4784069_terminated-exit-code-error-eclipse.html
Make sure the Eclipse and the Java that you are using are both either 32-bit or 64-bit.
You cannot run 64-bit eclipse with 32-bit JRE.
java -version
Java HotSpot(TM) 64-Bit Server VM
The 32 bit version JRE will not have 64-Bit in it.
I just had the same issue, and spend about an hour trying to solve the problem.
In the end it was a '#' character in the path.
So I renamed "C:\# IDE\eclipse 3.7\" to "C:\+ IDE\eclipse 3.7\" and that solved the problem.
Recently I faced same issue.My version of eclipse didnt support java version 8.
I had accidently installed jre 8 on my machine which automatically updated my PATH variable by appending "C:\ProgramData\Oracle\Java\javapath" in the beginging which led eclipse to pick up this version(and ignore the manually added 1.6 version which came later in order)and crash with exit code 13.
I just removed this string from the path so which led system to pick up my older version and eclipse started just fine.
I had the same issue with eclipse in my both machine. I had jre 32 bit installed. So I removed 32 bit and installed 64 bit instead and it worked perfectly.
simply install 64 bit version of JAVA from http://java.com/en/download/manual.jsp
and uninstall older version if prompted by the 64 bit installer
Go to the folder where you saved Eclipse. Look in the configuration folder at the startup log. It will give you a much better diagnostic than "exit code 13".
After java update, eclipse will not start because default jdk location has changed. Adding the following lines to eclipse.ini file solved my problem immediately:
-vm
C:\Program Files (x86)\Java\jdk1.7.0_75\bin\javaw.exe
I added these lines just before vmargs. It looks like as the following :
...
--launcher.defaultAction
openFile
-vm
C:\Program Files (x86)\Java\jdk1.7.0_75\bin\javaw.exe
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Dhelp.lucene.tokenizer=standard
-Xms40m
-Xmx512m
For more information on eclipse.ini, visit this the site http://wiki.eclipse.org/Eclipse.ini#-vm_value:_Windows_Example
In my case, i use 32 bit eclipse and java. If you installed both 32 bit and 64 bit versions of java, be careful to choose the right version. For 64 bit versions, refer to the javaw.exe file under the directory
C:\Program Files\Java\jdk1.8.0_60\bin
Whenever you see this error, go to Configuration directory and check for a log file generated just now. It should have proper Exception stacktrace. Mine was a case where I got an updated 32-bit JRE (or JVM) installed which was the default Java that got added to the Path. And my Eclipse installation was 64-bit which meant it needed a 64-bit VM to run its native SWT libraries. So I simply uninstalled the 32-bit JVM and replaced it with a 64-bit JVM.
I wonder if they will improve this reporting mechanism, instead of silently generating a log file in some directory.
This error occurred to me on ubuntu, having installed 32bit and 64bit java. Use
sudo update-alternatives --config java
to set the right version to use as default.
Just uninstalled jre-32 bit version and It worked fine for me.
I was using Eclipse Juno and I didn't remember if it was 32 or 64 bits. I installed Java 32 bits and that's why it failed. I then installed Java 64 bits and Eclipse Juno is working again.
I also removed any java or jre reference in my environment variables (PATH).
In my opinion the most answers here regarding different architectures of Eclipse and Java are simply wrong and this can be easily checked using e.g. Process Monitor under Windows. The -vm option is there to run a specific version of java and the point of it is, that the configured process is started and runs all the Java code on its own, that's why you configure up to java.exe. In that case you DON'T need to have the same architecture for Eclipse and Java, but can happily mix both 32 Bit and 64 Bit. You only CAN'T mix both, if you DON'T use -vm, but let Eclipse load Java natively into its own process using jvm.dll and such. That latter behavior is Eclipse's default, but not the case anymore if you properly configure -vm in eclipse.ini.
If you don't believe me, do some tests on your own using different architectures of Eclipse and Java and do configure -vm or not properly. In the end, that's exactly what the questioner described in his comment to the accepted answer:
Cannot run Eclipse; JVM terminated. Exit code=13
He is telling that a 64 Bit JDK is working now, but in his screenshot one can see that his Eclipse is 32 Bit, because the path for launcher.library is 32 Bit.
And now for the reason I came here: Ony of my customers had some problems loading one of our Eclipse/OSGI based applications as well and Java exited with exit code 13. In the end it showed that the problem was not about -vm or the architectures of Java and eclipse.exe, but instead he was simply missing config.ini and I guess eclipse.exe wasn't aware what to load or such. After we recognized that and put a config.iniback in place, the app loaded fine with using -vm and a 64 Bit JRE7 in combination with a 32 Bit eclipse.exe.
I had the same issue on Ubuntu, and solved it by unpack all *.pack files in jdk directory.
for example:
cd /usr/java/jdk1.7.0_03/jre/lib
sudo ../bin/unpack200 rt.pack rt.jar
use the configuration below;
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.200.v20130807-1835
-product
org.springsource.ggts.ide
--launcher.defaultAction
openFile
--launcher.XXMaxPermSize
256M
-vm
C:\Program Files\Java\jdk1.7.0_51\jre\bin\javaw.exe
-vmargs
-Dorg.eclipse.swt.browser.IEVersion=10001
-Dgrails.console.enable.interactive=false
-Dgrails.console.enable.terminal=false
-Djline.terminal=jline.UnsupportedTerminal
-Dgrails.console.class=grails.build.logging.GrailsEclipseConsole
-Dosgi.requiredJavaVersion=1.6
-Xms40m
-Xmx768m
-XX:MaxPermSize=256m
-Dorg.eclipse.swt.browser.IEVersion=10001
I fixed it reinstalling the jdk. In my case it was necessary to do:
java -version
sudo apt-get purge openjdk*
sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java7-installer
java -version
javac -version
taken from Install Java JDK+JRE (oracle) in Kubuntu 13.04 from apt
In my case JAVA path was not set in Env variables. Started to work after correct path was set in Env PATH.
Type javac in command prompt and make sure JAVA PATH is correct.
I did couple of things inorder to get rid of this annoying error as modifying .ini never worked for me.
Installed latest JDK
Delete old eclipse IDE folder completely.
This time i Unziped to different location
Double Click "eclipse.exe" Works now like charm
Use default workspace to load your old projects.
Am suspecting it to be JDK's Java VM issue more than eclipse.
I used the new Eclipse Installer. I didn't like the installation path and I changed it manually. After that, I got the exit code=13 message too.
There is a new property in the eclipse.ini file named -install. I just had to modify it with the new location, and that solved this issue.
In the new installer I selected D:/eclipse, but the IDE was installed at D:/eclipse/eclipse. So, I moved the folder manually. The next time I tried to open eclipse I got the exit error. Thus, I had to modify eclipse.ini and set the current location:
-install
D:/eclipse
Before going to the solution, let us know why it is showing that error. If you know the problem behind this issue we can easily fix that error.
Reason 1: The most common reason behind this problem is, we are trying to install different bit version-that is, 64 bit or 32 bit version of the software. It maybe either Eclipse or Java.
Solution:
Check which version of operating system you are running.make sure you downloaded the same version of Eclipse as well as same version of Java software.
Reason 2: Configuration mistake in Eclipse.ini file
Solution:
Add this line "-vm then path of your java sdk" at the end of Eclipse.ini file. for example:
-vm
C:\Program Files\Java\jdk1.7.0_71\bin\javaw.exe
Reason 3: Special characters ( #, !, #) in Eclipse installation directory.
Solution:
Make sure you don’t have any special characters.
Reason 4: You have added JAVA path two times in PATH system variable and both the path are different.
Solution:
Remove one incorrect/different JAVA path from PATH system variable.
Reason 5: You maybe using latest version of Eclipse, but you might be using wrong version or unsupported version of Java Virtual Machine (JVM).
Solution:
To check which version of java you are using open command prompt by pressing win+R key and type cmd and press enter. Now in that console type Java -version command to know java version.
Now research whether eclipse support that version or not.
Or
You can open “readme” folder in Eclipse folder and open readme_eclipse.html to see which version it supports.
for ones with Eclipse Neon
I wanted to run Eclipse Neon and had JRE 1.8 but JDK 1.7
It returned error=13
then I installed java JDK 1.8 and everything worked like a charm
I had this issue also. I had an old JDK1.8.0_05. I installed the newest JDK1.8.0_111 and everything works great now. Just be sure to update your environment variable.
I am on Windows 7 64 bit.
Using Eclipse Neon 1a.
Hope that helps someone.
I face same issue with sts 3.8.4, so I tried different settings but not luck,
I reinstall jdk again n tried but same problem.
Finally I downloaded sts 3.8.2 n it runs with out any issue.
Using windows 8, 64 bit os.
thanks
This can happen when the PATH environment variable is point to a wrong java instalation.
I have thoroughly researched this problem and the posted solutions have not worked for me.
I'm running Windows 8, and the most recent JAVA JDK (64 bit) and Android Studio versions.
[System specs: new XPS 13, core i5, 8GB RAM, SSD]
The exact error is:
Failed to load JVM DLL C:\Program Files\Java\jdk1.8.0_45\jre\bin\client\jvm.dll
If you already have a 64-bit JDK installed, define a JAVA_HOME variable in ... Environment Variables
-- Verification --
java -version
java version "1.8.0_45"
Java(TM) SE Runtime Environment (build 1.8.0_45-b15)..
-- Things I've tried --
Uninstall java and AS, reboot, install 64 bit java jdk, verify installation, reboot, install AS, set JAVA_HOME variable
YES, the viable is an Environment variable and not a User variable
I have added the /bin/ directory to the "path" environment variable
I have reversed the slashes in the environment variable paths as per one solution stated
Followed the uninstall/reinstall process stated above, but with a 32bit jdk instead (with the correct environment variable paths)
Done the whole process over (uninstalling, rebooting after installs, etc.) but with older JDKs
I have tried running studio.exe with 32 bit JDK installed, and studio64.exe with the 64 bit JDK installed
I feel like I've tried everything. I HAD to have screwed up somewhere along the line. Any idea?
Try running android studio as Administrator. That worked for me. Try installing a different version of Android Studio.
This worked for me...
Try running studio64.exe instead of studio.exe.
I had to install vcruntime140_1.dll via https://learn.microsoft.com/en-US/cpp/windows/latest-supported-vc-redist?view=msvc-170 to solve the this issue. I used process monitor to see that it was missing.
Tried everything nothing worked. Restarted my laptop, Android Studio works perfectly.
I installed Microsoft Visual C++ X86 or X64 from here and AS started up fine.
you said you have added /bin/ directory to the "path" environment variable, if you are putting C:\Program Files\Java\jdk1.8.0_45\jre\bin .that is wrong it should be C:\Program Files\Java\jdk1.8.0_45\jre\bin\client to path system variable and you put it as first item.
I checked my java installation path. I found jvm.dll is located at C:\Program Files\Java\jdk1.8.0_45\jre\bin\server please check yours.
see the screen shot.
I got it working. I uninstalled everything again. Reinstalled the 64 bit jdk, remade the environment variable, rebooted, reinstalled Android Studio and it still was not working.
I downloaded the 32 bit JDK just got giggles and installed it. I did not uninstall the 64 bit java... I pointed the environment variable to the 32 bit JDK directory and tried to launch Androd studio with the 32 bit .exe (not studio64.exe), and it worked.
I guess I'll have to live without 64 bit.
Thanks for the help, everyone.
Downloaded OS X Yosemite Beta 3 and I'm trying to run some eclipse based IDE's, namely Titanium Studio and Aptana Studio.
Running into this error message when I try to start the apps. Didn't work on boot, so I downloaded JDK 1.8.0_40, still no dice. It's looking in the proper location, the file exists and it's using the correct java version. Not sure what the issue is, any help would be appreciated.
Download the newest version of Java for OS X 2014-001 from Apple. http://support.apple.com/kb/DL1572?viewlocale=en_US&locale=en_US
I encountered the same error this morning and this was a quick and easy fix.
I got this problem when I try to lunch AptanaStudio 3.1 on OSX yosemite.
I google this problem for quite a lot and found that JDK1.8(64-bit) version just does not support the Aptana Studio(3.1), maybe also not working on some other IDE which based on the same skeleton of Eclipse.
The only solution I can came out is to install an older version of JDK, and I found that the link #ChancePance provide just worked for me.
Why I am answering this question is just to specify that it's OK to install this version of JDK(which is version 1.6.0_65, 64-bit when I download the package) alongside with the J2SE 1.8(provided by Oracle). So you don't have to worry about there is any conflicts while installing two version of JDK.
I need the JDK1.8 for some of the new features of the latest version of Oracle's J2SE. And I need Aptana Studio at the same time. I am quite worried about there might be some conflicts.
Below is what I have done on OSX Yosemite to solve the problem of AptanaStudio3.1:
Download and install the package: JavaForOSX.
Found the file "AptanaStidio3.ini", the file by default located under the the directory here: /Applications/Aptana Studio 3/AptanaStudio3.app/Contents/MacOS
Add "-vm" argument to specify the java which will be used to lunch Aptana Studio.
-vm
/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/bin/java
Hope this will help you guys who got the same problem.
I ran into this problem as well. Apparently Aptana Studio is 32-bit, while the java I have installed is 64-bit.
I didn't want to revert to Java6 as the accepted answer suggested, so I solved it another way.
I downloaded a 64-bit version of Eclipse and installed the plugin version of Aptana Studio.
I was also experiencing this problem because I had a 64 bit JDK 1.7 installed (the standard Oracle version - not the Apple version indicated in the other answers) and had mistakenly downloaded a 32 bit version of Eclipse. Doh!!
I removed the 32 bit version and downloaded the 64 bit version of Eclipse and everything works great now.
Simply downloading the newest Java for OSX worked the charm. I clicked and downloaded the file from the link above -> http://support.apple.com/kb/DL1572?viewlocale=en_US&locale=en_US <
Open "/Applications/BonitaBPMCommunity-6.5.0/BonitaBPMCommunity.app/Contents/MacOS/BonitaBPMCommunity.ini"
Obtain the location of the JRE / JDK on your system by executing in a terminal:
/usr/libexec/java_home
Add 2 lines after adapting the ...jdk1.8.0... to your system as found out above
-vm
/Library/Java/JavaVirtualMachines/jdk1.8.0_31.jdk/Contents/Home/bin/java
in between the following lines:
-clearPersistedState
-vmargs
Every time I try to start Eclipse, it says
Failed to load the JNI shared libraby
"C:\Program Files (x86)\Java\jre7\bin\client\jvm.dll"
I have no clue why this happens, because I reinstalled JDK, JRE and Eclipse multiple times. All the 64 bit version (I've got Windows 7 64 bit)
Alright, it somehow worked using the 32 Bit version of Eclipse...
If you have installed all 64 bit version of Eclipse and JDK, you can check your system environment variable. Probably you set on old JAVA_HOME path pointing to
"C:\Program Files (x86)\Java"
I had the same problem: in my case everything was in fact 64-bit - 64-bit OS, 64-bit Eclipse and 64-bit JRE in use, so there was some confusion as to the origins of the issue...
What helped was correcting environmental variables JAVA_HOME and PATH - and pointing them directly to
.../My/Java/Location/bin
instead of
.../My/Java/Location
If eclipse is 32bit
then, eclipse.ini file
specify -vm C:\Program Files (x86)\Java\jre\bin\javaw.exe
If eclipse is 64bit
then, eclipse.ini file
specify -vm C:\Program Files\Java\jdk\jre\bin\javaw.exe
Summary: specify compatible java version path ( 32 bit or 64 bit ).
-vm %JAVA_HOME%\jre\bin\javaw.exe
Just try to download this if you have 64 bit OS windows.Hope it will work :)
Trying to open Eclipse after a couple of months and get this error:
So I checked that folder to see if it existed, and it did:
I checked my PATH Was correct and it was also correct:
When this error first occurred I had 3 Java installations. JRE 7 Update 10, JDK 7 Update 7 32bit and 64 bit.
I uninstall ALL and restarted my machine. Eclipse then stated, as expected that I needed a JRE or a JDK. So I downloaded and installed the latest JDK and now I get this error, despite everything appearing to be correct.
Any ideas?
As requested in the comments.
Your eclipse version is searching for the x86 version of the jdk (You probably set this value when eclipse started). You should check if your eclipse is a 64 bit version if not, switch to a 64bits jvm.
the problem lies with compatibility issue of jdd 6 with eclipse.I tried jdk 7 and it worked perfectly.Here is a link for jdk 7 downloading
http://download.cnet.com/Java-Development-Kit-64-Bit/3000-2218_4-75317068.html
The problem is with the Eclipse version. I faced the exact same problem, I was using Eclipse helios. I switched to Eclipse Kepler 64 bit and it is now working perfectly on my system. Even if the eclipse is 64 bit, some versions may not be compatible with other softwares using the same Java path (Eg: Oracle BI Publisher). Make sure to use the version compatible with others.
FIX for :: jvm.dll file missing issue while you open eclipse
This issue appears because of (64 or 32 bit) version conflict/mismatch happens between
installed OS,
Java(JDK)version and
eclipse version.
I got this issue and fixed it in this way.by adding the below argument (64 bit Java(JDK) path) in eclipse.ini.
-vm
C:\Program Files\Java\jdk1.8.0_144\bin
My environment,details below
Mine is windows-7 64bit OS,
Java(JDK) 64 bit (so path specified in eclipse.ini)
Eclipse 64 bit(never confuse the eclipse version as 32 bit by seeing the win32.x86, see the later _64) i.e I use eclipse version below.
org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.500.v20170511-1520
You can see your eclipse version in eclipse.ini file.
Note:
I have another Eclipse (plugin tool) installed in my machine, which had the same issue, was expecting 32 bit Java(JDK), After I fixed the issue by setting the path for 32bit Java1.8 in environment variables, the primary eclipse stopped working.
So I set 64bit Java1.8 path in eclipse.ini.
Now both eclipse.exe and my plugintool eclipse working fine.
Thanks,
Murali
Here we fristly check the ur path. when ur path is correctly. Then after u will move the given location (their checking jvm.dll file will be presented or not).
that type problem came max to max 64-bit systems.
Here main focus on path. when u set path then after retsart the system.
This happend to me yesterday and fortunately I found this post.
I was working on eclipse and tried to compile a class using the command line in paralell. I noticed that the javac command wasn't on the Path environment variable so I added.
Afterwards, I closed Eclipse and when I tried restarting the IDE I found the "Failed to load JNI shared Library" error.
I opened back the environment variable dialog box and pointed the java bin path to a compatible version of java (Same bit version on both, eclipse and jdk).
Finally I was able to start eclipse again.