I recently just upgraded to OpsCenter v10. The upgrade was successful and all services are started. However, when launching OpsCenter the UI displays a message "Error occurred while connecting to the OpsCenter Server. Please ensure that the server is running." AND the Domain drop down is empty. Looking at previous KB and support articles I've done the following .. any help is appreciated:
I appreciate any help.. Thank you
Could be a long shot but I do remember there being an issue with 8.3 naming convention in windows being disabled. I'd just verify that is enabled. Should be able to open CMD and type this fsutil 8dot3name query C:\ or whatever path you have installed OpsCenter on.
The entire Domain dropdown is blank and nothing is listed including the OpsCenterusers. Not sure I follow in reference when I'm logged into my mater do I see any issues with OpsCenter server -- how can I verify that?
I don't believe that the dot on the OpsCenter server changes color in host properties ever changes color (it is yellow on a test system I have and everything is running fine).
The issue you are having is with the authentication services not initialising correctly. It has nothing to do with your browser or the connection to the master server (which may well be working even though you can't log in to check).
I'd let support help you here - although what steps did you do after the upgrade to revert your custom certificate and are you sure you did this correctly?
Thank you for the reply. Support unfortunately is a bit "stumped" and they think it's an issue with the custom SSL certificate that is applied to OpsCenter. After the upgrade, I edit the server.xml file in <PF>\Symantec\OpsCenter\gui\webserver\conf and edit the keystone file path and password entries. I then replace the keystone and custom .jks files located in <PF>\Symantec\Opscenter\gui\security. I then restart OpsCenter services and the custom SSL certificate is re-applied.
i faced the same issue when upgraded from 8.2 to 9.1
this is what support did:
1. Rename the existing jkskey file:
2. Rename the existing keystore:
3. Generate a new keystore and jkskey file by executing the createSSLStore.cmd command
4. Ensure the keystorePass= entry in the server.xml file matches what is in the newly created jkskey file
• Open the server.xml file for editing as an Administrator:
• Search for 'keystorePass' without the quotes.
• Make sure that keystorePass= is set to what's in the jkskey file just created
5. Restart OpsCenter services:
once this works, you can go back to installing custom SSL for fixing warnign window