Data Infrastructure Management Software Discussions

Highlighted

OnCommand System Manager 3.1.1 doesn't tolerate Java 8 Existence

Per a Java.com recommendation, I upgraded to the java 8 jre for Windows this morning.  Afterwards, System Manager gave errors that it could not authenticate securley.  

 

After uninstalling java 8, functionality was restored.

 

Any ideas on how to force System Manager to use the java 7 client w/ the java 8 client installed as well?

26 REPLIES 26
Highlighted

Re: OnCommand System Manager 3.1.1 doesn't tolerate Java 8 Existence

Hello bsnyder27,

 

could you find a solution for this? We are having the same problem now.

 

 

Highlighted

Re: OnCommand System Manager 3.1.1 doesn't tolerate Java 8 Existence

Only to uninstall java 8 and go back to the latest release of java 7.  

 

 

 

Highlighted

Re: OnCommand System Manager 3.1.1 doesn't tolerate Java 8 Existence

Remove Java 8.x and then revert to the version of Java that was working before the update to 8.x. If you are unsure what version was being run before the update, download Java 7u45 64bit, or 7u65 64bit.

Future instances of OnCommand System Manager are expected to function with Java 8.x.

If issue exists even after reverting to Java 7u65 64bit or 7u45 64bit, perform a manual uninstallation.

 1. Uninstall all Java versions listed in Control Panel/Program and Features.
 2. Make a backup of registry key HKEY_LOCAL_MACHINE\SOFTWARE\Javasoft.
 3. Delete the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Javasoft and all of its subkeys.
 4. Rename Java folder to Java.bak inside both %ProgramFiles% and/or %ProgramFiles(x86)%.
 5. Download and Install either Java 7u65 64bit or 7u45 64bit here.
 6. If launching OnCommand System Manager is successful, remove backups made in steps 2 and 4

 

Thanks

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

Highlighted

Re: OnCommand System Manager 3.1.1 doesn't tolerate Java 8 Existence

If you run it using the .jar file instead of the .exe file it will work using Java 8.

 

"C:\Program Files\NetApp\OnCommand System Manager\SystemManager.jar"

Highlighted

Re: OnCommand System Manager 3.1.1 doesn't tolerate Java 8 Existence

Didn't work for me though.

 

Anybody namaged to find a final solution ?

Highlighted

Re: OnCommand System Manager 3.1.1 doesn't tolerate Java 8 Existence

Hello

You can use the last version of System manager 3.1.2RC1 , it works fine with java 8

But beware, version 3.1.2RC1 doesn't work with java 7

 

Highlighted

Re: OnCommand System Manager 3.1.1 doesn't tolerate Java 8 Existence

Other Java programs detect which JVMs are installed, display a list and allow the selection of the JVM to be used.
Highlighted

Re: OnCommand System Manager 3.1.1 doesn't tolerate Java 8 Existence

I'm attempting to install 3.1.2RC1 and I'm getting the error that it requires Java 7.  Are we sure 3.1.2RC1 uses Java 8?

Highlighted

Re: OnCommand System Manager 3.1.1 doesn't tolerate Java 8 Existence

 

I tried 3.1.2RC1 with Java 8 and it didn't work.

Highlighted

Re: OnCommand System Manager 3.1.1 doesn't tolerate Java 8 Existence

Dear All,

 

For me here , the only way I found to get it back working was:

 

1 - Unsinstall all Java versions installed in my computer.

2 - Uninstall OnCommand

3 - Delete the Reg key related to Java ( mentioned in the post here above)

4 - Delete the Netapp folder created during OnCommand Installation

5 - Restart computer

6 - Reinstall Java JRE 7 x64

7 - Reintall OnCommand 3.1.1

 

 

Any other sequence listed in any of the posts here didn't work.

Please let us know if it this sequence of actions worked for you too.

 

Regards,

Jan

Highlighted

Re: OnCommand System Manager 3.1.1 doesn't tolerate Java 8 Existence

The following worked for me with 3.1.2...

 

Put this in the target field under the shortcut tab for the icon.

 

"C:\Program Files\Java\jdk_latest\bin\java.exe" -jar "C:\Program Files (x86)\NetApp\OnCommand System Manager\2.0\SystemManager.jar"

 

You should use the actual path for the 1.8 java.exe and the SystemManager jar as it may be different for you than me.

 

Jim

Highlighted

Re: OnCommand System Manager 3.1.1 doesn't tolerate Java 8 Existence

(Clearly you had to already have installed SystemManager before installing Java 1.8, as the install routine itself will fail with Java 1.8. I haven't experimented with trying to get the install routine working...)

 

Netapp needs to get this fixed, as Oracle is about to stop updating Java 7 for security patches.

 

Jim

Highlighted

Re: OnCommand System Manager 3.1.1 doesn't tolerate Java 8 Existence

Uninstalling Java 1.8.31 (32-bit, not sure if 64-bit would work), and reinstalling Java 1.8.31 32-bit worked for me (as of this writing 1.8.31 is the latest).  SysMgr 3.1.1.  I'm on Windows 2008r2 64-bit.  I have no other Java version in this box.

I had to do this after updating DFM (OnCommand Core) because of an Apache vulnerability.

(Yes, it is a pain to do this, but have limited choices 😞

Highlighted

Re: OnCommand System Manager 3.1.1 doesn't tolerate Java 8 Existence

Has it been pointed out that forcing customers to retrograde to unsafe versions of Java is completely unacceptable? Is there an actual fix for this? 

Highlighted

Re: OnCommand System Manager 3.1.1 doesn't tolerate Java 8 Existence

The next version of 3.1.2, targeted for end of March or early April, will officially support Java 8.

Try the NEW Knowledgebase!
NetApp KB Site
Forums