CODEWITHSUNDEEP
oracle-databaseoracle-sqldeveloper
4532066
4532066

Reputation: 2110

SQL Developer 17.2 - Unable to launch the Java Virtual Machine

SQL Developer version 4.2.0.17 is set up on a computer I'm using (I'm using Windows).

The folder for that version contains a jdk folder and the SQL developer runs fine.

I downloaded SQL Developer 17.2 and unzipped the file. When I went to run the .exe I was asked to confirm the location of the jdk on the computer.

At that time, I didn't realise that the jdk folder was already in the folder for SQL Dev 4.2.

There is also an 'OraHome_WF' folder on the c:\ drive, which contains a jdk folder, so I confirmed that was the location of the jdk folder when first launching SQL Dev 17.2.

Now when I launch SQL Dev 17.2 I get an error message:

Unable to launch the Java Virtual Machine Location at path: C:\OraHome_WF\jdk\jre\bin\msvcr100.dll

I looked in the 17.2 folder to see if there were any config or settings files that might have been updated after I put the wrong jdk path in, so I could point to the correct jdk folder, but I can't see anything.

I tried deleting the 17.2 files and unzipping the 17.2 folder again, but when I launched SQL Dev I got the same error without being asked where the jdk folder is located.

Is there any way I can work around this problem?

I already tried this workaround: SQL Developer error Unable to find Java Virtual Machine

Upvotes: 6

Views: 37209

Answers (2)

Ranjith Reddy
Ranjith Reddy

Reputation: 129

I faced similar issue for Jdeveloper. Apparently the latest jdk does not have the msvcr100.dll file. I resolved it by previous jdk version Jkd 8u221 which has this file and it ran successfully

Upvotes: 1

krokodilko
krokodilko

Reputation: 36087

According to the documentation, user preference settings are located in the following locations:

SQL Developer user preferences

Windows: C:\Users\\AppData\Roaming\SQL Developer\systemn.n.n.n.n

Linux or Mac OS X: ~/.sqldeveloper/systemn.n.n.n.n

Removing this subdirectory should fix the problem (and in this case it fixed it).

Upvotes: 8

Related Questions