Thanks for sharing the log. Unfortunatly I couldn't find any clue from log you have provided as the log is old which was captured on 30th July2013.
It would be better if you can enable orion debug level and reproduce the issue then get the orion.log along the bellow information: to enable orion debug log level you may refer article http://kc.mcafee.com/corporate/index?page=content&id=KB52369
-Which version of ePO are you using and it's patch?
-What is the version of SQL ? Is it installed on same ePO server or on a remote server?
-Check the DB port and verify if the same port is listed in db.properties file.
-Also please check your IE security settings and make sure it is not blocking.
Sorry about that. Just found the event service is not starting. This is what is being used to get the logs for Orion correct?
I enabled the Orion debug log.
-Which version of ePO are you using and it's patch? EPO 4.6.4.
-What is the version of SQL ? Is it installed on same ePO server or on a remote server? SQL 2008 R2 SP1
-Check the DB port and verify if the same port is listed in db.properties file. DB port is showing as 58308, is that correct?
-Also please check your IE security settings and make sure it is not blocking. Checked
The orion.log is created by ePolicy Orchestrator Application Server.
If I understand your post; your ePO log in page is not loading and when tried TS the issue you found Event parser service is not running. is that correct?
There is nothing to do with event parser if the credential is fine and application server service is running, ePO log in page will open and you will be able to log in. If the log in page itself is not opening it means there is something wrong with the authentication between ePO server and the SQL. Once this is corrected the ePO log in page will comes and you will be able to log in also the event parser service will starts. So here you need to check few thing as below:
1) ePO DB size
2) DB port
3) DB connection with the credentials
where did you see DB port is showing as 58308 - is it in db.properties file or in sql configuration manager. If you have not confirmed from both the side please reconfirm it (db port should be same in both the location) and once it is done then go to ePO configuration page and test the connection. If the connection is succesfull with the provided credential apply it and restart all the three ePO services.
Location to check the port:
1 - SQL Server Configuration Manager
2-To change the value of db.port= in the file db.properties.
Note: Before making any changes to any file please make sure you have taken back of that.Stop and Start the ePO 4.x services.
Yes thats correct, found when I was restarting services that event parser is not running.
1) ePO DB size: 210GB
2) DB port: 1433
3) DB connection with the credentials: If i go to https://myserver:8443/core/config and I test DB then it connects fine?
@vuilwerking yep i have tried the compatability view option
Here I can see the port difference as you said in your previous reply the DB port is: 58308 and now you said db port is : 1433
I guess the db port 1433 you have seen from SQL configuarion manger and the db port 58308 you have seen in db.properties file. is that correct?
Then please correct the db port number in db.properties(58308) file which you got from SQL configuration manager(1433). Means remove the dp port 58308 and put 1433 in db.properties file.
Ideally a clean set of logs would be useful here. Can you stop the services, then remove the contents of ..\DB\logs and ..\server\logs (or move the contents to a different location if you want to keep them.)
Then start the services again and once you have reproduced the problem zip up and attach the logs that have been created - we can have a look.