4 Replies Latest reply on Apr 15, 2013 10:06 AM by rackroyd

    ePO login page problem

      we are facing login problem in ePO console page every day. Mcafee support has checked. but the problem happend again today. the Case id 3-2985644795.

       

      kindly do the needful.

       

      Regards,

       

      Raamkumar.

        • 1. Re: ePO login page problem
          Tristan

          Usually a result of one or more of the McAfee services not running on the ePO server.

           

          Make sure

           

          McAfee ePolicy Orchestrator 4.X.X Application Server

          McAfee ePolicy Orchestrator 4.X.X Event Parser

          McAfee ePolicy Orchestrator 4.X.X Server

           

          and database service

           

          SQL Server (EPOSERVER)

           

          are all in a running state

          • 2. Re: ePO login page problem
            kmcin11

            Hi Arkey,

             

            Mark the red text with your mouse and drag it all the way down. In the very end of the text, you will see the actual error description. It is possible that the database is not accessible to ePO at the moment, that is what I usually see. I have set the ePO services to delay their start in order for the SQL services to come up before ePO attempts to connect to the database.

             

            K

            • 3. Re: ePO login page problem
              alexn

              Arkey,

               

              https://172.16.48.60:8443/core/config

               

               

              Check DB connection and report back.

              • 4. Re: ePO login page problem
                rackroyd

                Hi,

                 

                With these errors please refer to McAfee support article:

                KB51670 - Unable to log on to the ePO 4.x console (Troubleshooting - Master Article) 

                 

                What you have looks an exact match to KB69850.

                 

                As everyone is suggesting, most common cause for this is Sql connection failure somewhere along the line.

                Often an unexpected Sql password change.