1. Java Version 7 Update 51 32 Bit Download
2. Java Version 7 Update 51 32 Bit

I'm unable to pass below rule while installing SQL Server 2017 Developer edition on windows 10 machine on Feature Rules screen:

• Oracle JRE 7 Update 51 (64-bit) or higher is required for Polybase

I'm getting below error:

This computer does not have the Oracle Java SE Runtime Environment Version 7 Update 51 (64-bit) or higher installed. The Oracle Java SE Runtime Environment is software provided by a third party. Microsoft grants you no rights for such third-party software. You are responsible for and must separately locate, read and accept applicable third-party license terms. To continue, download the Oracle SE Java Runtime Environment from https://go.microsoft.com/fwlink/?LinkId=526030.

I've sufficiently high Java version (9.x) installed on my machine. I ran the command java -XshowSettings:properties -version which gives below details related to Java installation on my box:

Download Java JDK 7 Update 51 (64-bit) for Windows PC from FileHorse. 100% Safe and Secure Free Download 64-bit Software Version.

Not sure what else this installer is looking for. Has anyone else faced this error? One obvious solution is to skip PolyBase Query Service for External Data feature i.e. unselect it on Feature Selection screen but I don't want to do that. I want to resolve this issue as to why it is still interrupting the installation when my machine configuration is meeting all the prerequisites?

RBTRBT

Java 7 update 51 free download - Java Update for Mac OS X 10.3.9, Apple Java for OS X 10.7/10.8, Adobe Photoshop 7.0.1 update, and many more programs. This page is your source to download or update your existing Java Runtime Environment (JRE, Java Runtime), also known as the Java plug-in (plugin), Java Virtual Machine (JVM, VM, and Java VM).

6 Answers

INTRODUCTION:

Java Version 7 Update 51 32 Bit Download

I had the same exact issue, took me forever to fix it. I started with the latest versions of Java (available here: http://www.oracle.com/technetwork/java/javase/downloads/index.html) and installed JRE, JRE Server, and JDK; first separately and then altogether following the instructions here: https://docs.oracle.com/javase/9/install/installation-jdk-and-jre-microsoft-windows-platforms.htm#JSJIG-GUID-A7E27B90-A28D-4237-9383-A58B416071CA) but kept getting the same error message.

SOLUTION:

1. Uninstalled all three Java 9s that I had installed on my Windows 10
2. Deleted all Java paths in the Environment Variables (located in the System Properties, Advanced Tab); find it easily by searching for env after opening the start menu and choose 'Edit the System Environment Variable' in the search results
   • In the System Properties/Advanced, select the 'Path' variable in the 'System Variables' and delete all Java paths within that variable.
3. Restarted my PC and downloaded JRE 7 (jre-7u80-windows-x64.exe) from this path: http://www.oracle.com/technetwork/java/javase/downloads/java-archive-downloads-javase7-521261.html
4. Ran the exe file and after finishing the installation, went back to the System Properties and added the new Java location to the path. You should add the location of the bin folder; in my computer, it was: C:program filesjavajre7bin
5. I also enabled the Java Access Bridge. Java Installation Guide: 'By default, the Java Access Bridge is disabled. To enable it, run the following command (where %JRE_HOME% is the directory of your JRE): %JRE_HOME%binjabswitch -enable'
6. Restarted my system again
7. Easily installed the PolyBase.

Then after that I reupdated my Java to 9.Hope this helps your situation as well!

I fully explained the root cause and provided a registry edit workaround in an article I published in early December 2017. The problem is the same in SQL Server 2016 and 2017 as mentioned in the article here.

Java Version 7 Update 51 32 Bit

The quick summary is that Oracle changed the registry key structure after version 8 of the JRE. The SQL Server 2016 and 2017 installers look for the JRE version 7 registry key names found at and below: HKEY_LOCAL_MACHINESOFTWAREJavaSoftJava Runtime Environment

Let's say you want to use JRE version 9 and you don't want to install JRE version 7. You'll have to export the JRE 9 version keys found at HKEY_LOCAL_MACHINESOFTWAREJavaSoftJRE and edit them to make the key names match the JRE 7. There are three keys to rename. Import the edited keys. That way the installer will find version 7 key names that are pointing to JRE 9 locations.

Quoting from the part of the article about editing key names:

You want to replace all occurrences of JRE with Java Runtime Environment. You must not alter the lowercase jre references.

For example, change HKEY_LOCAL_MACHINESOFTWAREJavaSoftJRE to HKEY_LOCAL_MACHINESOFTWAREJavaSoftJava Runtime Environment

RBT

I tried to install SQL Server 2017, with PolyBase included. No solution worked for me except installing JRE 8.144

FLICKERFLICKER

Warning: This is a registry fix so try it at your own risk !

Situation: I already had JDK installed which was much higher that version required in the setup.

Looking at the installation logs I found this:

Solution: Go to registry editor. Create the key 'Java Runtime Environment' and replicate everything under the following key:

Once that's done, running the scan should succeed.

RBT

I had this problem just today and I've been looking for a solution for the last 5 hours, but I really did find it here but there is kind of 'bad way to give the solution'

Basically the solution is to go to the registery editor (Open run and type regedit) and go to the third choice which is 'HKEY_LOCAL_MACHINE' and >SOFTWARE>JAVASOFT>JRE you will find the file named JRE just change the name to 'Java Runtime Environment' !! And thats basically it because the SQL server installation problem is that it didnt find the folder with the name 'Java Runtime Environment' instead it found JRE which is just a shortcut and that shortcut Came with the last updates 5 and higher thats why u get an error when u download and install the JRE 5 or higher!

RBT

John Paul Cooks answer above and backing article worked perfectly for JDK 11 and SQL 2017

I added this comment to show specific JDK 11 values – the process has not changed.

JDK 11 – Simple Registry Trick Works for SQL 2017

1: Export the JDK Key from Registry HKEY_LOCAL_MACHINESOFTWAREJavaSoftJDK

2: In Text .reg File that was exported Replace the Key Name Part JDK with Java Runtime Environment. Just the Key Name – not anywhere else the text JDK is used like in values.

3: Import to the Registry the .Reg File You just edited.Now you have the real JDK key and a Copy of the JDK key with all its values. This second new JDK Key is named “Java Runtime Environment” instead of JDK.

The real Key JDK is left alone. The second Key called Java Runtime Environment is there to let SQL Server do the Install. The second new key has the exact same item values as the JDK key for each SubKey - it is only the name of the JDK key that changed.

Not the answer you're looking for? Browse other questions tagged sql-serverinstallationsql-server-2017 or ask your own question.