Eclipse Helios not starting

Question

I used Eclipse in the past with no problems more than a year ago, but now I downloaded Helios to a new computer with Windows Vista and Java 1.6.13. I extract the folder and try to start the Eclipse exe and get the error message "Java was running, but exit code = 13 returned."

I did some copying and it seems that the configuration file requires running Java 1.5 (dosgiRequiredJavaVersion = 1.5). Removing this line does not matter.

I went and got an archived copy of 1.5.0_22 and tried using -vm mypath / java / jre1.5.0_22 / bin in the configuration file before vmargs, and that still doesn't help.

I also tried making a shortcut and specifying "eclipse -vm mypath" in the target properties field and still nothing.

Here are my configuration settings that still give an error:

-startup plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar --launcher.library plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.0.v20100503 -product org.eclipse.epp.package.java.product --launcher.defaultAction openFile --launcher.XXMaxPermSize 256M -showsplash org.eclipse.platform --launcher.XXMaxPermSize 256m --launcher.defaultAction openFile -vm c:\program files\java\jre1.5.0_22\bin -vmargs -Dosgi.requiredJavaVersion=1.5 -Xms40m -Xmx384m 

Has anyone solved this problem?

Answer 1

This happens when using x86 Eclipse with the x64 JDK (and possibly vice versa). Just specify the JDK with the same architecture as your Eclipse in the eclipse.ini file, for example:

 -vm D:/Dev/Java/jdk1.6.0_25_x86/jre/bin/javaw.exe 

Answer 2

I had the same problem.

I am on Windows Vista 64 with 64-bit versions of both Helios and JDK / JRE 1.6. 14. I made excellent use of Eclipse Galileo.

Upgrading to JDK / JRE 1.6 24 (the latest as of this date) fixed the issue. I do not need to make any changes to the Helios eclipse.ini file.

Answer 3

If this started when it would seem that nothing has changed with respect to your eclipse and java installations, and there is a chance that it started after a system crash (Windows) or an unexpected eclipse closure, the problem may be related to changing the compatibility mode of eclipse.exe . When the system or eclipse crashed, Windows may have decided to change the compatibility mode of eclipse.exe, whether you like it or not.

Unfortunately, this mode cannot be changed on the "Compatibility" tab of the file properties. This change must be made by editing the registry. Find two keys:

• HKEY_CURRENT_USER \ Software \ Microsoft \ Windows NT \ CurrentVersion \ AppCompatFlags \ Compatibility Assistant \ Persisted
• HKEY_CURRENT_USER \ Software \ Microsoft \ Windows NT \ CurrentVersion \ AppCompatFlags \ Layers

Search for any entries for eclipse.exe. I deleted one from each place and this solved the problem for me.

Compatibility information is tied to a file name and stored in the registry, even if the file itself is deleted or moved. This is why changing the location of the eclipse directory will solve the problem. It also means that reinstalling eclipse in the same place will not fix the problem, as the registry entry will still be there.

Answer 4

ok, so I had this problem and the update did not work, I fixed it, because, apparently, my computer was not pointing to the right place or was not confused

I have a 32 bit machine and 32 bit java

I had an eclipse folder on my desktop and it gave me this error

I just moved the eclipse folder to the program files and it worked, I don’t know why

Hope this helped good luck!

Answer 5

For me, setting switch -VM at the beginning of the eclipse.ini file worked. Also, I have both Java and Eclipse in the 32-bit version, although I have the 64-bit version of Win 7.

Answer 6

I also had the same problem with Eclipse Indigo on 64-bit Windows 7. The error message was "Java was running, but exit code = 1 returned."

Updating the latest JRE 1.6 29 update has been fixed.

Answer 7

Move the folder to Program Files . This fixed my problem with error code 13.