1 Reply Latest reply on Jul 29, 2013 7:44 AM by rackroyd

    EPO 5.0.0 - Can't login to the console, https://ARMOUR:8443

      Hello everyone....

       

      I am new to EPO. the software was installed on to our server couple of months back and was working fine till last wednesday.

      Now when I try to login to the console its not loading. Even the https://ARMOUR:8443/core/config doens't load too.

       

      *services: McAfee EPO 5.0.0 Event Parser is not running, If I start manually it stops with error "some services stop automatically if they are not use by other programs"

       

      I have looked at the logs and they are as follow,

       

      EventParser - Log

       

      20130726220746          I          #00916          EVNTPRSR          Initializing Server...

      20130726220746          I          #00916          EVNTPRSR          Database initialization: Starting.

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

      20130726220747          I          #00916          MFEFIPS           Module Initialized.

      20130726220747          I          #00916          EPODAL            Using SSPI/NTLM Authentication for [ARMOUR\EPOSERVER,59656].[ePO_ARMOUR]

      20130726220747          W          #00916          EPODAL            Login for ARMOUR\Administrator failed. Building profile and retrying.

      20130726220747          E          #00916          PONTUTIL          Failed to create local ePO User Group, push agent aborted!  System error code 1379

      20130726220747          E          #00916          EPODAL            ePOData_Connection.cpp(282): Failed to logon the domain user ARMOUR\Administrator to connect to database.

      20130726220747          E          #00916          EPODAL            ePOData_Connection.cpp(352): Error 0x80070002 returned from credentials callback. Database NOT available

      20130726220747          E          #00916          EVNTPRSR          D:\EPO3\BUILD\epo\dev\src\server\include\ePOData.inl(319): Database initialization: Failed (hr=0x80070002).

      20130726220747          E          #00916          EVNTPRSR          Failed to initialize database layer. Cannot continue.

      20130726220747          I          #00916          EVNTPRSR          EventParser Stopped.

      20130726220747          I          #00916          EVNTPRSR          Cleaning up Server...

       

      Orion - Log

       

      2013-07-26 22:37:52,082 FATAL [main] core.OrionCore   - killing server. reason = Failed to read the server's multi-tenant mode property (is there a multi.tenant.mode record in the OrionServerProperties table?)

      2013-07-26 22:38:01,255 WARN  [main] base.Database    - database startup attempt (1 of 12) failed; sleeping for 10000 milliseconds and will try again...

      2013-07-26 22:38:11,332 WARN  [main] base.Database    - database startup attempt (2 of 12) failed; sleeping for 10000 milliseconds and will try again...

      2013-07-26 22:38:21,394 WARN  [main] base.Database    - database startup attempt (3 of 12) failed; sleeping for 10000 milliseconds and will try again...

      2013-07-26 22:38:31,456 WARN  [main] base.Database    - database startup attempt (4 of 12) failed; sleeping for 10000 milliseconds and will try again...

      2013-07-26 22:38:41,518 WARN  [main] base.Database    - database startup attempt (5 of 12) failed; sleeping for 10000 milliseconds and will try again...

      2013-07-26 22:38:51,580 WARN  [main] base.Database    - database startup attempt (6 of 12) failed; sleeping for 10000 milliseconds and will try again...

      2013-07-26 22:39:01,642 WARN  [main] base.Database    - database startup attempt (7 of 12) failed; sleeping for 10000 milliseconds and will try again...

      2013-07-26 22:39:11,704 WARN  [main] base.Database    - database startup attempt (8 of 12) failed; sleeping for 10000 milliseconds and will try again...

      2013-07-26 22:39:21,766 WARN  [main] base.Database    - database startup attempt (9 of 12) failed; sleeping for 10000 milliseconds and will try again...

      2013-07-26 22:39:31,828 WARN  [main] base.Database    - database startup attempt (10 of 12) failed; sleeping for 10000 milliseconds and will try again...

      2013-07-26 22:39:41,907 WARN  [main] base.Database    - database startup attempt (11 of 12) failed; sleeping for 10000 milliseconds and will try again...

      2013-07-26 22:39:51,969 ERROR [main] core.OrionCore   - Failed to read the server's multi-tenant mode property (is there a multi.tenant.mode record in the OrionServerProperties table?)

      java.sql.SQLException: Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.

      etc........... .................

      2013-07-26 22:39:51,969 FATAL [main] core.OrionCore   - killing server. reason = Failed to read the server's multi-tenant mode property (is there a multi.tenant.mode record in the OrionServerProperties table?)

       

      I dont want to reinstall EPO as its a pain, because i have to redo the rules and etc.

       

      Any help would be appreciated.



       

      Message was edited by: nalaka0094 on 26/07/13 16:55:19 CDT
        • 1. Re: EPO 5.0.0 - Can't login to the console, https://ARMOUR:8443
          rackroyd

          The problem would seem to be a failure to connect to the expected Sql instance:

           

          20130726220747          E          #00916          EPODAL            ePOData_Connection.cpp(282): Failed to logon the domain user ARMOUR\Administrator to connect to database.

          20130726220747          E          #00916          EPODAL            ePOData_Connection.cpp(352): Error 0x80070002 returned from credentials callback. Database NOT available

           

          Unfortunately the failure to load /core/config when Sql is unavailable is another known issue for ePO 5.0.0 alone (to be fixed in ePO 5.0.1, aka patch 1).

          It's still possible to find and check the db.properties file manually,  except for the hashed db password in the file. which is basically the same thing.

           

          Also, you should check the obvious that Sql services are started and a test connection shows that Sql is available.

           

          This support article may help you on the last part if you're not sure:

          KB70929 - Steps for testing SQL database connectivity using test.udl file