Subscribe

OnCommand System Manager 3.1.2 died after Java-update

[ Edited ]

Hi!

 

We're running  Oncommand System Manager 3.1.2 with Windows 2008-server. After we updated Java to 1.8.0.73, systemmanager.exe doesn't start. If I execute the Java-applet either from command line or from GUI, it starts but it's unable to connect to the clusters claiming Error 500 Connections refused. It seems that it thinks that TLS is not enabled which not the case. SM is configured to use Firefox and we're running version 44.0.2.

 

Rgds, MiikaP

Re: OnCommand System Manager 3.1.2 died after Java-update

Uninstall java 7.

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

Re: OnCommand System Manager 3.1.2 died after Java-update

1- putty(ssh)  into each controller

2-  run "options tls.enable on"