But run this from a cmd window - run the sqldeveloper.exe out of the bin directory and show us the stack dump.
Forgot to mention it is on a Windows 7 32 bit machine.
Thanks for the quick reply, sorry, but I am not sure how to generate the stack dump, can you please share the steps for it.
Start > Run > CMD
CD to your $INSTALL\bin directory
Copy and paste the output back here
I followed your instruction, but there was no stack dump in CMD window, below is the result, same case, the progress bar reached to 4 bars, and shut off and went back to command line, no dump.
The JDK 1.4 was installed via installation, the SQL Developer 4.1 was just a unzip to a folder.
Do I need to enable the Java trace for getting the dump?
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
So you have a 32 bit JDK for Java 8?
If you run 'java -version' from that same CMD window, what do you get?
I had a similiar issue with SQl Developer on Linux.
There was an invisible command prompt that was asking me for the directory location of the Java install.
Running this from the command line allowed me to see the previously invisible pronpt.
Here is the result
java version "1.8.0_31"
Java(TM) SE Runtime Environment (build 1.8.0_31-b13)
Java HotSpot(TM) Client VM (build 25.31-b07, mixed mode, sharing)
What is the command? I am using Windows 32 client, is there a similar command?
Thanks for your help.
Is there any other suggestions? Anything else to check?
When all else fails, try:
- find your application data directory, rename it
- find your product.conf, make sure the SetJavaHome is correct
For #2, on Windows:
You'll have a 4.1 folder..that's the one you want to check.
Now go up two directories, that's where you'll find a 'SQL Developer' folder with a subfolder of system4.1.... -> that's the one you want to rename for #1
It seems did trick, the SQL Developer is now able to load and start. Thanks for your help.
Here are what I did,
1 renamed the application data directory
2. un-comment the following lines in product.conf
not sure #2 has any effect on it or not.
again, thanks for your help.