2 Replies Latest reply on Jul 23, 2014 10:30 AM by ansarias

    Error Console EPO 4.5


      Hi everyone,


      I have a EPO 4.5, when I try to log on console. Errors are displayed:


      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


      The configuration file db.properties - ok

      The user name and password - ok


      I use Windows Server 2003 - SP2


      (sorry, my english is horrible)




      Message was edited by: delepa on 7/22/14 7:58:57 AM CDT
        • 1. Re: Error Console EPO 4.5



          Firstly - it's important to point out that ePO 4.5 is end-of-life, and you should definitely think about upgrading to a supported version.


          This type of error is almost always caused by a problem accessing the DB. In the information you have provided, it appears that ePO is configured to access SQL using an account called epoadmin  - but it also looks like epoadmin is an ePO account.

          Are you sure that there is an SQL account called epoadmin with the correct permissions?

          What happens if you try using the sa account, or a domain admin account, in the Configure Database Settings page?


          HTH -



          • 2. Re: Error Console EPO 4.5



            Select all in ePO login page and paste into notepad and check at last it will give you exact error message.

            Issue seems missing some .xml files in ePO installation directory which is in Catlina folder. Compare current extensions (Program Files\McAfee\ePolicy Orchestrator\Server\conf) with respective .xml file (Catlina folder). And check which are missing.

            You can create missing .xml files by copying existing other .xml with editing.


            This error occurs when there was a focereboot happen to your ePO server.



            Aslam Ansari