8 Replies Latest reply on Jan 17, 2011 5:05 AM by babiyan

    Can't Log in to EPO 4.5 Console - errors - urgent!

      We recently did a fresh install of epo 4.5 and created a new database on our sql server.

       

      Everything was working great as of Monday around 10am, which was the last confirmed successfull login. Sometime between that time and 8am on Wed (today) something broke and I can no longer log in to the EPO console.

       

      I can connect to the database successfully from the core/config page.
      I have restarted the services multiple times.

      The dropdown box for Language on the login screen is empty (normally displays "english")

       

      Anyone have any ideas???

       

       

      These errors show on the login screen:

      -------------------------------------------------------

      DataChannel - Dependency scheduler had initialization  error
      LYNXSHLD1510 - Dependency EPOCore had initialization  error
      AvertAlerts - Dependency scheduler had initialization  error
      LYNXSHLDPARSER - Dependency core had initialization  error
      GSD7REPORTS - Dependency core had initialization error
      VSEMAS850000 - Dependency VIRUSCAN8600 had  initialization error
      issue - Dependency rs had initialization error
      VIRUSCANREPORTS - Dependency CommonEvents had  initialization error
      rsd - Dependency Notifications had initialization  error
      GSE7REPORTS - Dependency GROUPSHD7000 had  initialization error
      Notifications - Dependency response had initialization  error
      VSCANMAC8610 - Dependency ComputerMgmt had  initialization error
      VIREXREPORTS - Dependency core had initialization  error
      remote - Dependency core had initialization error
      SITEADV_1500 - Dependency EPOCore 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
      SMDWIN__7000 - Dependency ComputerMgmt had  initialization error
      aramid - Dependency CommonEvents had initialization  error
      AgentMgmt - Dependency RepositoryMgmt had  initialization error
      GROUPSHD7000 - Dependency ComputerMgmt had  initialization error
      InstallHelper - Dependency core had initialization  error
      EPOAGENTMETA - Dependency ComputerMgmt had  initialization error
      scheduler - Dependency console had initialization  error
      ComputerMgmt - Dependency ldap had initialization  error
      PolicyMgmt - Dependency ComputerMgmt had  initialization error
      VIRUSCAN8700 - Dependency EPOCore had initialization  error
      VSEMAS870000 - Dependency VIRUSCAN8700 had  initialization error
      console - Dependency core had initialization error
      ldap - Dependency rs had initialization error
      VIRUSCAN8600 - Dependency EPOCore had initialization  error
      rs - Dependency console had initialization error
      RepositoryMgmt - Dependency ComputerMgmt had  initialization error
      core - Error creating bean with name  'core.ext.taskGlobals' defined in URL [jndi:/localhost/core/WEB-INF/beans.xml]:  Invocation of init method failed; nested exception is  java.lang.IllegalStateException: The following extensions are in a partially  installed state: [epo_help:450.399, ePO_Help:]
      CommonEvents - Dependency ComputerMgmt had  initialization error