If you could share the Orion.log then it would be easy for us to give you any suggestion, However what you can do is -
Stop all the McAfee EPO Services.
Go to <EPO Installation Path>\server\conf\orion\
Copy db.properties to another location (If something goes bad then you can copy it back )
Then go to <EPO Installation Path>\server\conf\orion\, open db.properties using a text editior (notepad), remove the DB Instance name and Encypted password.
Save the File.
Start Only McAFee EPO Application Service and try to access https://localhost:8443/core/config page and if you are able to access it then enter the required credentials and click on Test Connection.
Assuming that you have entered the correct credentials,If test connection is successfulll, Click on Apply.
Restart the Application Service and Start Other two McAfee EPO Service and try to login and update the post there is any issues.
No luck with this workaround. I think ePO 5.0 should behave like 4.6.It doesnt understand Windows or Mixd mode and keep on trying with same user even if changed the authentication mode.
Please see orion.log
orion.log.zip 21.6 K
Hi anyone can let me know this location, this is the fresh event parser log
0130516080848 I #06832 EVNTPRSR Initializing Server...
20130516080848 I #06832 EVNTPRSR Database initialization: Starting.
20130516080848 I #06832 MFEFIPS Loading: "C:\PROGRA~2\McAfee\EPOLIC~1", Role = Officer, Mode = Normal
20130516080848 I #06832 MFEFIPS Module Initialized.
20130516080848 E #06832 EVNTPRSR D:\EPO3\BUILD\epo\dev\src\server\include\ePOData.inl(290): Missing DB connection info in C:\PROGRA~2\McAfee\EPOLIC~1\Server\conf\orion\DBFAC3~1.PRO
20130516080848 E #06832 EPODAL ePOData_Connection.cpp(352): Error 0x80000008 returned from credentials callback. Database NOT available
20130516080848 E #06832 EVNTPRSR D:\EPO3\BUILD\epo\dev\src\server\include\ePOData.inl(319): Database initialization: Failed (hr=0x80000008).
20130516080848 E #06832 EVNTPRSR Failed to initialize database layer. Cannot continue.
20130516080848 I #06832 EVNTPRSR EventParser Stopped.
20130516080848 I #06832 EVNTPRSR Cleaning up Server...
This error is slightly misleading - it's a result of the main issue, which is a failure to authenticate to SQL. The way that ePO 5.0 responds when it can't access the DB is different compared to previous versions, which has the side-effect of making the config-auth page unavailable. (This will be fixed in the next patch.)
The way round this is to manually edit the db.properties file (which is what the config-auth page does.) Take a backup copy of the file and then open it in a text editor.
- db.user.name is the name of the account ePO will use to connect to SQL.
- db.user.domain indicates if ePO is using Windows or SQL authentication: if blank, it's using SQL: otherwise this is the name of the domain that will be used for Windows authentication.
- db.user.passwd.encrypted.ex is the password hash for the account.
Change db.user.passwd.encrypted.ex to db.user.passwd and enter the password in plain text. So for example if the password was "foobar", the entry might look like this:
You would change it to:
Save and close the file, and start the application server service. (Don't start the other ePO services yet.) Once started, go to the config-auth page and re-enter the password, and test the connection. Assuming the test passes, click Save, which will save the hash back to the db.properties file. You can then start the other services.