2 Replies Latest reply on Feb 1, 2010 10:41 AM by zuffy

    ePO can't connect to SQL server

      I have ePO 4.5 in server 1 and SQL 2005 Standard in server 2. Yesterday, when I tried to login, I got an error that said it can't communicate with the SQL server. I checked the SQL server and all the services are running. I rebooted the SQL server but that didn't help. Next, I rebooted the ePO server and that didn't help. After the reboot, I am getting these errors below the login screen:

       

       

      DataChannel - Dependency scheduler had initialization error
      AvertAlerts - Dependency scheduler had initialization error
      VSEMAS850000 - Dependency VIRUSCAN8600 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
      response - Dependency scheduler had initialization error
      help - Dependency core had initialization error
      aramid - Dependency CommonEvents had initialization error
      AgentMgmt - Dependency RepositoryMgmt 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
      RepositoryMgmt - Dependency ComputerMgmt had initialization error
      rs - Dependency console had initialization error
      core - Error creating bean with name 'core.db' defined in URL [jndi:/localhost/core/WEB-INF/beans.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [com.mcafee.orion.core.db.base.Database]: Constructor threw exception; nested exception is java.sql.SQLException: Unable to get information from SQL Server: USNY01DBS007.
      CommonEvents - Dependency ComputerMgmt had initialization error

      I went to the config page and confirmed that the DB name, SQL server name, port are all correct. Confirmed that the service account is not locked. I type in the password and test connection but I get a failed. Any idea what can cause this? So far, McAfee support is useless. I uploaded the 207MB MER log with their MER client but he said the file is 100k. Provided a FTP site but I have no access to upload to it.

       

       

      Message was edited by: zuffy on 1/27/10 11:43:30 AM CST