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
If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.
(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.
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 😞