05-03-2022 12:50 PM - edited 05-03-2022 12:57 PM
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
Solved! Go to Solution.
08-02-2022 12:10 PM
I wanted to update the thread we were finally able to resolve the issue. We performed the following steps:
The domain selections reappeared and authentication to the Web UI was successful
Thank you to all who responded, and hopefully, this may help someone out in the future.
05-04-2022 03:39 AM
Once I was in the same situation and the whole OS reboot resolved this.
Michal
05-04-2022 04:40 AM
Thank you, Michal, but I have tried server reboots and it hasn't resolved the issue. Thanks.
05-04-2022 06:26 AM
Then I recommend you to test another/newer version of browser and if it wont help, open a support ticket.
05-04-2022 06:28 AM
Hi Michal,
Yes, I've tested a different browser locally and remotely as well and have a support ticket open as well. Thanks for the suggestions.
05-04-2022 08:16 AM
What version did you upgrade from?
05-04-2022 08:18 AM
I upgraded from v9.1.0.1 to v10.
05-04-2022 09:45 AM
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.
05-04-2022 10:10 AM
Hi Krutons,
Thank you - yes, I checked that as well and 8.3 naming convention is enabled. I forgot to list that it my troubleshooting steps so I appreciate the thought.
05-04-2022 10:31 AM - edited 05-04-2022 10:33 AM
So are you able to see the default domain, OpsCenterUsers(vx)? or it is entirely blank? Also, when you are logged into your master, do you see any issues with the OpsCenter server.
05-04-2022 10:34 AM
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?
05-04-2022 10:38 AM - edited 05-04-2022 10:38 AM
I'm unable to verify atm but if you looked at host properties -> master -> servers -> opscenter tab, it would show a green/red/yellow yellow circle I think.
05-04-2022 11:04 AM
Oh right, it is a yellow circle at the moment.
05-04-2022 04:38 PM
Hi @new2nbu
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?
Cheers
David
05-05-2022 05:28 AM
Hi David,
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.
05-05-2022 11:17 AM
i faced the same issue when upgraded from 8.2 to 9.1
this is what support did:
Solution
1. Rename the existing jkskey file:
From: <INSTALL_PATH>\Symantec\OpsCenter\gui\config\jkskey
To: <INSTALL_PATH>\Symantec\OpsCenter\gui\config\jkskey_orig
2. Rename the existing keystore:
From: <INSTALL_PATH>\Symantec\OpsCenter\gui\Security\keystore
To: <INSTALL_PATH>\Symantec\OpsCenter\gui\Security\keystore_orig
3. Generate a new keystore and jkskey file by executing the createSSLStore.cmd command
<INSTALL_PATH>\Symantec\OpsCenter\gui\bin\goodies\creatSSLStore.cmd
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:
<INSTALL_PATH>\Symantec\OpsCenter\gui\webserver\conf\server.xml
• Search for 'keystorePass' without the quotes.
• Make sure that keystorePass= is set to what's in the jkskey file just created
<INSTALL_PATH>\Symantec\OpsCenter\gui\config\jkskey
5. Restart OpsCenter services:
<INSTALL_PATH>\Symantec\OpsCenter\server\bin\opsadmin stop
<INSTALL_PATH>\Symantec\OpsCenter\server\bin\opsadmin start
once this works, you can go back to installing custom SSL for fixing warnign window
05-05-2022 03:12 PM
08-02-2022 12:10 PM
I wanted to update the thread we were finally able to resolve the issue. We performed the following steps:
The domain selections reappeared and authentication to the Web UI was successful
Thank you to all who responded, and hopefully, this may help someone out in the future.