Restart the Microsoft SQL Server service.
Log on to the SQL Server hosting the ePolicy orchestrator (ePO) database.
Click Start, Run, type services.msc, then click OK.
Right-click on the SQL Server [EPOSERVER] service and select Restart.
Verify it is possible to connect to the SQL server to access the ePO database using OSQL commands. For more information see KB51855 .
1 of 1 people found this helpful
Debugging install issues can be quite complex and involved, you may find it better to open a McAfee support call at this point.
This specfic issue was resolved by disabling VSE and disabling the agent so it wouldn't reactivate at the next policy enforcement.
I would with McAfee Support to troubleshoot this.
Ok just want to confirm.. before upgrading from 4.6.4 to 4.6.6. best would be to follow these steps:
1. Backup database & EPO folders
2. Stop McAfee services
3. Run upgrade installation 4.6.6
4. Restart EPO server
Does that sound about right? Also maybe go through the supported products KB before the upgrade: https://kc.mcafee.com/corporate/index?page=content&id=KB69814
Yes having good backups are very important! I would also advise you to take regular backups of all the important bits of ePO (keys, policies,system tree, server tasks etc..) you never know when you might need one.
I didnt stop the services for my upgrade, but i did remove VSE which helped.
Oh an keep supports number to hand just in case :-)
Awesome! Thanks Pierce.