MSVCR100.DLL error launching SQL Developer 4.1.2 with JDK 8 on Windows 7

Environment: Windows 7 Enterprise SP1 64-bit, SQL Developer 4.1.2.20.64 with JDK 8 included.

Me again :-)

I recently faced an issue installing SQL Developer 4.1.2 on Windows 7, and it took me some time to find the solution, so I’m going to share it…

I downloaded version 4.1.2 of SQL Developer from http://www.oracle.com/technetwork/developer-tools/sql-developer/downloads/index.html, I selected “Windows 64-bit with JDK 8 included” from the list.

I rarely have problems running or upgrading SQL Developer on Windows, but this time was a different experience. After extraction of the zip file to a new folder, I double-clicked “sqldeveloper.exe”, and (surprisingly!) the following error message appeared:

The program can’t start because MSVCR100.dll is missing from your computer. Try reinstalling the program to fix this problem.

MSVCR100DLL

Followed by:

Unable to launch the Java Virtual Machine located at path: …

MSVCR100DLLa

I was confused. The file MSVCR100.dll is part of the included Java Development Kit, so why wasn’t SQL Developer able to find it? I never had an issue like this with previous versions of SQL Developer (I always choose the version with included JDK to avoid Java issues like this one).

After some searches on Google, I found that someone suggested to copy the file MSVCR100.dll from the folder ..\jdk\jre\bin to ..\sqldeveloper\bin, so in my case from C:\sqldeveloper41\jdk\jre\bin to C:\sqldeveloper41\sqldeveloper\bin. Guess what? This worked! SQL Developer started, I could import my previous configuration and everything is looking good :-)

HTH,

Matthias

Installation of Oracle SQL Developer 3.2 64-bit on Windows 7 64-bit

Environment: Oracle SQL Developer 3.2.09 64-bit, Java 1.6.0_34 64-bit, Windows 7 64-bit

Oracle recently released version 3.2 of SQL Developer. This new version has some interesting new features, like the possibility to administer the APEX Listener, the option to connect to databases in the cloud, and an improved DB Diff wizard. To read more about the new features, check this page.

There are both 32-bit and 64-bit versions of the software. I will explain here how you can install the 64-bit version on Windows 7 64-bit.

1) Download and install 64-bit Java 6 JDK

The 64-bit version of SQL Developer does not include a Java Development Kit, but you need a Java 6 JDK to run it. If you don’t already have one on your system, you can download one here: http://www.oracle.com/technetwork/java/javasebusiness/downloads/java-archive-downloads-javase6-419409.html#jdk-6u34-oth-JPR. I downloaded and installed jdk-6u34-windows-x64.exe, the 64-bit version of Java 6 Update 34 for Windows 64-bit.

2) Download and install 64-bit SQL Developer

If you have any previous versions of SQL Developer installed, do not remove them! You should only remove them after the new installation has finished successfully.

SQL Developer can be downloaded here: http://www.oracle.com/technetwork/developer-tools/sql-developer/downloads/index.html. You need the “Windows 64-bit” version.

After the download, extract the “sqldeveloper64-3.2.09.30-no-jre.zip” ZIP file to a temporary folder and then copy/move the folder “sqldeveloper64-3.2.09.30-no-jre” to C:\Program Files. This is where Windows 7 by default installs its 64-bit programs and I prefer to keep it that way.

Now start SQL Developer for the first time by right-clicking on “sqldeveloper.exe” inside the “sqldeveloper” folder. It will now ask for the path to your 64-bit java.exe. Browse to C:\Program Files\Java\jdk1.6.0_34\bin\java.exe. This is the Java 6 JDK that you installed in step 1.

If you have any previous installations of SQL Developer installed, the new version should now show them and you will be given the possibility to import an old configuration. Might be handy to keep your connections and stuff!

SQL Developer should now start up fine. You can check the version under Help -> About.

When you have verified that everything works fine, you are safe to remove any older versions that you should have.

 

Have fun,

Matthias

 

 

 

How to modify the version of Java used for GlassFish 3.1.2.2

Environment: GlassFish 3.1.2.2 OSE Web Profile, Oracle Linux 6.3, Java 7 Update 7.

Whenever you upgrade your Java installation or install a new version, you have to make sure that your GlassFish installation is using the new version.

1) Download and install the new Java JDK 

New versions of Java can be found here. For GlassFish, you need to download the JDK (so not JRE), and you can use both Java 6 or Java 7.

For example, I downloaded and installed JDK 7 Update 7 to /u01/app/jdk1.7.0_07 and I created a symbolic link “java7” to it:

$ /u01/app/java>tar -zxf jdk-7u7-linux-x64.tar.gz
$ /u01/app/java>ln -sf jdk1.7.0_07 java7
$ /u01/app/java>ls -la
total 93904
drwxr-xr-x   4 oracle oinstall     4096 Sep 10 15:16 .
drwxr-xr-x   7 oracle oinstall     4096 Feb 17  2012 ..
lrwxrwxrwx   1 oracle oinstall       11 Feb  7  2012 java6 -> jdk1.6.0_30
lrwxrwxrwx   1 oracle oinstall       11 Sep 10 15:16 java7 -> jdk1.7.0_07
drwxr-xr-x  10 oracle oinstall     4096 Feb  3  2012 jdk1.6.0_30
drwxr-xr-x   8 oracle oinstall     4096 Aug 29 03:12 jdk1.7.0_07

2) Modify the GlassFish domain config file and JAVA_HOME environment variable

Next, you need to modify the AS_JAVA  variable in the GlassFish config file “asenv.conf”. In my case, this file was stored in the folder /u01/app/glassfish/glassfish/config. I changed it as follows:

AS_JAVA=/u01/app/java/java7

You also need to modify the environment variable JAVA_HOME. This variable can be found in the .bash_profile file of the user which is used to start GlassFish. Run “echo $JAVA_HOME” to see its current value. After the changes, log out and log in again (or run .bash_profile) to reset it.

3) Restart the GlassFish domain server

Restart the GlassFish domain server and any other server instances you might have.

/u01/app/glassfish/bin/asadmin stop-local-instance
/u01/app/glassfish/bin/asadmin stop-domain domain1

/u01/app/glassfish/bin/asadmin start-domain domain1
/u01/app/glassfish/bin/asadmin start-local-instance

 

HTH,

Matthias