Eclipse worked fine for months, all of a sudden I'm getting error code 13 when trying to start. Searches indicated this was from incompatible "bitness" of java. I've since downloaded a new copy of eclipse, uninstalled all copies of java, reinstalled just x64 & run eclipse x64, uninstalled & tried x86 with 32 bit eclipse & every other possible combination.
Right now if I run eclipse with its own copy of the JDK folder locally I either get error code 13 if I use 32 bit java with 32 bit eclipse, or "Failed to load the JNI Shared library" if I use the 64 bit copy.
Take a look if this can help you.
According to this site, there are some Reasons to the error, see the link above that explain how to fix it.
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.
Reason 2: Configuration mistake in Eclipse.ini file
Reason 3: Special characters ( #, !, #) in Eclipse installation directory
Reason 4: You maybe using latest version of Eclipse, but you might be using wrong version or unsupported version of Java Virtual Machine (JVM)
http://www.ashout.com/fix-java-started-returned-exit-code13-eclipse/
Yeah, I'd already read & tried all of that.
The solution was absolutely ridiculous:
I noticed when I tried to verify java via browser all I was getting was a grey box, and java applets on other pages were failing. After hours of insanity I noticed I was having some network issues with other apps as well.
Turns out a permissions error on HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\services\Tcpip\Parameters\Interfaces{(my interface id)} caused Java to crash globally for any user in the system running any app in the system.
This was causing random errors such as
NoClassDefFoundError
Could not initialize class sun.security.provider.SecureRandom$SeederHolder
This interface wasn't even in use & in fact didn't exist any more, but when I tried to open the key I got an Access Denied error. After I took ownership of this key & deleted it java works everywhere again.
Related
I tried to download Java on my laptop (which has windows 10) but i keep getting a 1603 error. My computer used to have windows 8.1 and it did not work back then either
I appreciate any advice to solve or work around this problem
I have had this problem. I was able to fix it thanks to a co-worker. The problem started happening after I installed HP Unified Functional Testing (UFT, aka QTP). Installing this product changes the Windows environment variables used by Java. He told me the following: "So change the names of JAVA_OPTIONS, IBM_JAVA_OPTIONS, JAVA_TOOL_OPTIONS to something else (both in system and user variables) and delete any Java folder(in Program Files (x86) or Program Files) which gets installed despite the error. Restart the system and then try installing Java."
Actually, all I did was rename the environment variables and run the installer. This worked.
My answer is not related to win 10, but might help someone who is having similar problem in windows 7 machine and not able to install jre 32 bit version.
the work around to this is once you downloaded the jre, copy the path "C:\Program Files (x86)\Java\jre1.8.0_121\bin\javaw.exe" and paste it under java runtime environment settings which is found -Java Control panel>java>view
I think you downloaded the wrong version. If your laptop support x64 bit software you should download Java 1.8 x64 version.
Here is the link.
https://www.java.com/en/download/manual.jsp
I had this problem for a month now. I tried everything on my windows 8, but I couldn't get the latest java on it. When I tried to install java on an empty computer, the 64 bit version did not go through (error 1603) and I realized the problem didn't come from an old java install and I install 32 bit. it worked on the new computer with windows 7 and on my computer running 8.1.
note: I had deleted all the java versions before going through with it.
To fix java 1603 error you have to follow few simple steps.
First of all remove all old java version.
Then remove some windows update file which might be reason of this
error. Like KB2918614 update.
After that download and Install latest version of java and activate
java in browser. Now everything will be fine you can test the java
version on java website...
For explained and easy solution to java 1603 error follow this link: http://protechguides.com/java-error-code-1603-solved/
I encountered this error on Windows 8.1 and when I checked with Oracle web site, they said that is is not yet resolved, and under investigation. They also showed a link for off-line installation as an alternative arrangement. However, upon investigation of my system, i found out that the available space in C drive was only about 20 MB or so. I cleared my system and provided enough space. When I tried with the extra space, I didn't encounter any error. May be, you could try with a better free space...
First you should close the browser because if any webpage will use Java, it will cause conflict. Then do custom installation, i.e. install in some other folder other than default folder and point environment variable to newly installed Java location. It will resolve your issue.
Firstly I install JDK & JRE, it install correctly and works properly, but when I run Net-beans setup which is of 64 bit , after configuring process it shows an error and shows a message as title of Critical and displaying NUll Null message, I'm using window 8 with 64 bit (OS).
So how I Can come out from this problem?
Please help me my all friends on this issue........
Make sure you have installed JDK 64bit. during the setup jdk64 you may face with error when setup is trying install JRE, and it's normal, let just finish the setup.
I always have problems with windows too, you may just simply download the OS-independent package from netbeans.org. just extract and use it.
checking package(either zip or exe) hash is recommended, even a bit would mark the whole package incompatible.
You may also set the jre_home, java_home and jdk_home too before netbeans run.
I have two versions of Eclipse that I use (Indigo for C++ and Helios for Java). I've used both for years without problems. Last week I needed to view Java Bytecode, so in my Environment Variables I added "C:\Program Files\Java\jdk1.6.0_26\bin;" to the Path variable (this let me use javap 'class' -c to view bytecode in a command prompt).
I continued to use Helios just fine. Today I tried booting up Indigo to work on some C++ code, but I got the "Failed to load JNI shared library etc." error for it, causing it to force close. Eventually I tried removing that path I placed in environment variables, and Indigo boots up correctly again.
Any idea why this happened? I don't fully understand paths, but I don't see why adding the path I did would cause my other Eclipse to break. I don't really need javap anymore so I removed the path, but I'm still curious as to why this happened.
Thanks for any insight!
With the change to the path Eclipse was probably trying to load 32 bit Eclipse with a 64 bit Java (or the other way round), they both have to be 32 bit or 64 bit.
I am trying to launch an application (not Eclipse) that was written in Java. When I do, I get an error that says "Failed to Load the JNI shared Library (JDK)" along with a path that points to the location of the file.
From searching Google and StackOverflow, all I can find are people saying that the Java version installed needs to match my machine. My machine is 64 bit and so is my java installation, so I don't think that is my issue.
I have also verified that C:\Program Files\Java\jre7\bin is in my path variable. Also, just for the record, I do not use Eclipse. I have also tried uninstalling and reinstalling Java an the application that was written in Java. Lastly, the file it is complaining about exists on the machine.
Does anyone know what else could be the cause of this problem?
Update:
Thanks for your responses. I got it resolved, but the resolution seems like more of a hack and goes against what I was reading earlier. I installed the 32 bit version of Java 7 along side of my 64 bit version of Java 7. I then added the path the 32 bit version to the system path variable.
After I did this, the application was able to launch. Is there an issue with having both 64 bit and 32 bit versions of Java 7 installed simultaneously?
This is an error from your application. The application uses JNI. It is complaining that it cannot load it. Why it says (JDK) only its author knows. You will have to ask the author.
There is no problem having both versions of Java installed. However, the application you were using probably shipped with a 32-bit version of the JNI library. So, it needed to be used with a 32-bit Java JRE.
After a couple of months with no Android development, I ran the SDK Manager yesterday, and upgraded from r16 to r18. After that upgrade, everything stopped working. I downloaded a fresh copy of the SDK tools from Google. The Windows installer complains there's no Java installed (the solution here , which used to work before, doesn't work).
I downloaded the ZIP file instead and put it in the right place. Running SDK Manager.EXE does nothing (it just returns immediately to the command prompt). Running tools\android.bat displays an error complaining "Failed to convert path to a short DOS path: c:\windows\system32\java.exe", and then suggests I install Java.
I'm running Windows 7 64-bit, with Java 1.7 (64 bit) properly installed (Eclipse runs well, the Android tools r16 ran very well until yesterday). c:\windows\system32\java.exe exists and works as it should.
What am I doing wrong?
UPDATE: I found an old r16 setup around. I installed it and everything went back to normal.
I put this one aside for a while, but now I had to get it back running. I didn't want to install a 32-bit Java VM alongside the 64 bit one I have.
I found the culprit. in android_sdk\tools\lib there's a batch-file called find_java.bat. It calls find_java.exe -s to find a list of potential Java locations. Running the exe file like this returns the error I've been seeing:
Failed to convert path to short DOS path: c:\windows\system32\java.exe
-s stands for short. Running it without the -s causes find_java.exe to work, causing find_java.bat to work, causing everything else to work. So the fix was to edit find_java.bat, and remove the -s .
I honestly don't know what Google is thinking.
My fix was to remove /bin from my JAVA_HOME, as in C:\Java\jdk1.6.0_26\bin --> C:\Java\jdk1.6.0_26\
I'm running 64bit java on W7.
This google issue was helpful:
http://code.google.com/p/android/issues/detail?id=23648
This is just a guess, but I advise you to install JDK 6. It is said in the SDK requirements that you have to use it. I remember that I installed JDK 7 and I had some kind of trouble with it too.
Also it is safer to use the 32-bit version.
You need to also update the Eclipse plugins via Help > Install New Software.
I was able to fix same like problem by adding the jdk path to PATH variable in environment variables.