3 Replies Latest reply on Jul 16, 2014 1:18 AM by mattbald

    ePO server moved to AD domain - unable to login

    mattbald

      Environment:

      Win 2008 R2 SP1 (Virtual Machine)

      ePO 5.1

       

      We have recently moved our environment from Novell eDirectory to MS Active Dir and after the EPO server was moved to the AD domain (Meaning we are now logged into the server as the same user name, but a different account and profile) we are no longer able to login to the web portal.

       

      The login screen comes up with  the login box, plus the errors below:

       

      DataChannel - Dependent plugin EPOCore failed with initialization error                                
      LYNXSHLDPARSER - Dependent plugin EPOCore failed with initialization error                                
      AvertAlerts - Dependent plugin CommonEvents failed with initialization error                                
      EPOAGENTMETA - Dependent plugin DataChannel failed with initialization error                                
      TELEMTRY1000 - Dependent plugin RepositoryMgmt failed with initialization error                                
      VIRUSCANREPORTS - Dependent plugin CommonEvents failed with initialization error                                
      Notifications - Dependent plugin CommonEvents failed with initialization error
      SoftwareMgmt - Dependent plugin RepositoryMgmt failed with initialization error                                
      Countermeasures - Dependent plugin ComputerMgmt failed with initialization error                                
      epoMigration - Dependent plugin SoftwareMgmt failed with initialization error                                
      ComputerMgmt - Dependent plugin epoLicEnt failed with initialization error                                
      EPOCore - com.mcafee.epo.core.ServerNative.getFipsModeNative()I                                 
      VIRUSCAN8800 - Dependent plugin ComputerMgmt failed with initialization error                                
      PolicyMgmt - Dependent plugin RepositoryMgmt failed with initialization error                                
      ProductDeployment - Dependent plugin ComputerMgmt failed with initialization error                                
      LYNXSHLD1900 - Dependent plugin EPOCore failed with initialization error                                
      AgentMgmt - Dependent plugin RepositoryMgmt failed with initialization error                                
      PostInstallXP - Dependent plugin ProductDeployment failed with initialization error                                
      RepositoryMgmt - Dependent plugin epoLicEnt failed with initialization error                                
      epoLicEnt - Dependent plugin EPOCore failed with initialization error                                
      InstallHelper - Dependent plugin EPOCore failed with initialization error                                
      CommonEvents - Dependent plugin ComputerMgmt failed with initialization error                                
      SIARevocation - Dependent plugin RepositoryMgmt failed with initialization error

       

       

      We can then login but nothing is loaded correctly, as per attached (1).

       

       

      I have checked a bunch of other similar issues and they have mostly suggested checking the SQL connection by going to https://localhost:8443/core/config-auth and updating the details, but this hasn't made any difference for us.  When we go to that page it comes up with the same errors and then after you enter the login details it goes to the config page.

       

      I have also seen a few people talk about issues with extensions being the cause and when I go to the extensions page, I get a message like tthe one attached (2) for all of the extensions except Help and Shared Components:

       

       

      I have restarted the server and attached the last bit of the orion.log in case that helps.

       

      As we are running EPO as a VM, are we able to just roll back to the latest backup of the machine?  I saw soemwhere that this may cause issues if the DB isn't backed up at the same time, but our DB is fairly static, so hopefully this won't cause any issues.

       

      Thanks in advance for any help and let em know if you need anymore ifno to sort out our issues

       

      Message was edited by: mattbald on 7/14/14 7:24:47 PM CDT

       

      Message was edited by: mattbald on 7/14/14 7:29:12 PM CDT
        • 1. Re: ePO server moved to AD domain - unable to login
          Laszlo G

          It looks like ePO cannot still connect to its database, that's why you get all the extension errors and no results on the queries.

           

          If you go to https://localhost:8443/core/config-auth, then write down again domain, username and pasword and you click on the test button it should tell if it can connect or not to the database.

           

          If it can conncet then you should save settings and reboot ePO server to chechk if errors still appear or not

          1 of 1 people found this helpful
          • 2. Re: ePO server moved to AD domain - unable to login
            mattbald

            I have already done that a fewtime, but for the sake of thouroughness I have done it again.

             

            Went to the address, confirmed all details, click Test Connection (which succeeded), then clicked Apply and then restarted the server.

             

            It made no difference to the messages we see on the EPO login screen.

             

             

             

            I noticed that the EventParser was not started and wouldn't start manually either.  I checked the log file and saw the below entries at the server startup.

             

            20140716141549   I    #02616    EVNTPRSR   Initializing Server...

            20140716141549   I    #02616    EVNTPRSR   Database initialization: Starting.

            20140716141549   I    #02616    MFEFIPS    Loading: "C:\PROGRA~2\McAfee\EPOLIC~1", Role = Officer, Mode = Normal

            20140716141549   I    #02616    MFEFIPS     UsingRandom Generator: HMAC Random

            20140716141549   I    #02616    MFEFIPS     ModuleInitialized.

            20140716141549   I    #02616    MFEFIPS    MFEFIPS_Status() returned 1

            20140716141549   I    #02616    MFEFIPS    Loading: "C:\PROGRA~2\McAfee\EPOLIC~1", Role = Officer, Mode = Normal

            20140716141549   I    #02616    MFEFIPS     ModuleInitialized.

            20140716141549   I    #02616    MFEFIPS    MFEFIPS_Status() returned 1

            20140716141549   I    #02616    EPODAL      UsingSSPI/NTLM Authentication for [svrname\EPOSERVER,49239].[SQL_DB_NAME]

            20140716141620   E    #02616    EPODAL     ePOData_Connection.cpp(575): COM Error 0x80004005, source=Microsoft OLE DBProvider for SQL Server, desc=[DBNETLIB][ConnectionOpen (Connect()).]SQL Serverdoes not exist or access denied., msg=Unspecified error

            20140716141620   E    #02616    EPODAL     ePOData_Connection.cpp(593): COM Error 0x80004005, source=Microsoft OLE DBProvider for SQL Server, desc=[DBNETLIB][ConnectionOpen (Connect()).]SQL Serverdoes not exist or access denied., msg=Unspecified error

            20140716141620   E    #02616    EPODAL     ePOData_Connection.cpp(668): COM Error 0x80004005, source=Microsoft OLE DBProvider for SQL Server, desc=[DBNETLIB][ConnectionOpen (Connect()).]SQL Serverdoes not exist or access denied., msg=Unspecified error

            20140716141620   E    #02616    EPODAL     ePOData_Connection.cpp(343): COM Error 0x80004005, source=Microsoft OLE DBProvider for SQL Server, desc=[DBNETLIB][ConnectionOpen (Connect()).]SQL Serverdoes not exist or access denied., msg=Unspecified error

            20140716141652   E    #02616    EPODAL     ePOData_Connection.cpp(575): COM Error 0x80004005, source=Microsoft OLE DBProvider for SQL Server, desc=[DBNETLIB][ConnectionOpen (Connect()).]SQL Serverdoes not exist or access denied., msg=Unspecified error

            20140716141652   E    #02616    EPODAL     ePOData_Connection.cpp(593): COM Error 0x80004005, source=Microsoft OLE DBProvider for SQL Server, desc=[DBNETLIB][ConnectionOpen (Connect()).]SQL Serverdoes not exist or access denied., msg=Unspecified error

            20140716141652   E    #02616    EPODAL     ePOData_Connection.cpp(668): COM Error 0x80004005, source=Microsoft OLE DBProvider for SQL Server, desc=[DBNETLIB][ConnectionOpen (Connect()).]SQL Serverdoes not exist or access denied., msg=Unspecified error

            20140716141652   E    #02616    EPODAL     ePOData_Connection.cpp(343): COM Error 0x80004005, source=Microsoft OLE DBProvider for SQL Server, desc=[DBNETLIB][ConnectionOpen (Connect()).]SQL Serverdoes not exist or access denied., msg=Unspecified error

            20140716141652   E    #02616    EPODAL     ePOData_Connection.cpp(368): Error 0x80004005 returned from credentialscallback. Database NOT available

            20140716141652   E    #02616    EVNTPRSR   D:\EPO1\BUILD\epo\dev\src\server\include\ePOData.inl(404): Databaseinitialization: Failed (hr=0x80004005).

            20140716141652   E    #02616    EVNTPRSR   source\servinit.cpp(222): Failed to initialize database layer. Cannot continue.

            20140716141652   I    #02616    EVNTPRSR   EventParser Stopped.

            20140716141652   I    #02616    EVNTPRSR   Cleaning up Server...

             

             

            By the looks of it, it can’tactually connect to the SQL DB, even though the test was successful.

             

            I don’t get how/why the test is successful, but the service doesn’t start causing EPO to be broken…  Hopefully someone can explain how/why coz Iam confused….

             

            Does the user account that we use to connect  eed any special rights to the DB?  They are set to db_owner.

             


             

            Message was edited by: mattbald on 7/16/14 12:40:51 AM CDT
            • 3. Re: ePO server moved to AD domain - unable to login
              mattbald

              I have found the answer!!

               

              It was a port conflict issue.  In case anyone else stumbles across this in the future, I used the KB article at  https://kc.mcafee.com/corporate/index?page=content&id=KB53935 to find the port details and fix it up.

               

              Thanks for your help and time Laszlo.