Forum Discussion

new2nbu's avatar
new2nbu
Level 4
3 years ago

Error occurred while connecting to the OpsCenter Server and Domain is empty

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:

  • Windows Host File has short name and long name with correct IP address listed
  • Services have been stopped & started and are running 
  • The vxatd.log statues .. the last couple lines say (server.cpp:1806) Not able to fetch UseStateMachine flag value and (server.cpp:1823) found UseCACertForTLA = [0]      --- but I'm not sure what this could indicate
  • I do have a custom SSL certificate and I verified server.xml, keystore, & .jks file are all present and configured right
  • In the PF\Symantec\OpsCenter\server\logs -- the latest log directory - I see lines that have "OpenSection failed. sub_section = OpsCenterServices@servername.pit.sap.corp"  however that "pit.sap.corp" is the incorrect domain suffix.  I don't know where that is reading from?

I appreciate any help.. Thank you

 

Windows Server 2016
  • new2nbu's avatar
    new2nbu
    3 years ago

    I wanted to update the thread we were finally able to resolve the issue.  We performed the following steps:

    • Upgraded to OpsCenter v10 (although not mandatory) however because it's the last release we decided to upgrade to the latest supported version
    • Manually moved the custom keystore file back into place and updated server.xml file to reflect correct keystore password.  
    • Reset OpsCenter authentication (AT) with :
      • OpsCenter_Install\server\bin\stopAt
      • OpsCenter_Intstall\server\bin\configureAt
      • OpsCenter_install\server\bin\StartAT
    • Restarted OpsCenter services with opsadmin.bat stop/start

    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.

  • Azhar4's avatar
    Azhar4
    Level 4
    3 years ago

    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

    • davidmoline's avatar
      davidmoline
      Level 6
      3 years ago

      Hi new2nbu 

      I'd be looking to do something like what Azhar4 is suggesting or revert back to the certificates in place immediately after the upgrade (hopefully you have these backed up somewhere). Then assuming OpsCenter works correctly re-do the custom SSL certificate steps.

      David

  • new2nbu's avatar
    new2nbu
    Level 4
    3 years ago

    I wanted to update the thread we were finally able to resolve the issue.  We performed the following steps:

    • Upgraded to OpsCenter v10 (although not mandatory) however because it's the last release we decided to upgrade to the latest supported version
    • Manually moved the custom keystore file back into place and updated server.xml file to reflect correct keystore password.  
    • Reset OpsCenter authentication (AT) with :
      • OpsCenter_Install\server\bin\stopAt
      • OpsCenter_Intstall\server\bin\configureAt
      • OpsCenter_install\server\bin\StartAT
    • Restarted OpsCenter services with opsadmin.bat stop/start

    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.

    • new2nbu's avatar
      new2nbu
      Level 4
      3 years ago

      Thank you, Michal, but I have tried server reboots and it hasn't resolved the issue.  Thanks.

  • Michal_Mikulik1's avatar
    Michal_Mikulik1
    Moderator
    3 years ago

    Then I recommend you to test another/newer version of browser and if it wont help, open a support ticket.

  • new2nbu's avatar
    new2nbu
    Level 4
    3 years ago

    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.

  • Krutons's avatar
    Krutons
    Moderator
    3 years ago

    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.

    • new2nbu's avatar
      new2nbu
      Level 4
      3 years ago

      Oh right, it is a yellow circle at the moment.

      • davidmoline's avatar
        davidmoline
        Level 6
        3 years ago

        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  

  • new2nbu's avatar
    new2nbu
    Level 4
    3 years ago

    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.