|
|
|
Re: Eclipse IDE for Java Developers doesn't start-up. Exit code 2 [message #1861879 is a reply to message #1797195] |
Thu, 09 November 2023 17:55 |
Petre Mocanu Messages: 3 Registered: November 2023 |
Junior Member |
|
|
David Wegener wrote on Sat, 27 October 2018 15:38You appear to have a corrupted version of java installed. I can't be sure of the exact issue, but I would suspect a failed uninstall of an older version or some conflict when installing a new version. From the log file you posted, the java executable being run is C:\ProgramData\Oracle\Java\javapath\java.exe. This is giving the first three error messages that you list. Searching the internet for this path name seems to indicate that Oracle started using this location with Java 8. It seems its purpose is to use the registry to locate the actual VM to run. Eclipse runs in the java VM, so it won't be able to run until java can be started cleanly. I would focus on getting the java -version command to run successfully. After that, you can move on to getting Eclipse running again.
I'm not sure what you need to do to fix the problem. Perhaps you can check installed software to see if there are old Java versions listed. Maybe an uninstall of any java versions (both jdk and jre) followed by a reinstall of the one you want to use will help.
Sorry I couldn't be more helpful, but I'm not very familiar with Java installation issues.
You know, I've been where you are - frustrated with my computer not working correctly andJava errors getting in the way. It seems like you've run into one of those nasty corrupted Java issues, based on the error messages you described.
When I looked up that particular file path it was trying to run from, it sounded really familiar - I remember Oracle changing things up with Java 8 and using that weird ProgramData folder that always seemed to cause problems. No wonder your Eclipse wasn't launching!
The thing is, sometimes you just need to do a total cleanup and fresh start with Java. I know it's a pain to uninstall and reinstall everything, but in my experience, that's usually the quickest way to clear out all the old corrupted files and configure it properly.
I'd also definitely check for any other programs you don't need taking up space; you never know what kind of junk might be interfering. And don't forget to scan for viruses just to be safe - the last thing you want is some malware sneaking in there.
|
|
|
|
|
Re: Eclipse IDE for Java Developers doesn't start-up. Exit code 2 [message #1862113 is a reply to message #1797195] |
Mon, 13 November 2023 18:44 |
Wladyslaw Gorski Messages: 4 Registered: November 2023 |
Junior Member |
|
|
David Wegener wrote on Sat, 27 October 2018 15:38You appear to have a corrupted version of java installed. I can't be sure of the exact issue, but I would suspect a failed uninstall of an older version or some conflict when installing a new version. From the log file you posted, the java executable being run is C:\ProgramData\Oracle\Java\javapath\java.exe. This is giving the first three error messages that you list. Searching the internet for this path name seems to indicate that Oracle started using this location with Java 8. It seems its purpose is to use the registry to locate the actual VM to run. Eclipse runs in the java VM, so it won't be able to run until java can be started cleanly. I would focus on getting the java -version command to run successfully. After that, you can move on to getting Eclipse running again.
I'm not sure what you need to do to fix the problem. Perhaps you can check installed software to see if there are old Java versions listed. Maybe an uninstall of any java versions (both jdk and jre) followed by a reinstall of the one you want to use will help.
Sorry I couldn't be more helpful, but I'm not very familiar with Java installation issues.
Dealing with Java issues is so frustrating. I've been there - it's the worst when a program refuses to run. This sounds like my issue years ago at Andersen. An upgrade must have broken the uninstall. I got errors launching anything Java. Clearly an older Java 8 installed instead of the new one. That path brings back memories. Config files probably still conflict.
You have to purge all Java and do a totally clean reinstall. Uninstalling isn't enough - everything must go. A fresh reinstall is the best plan. It's a pain to reinstall, but sometimes you gotta nuke it. I hope reinstalling works like for me - corrupted installs are the worst. Fingers crossed it's resolved!
[Updated on: Mon, 13 November 2023 18:45] Report message to a moderator
|
|
|
Powered by
FUDForum. Page generated in 0.09095 seconds