1 Reply Latest reply on Dec 9, 2010 3:47 AM by JoeBidgood

    Not able to login to EPO

    krmason

      Hi,

       

      when I try to login I get the following errors:

       

      DataChannel - Dependency scheduler had initialization error
      AvertAlerts - Dependency scheduler had initialization error
      VSEMAS850000 - Dependency VIRUSCAN8600 had initialization error
      SPAMKILR2100 - Dependency EPOCore had initialization error
      issue - Dependency rs had initialization error
      VIRUSCANREPORTS - Dependency CommonEvents had initialization error
      Notifications - Dependency response had initialization error
      rsd - Dependency Notifications had initialization error
      remote - Dependency core had initialization error
      epolicensing - Dependency console had initialization error
      epoMigration - Dependency AgentMgmt had initialization error
      Countermeasures - Dependency ComputerMgmt had initialization error
      EPOCore - Dependency ldap had initialization error
      SITEADVMETA - Dependency ComputerMgmt had initialization error
      response - Dependency scheduler had initialization error
      help - Dependency core had initialization error
      aramid - Dependency CommonEvents had initialization erro

       

      Does this mean I have to rebuild the EPO server?

       

      Ken Mason

        • 1. Re: Not able to login to EPO
          JoeBidgood

          This sort of string of errors is usually an indication that ePO can't talk to its SQL database. Before anything else, check that the SQL server is running, the DB is availabel, and that the credentials specified in ePO's config page are correct. (This sort of error is quite common when the account used by ePO to access SQL has its password changed - it needs to be updated in the config page.)  Also check the orion.log for any errors.

           

          Rebuilding should hopefully not be necessary

           

          HTH -

           

          Joe