OnCommand System Manager 3.1.2 died after Java-update
2016-03-18 10:12 AM
We're running Oncommand System Manager 3.1.2 with Windows 2008-server. After we updated Java to 188.8.131.52, 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.
2 REPLIES 2