SQL Developer failed to start

Question

I\'ve just installed SQL Developer 4.1.1 64-bit on a Windows Vista machine, in directory c:\\sqldeveloper.

My Java installation is in c:\\program

Answer 1

I ran in to the same problem myself, trying to run SQL Developer 4.1.1 64-bit with JDK on a Windows Server 2008. I've installed SQL Developer many times over the years from 1.x to 4.1.1 and never encountered this until now.

I solved it by copying the MSVCR100.dll file from sqldeveloper\jdk\jre\bin to the sqldeveloper\sqldeveloper\bin folder.

Update 3/18/2017:

In downloading the latest version from Oracle's website, I found this in the installation notes which confirms and explains the issue:

Note: the Windows EXE requires a MSVCR100.dll to run. Most computers will already have this file and in the Windows PATH. However, if the first copy of the file found by the EXE is a 32-bit copy of the DLL, then SQL Developer will fail to start. You can fix this by copying a 64-bit version of the DLL into the BIN directory or updating your OS PATH such that a 64 bit copy of the DLL is found first.

Answer 2

You only need to create the directory \bin in sqldeveloper \sqldeveloper\jdk\bin and copy the msvcr100.dll file in this new directory.

Answer 3

Only create the directory /sqldeveloper/jdk/bin and copy The file msvcr100.dll is in the directory.

Then /bin don't exist is in the /sqldeveloper/jdk

Answer 4

Got the same issue with newest versions.

Interestingly enough, msvcr100.dll is present in JRE 1.8.0_251, but not in JRE included in JDK 1.8.0_261. Even though I run SQL Developer with included JDK, it tried to use my installed JRE 1.8.0_261.

Resolution was simply to copy missing msvcr100.dll from any other place (like jre1.8.0_251\bin or maybe even Windows/System32) to the JRE used by SQL Developer. In my case to jdk1.8.0_261\jre\bin.

Answer 5

You need to copy the msvcr100.dll file from sqldeveloper/jdk/jre/bin/msvcr100.dll to sqldeveloper/sqldeveloper/bin/. Then just open SQL Developer again.

Answer 6

I have faced this similar issue on my local system.
I have solved this issue by copying bin directory from insatallation_directory/jdk/jre to insatallation_directory/jdk/