Well I hate to be the bearer of bad news, but once the installer gets interrupted it is almost impossible to get the MSI installer to restart the setup completely. So in support we have been backing up the <install_path>\ePolicy Orchestrator\4.0\DB folder and the database, then removing ePO, re-installing 4.0, installing the last patch they were on (not the one they were trying to install) and then restoring the DB backup and files. This will get your server back up and running.
We would then attempt the patch 5 installer again once we have verfied the following:
/ Things to help you in the furture eith patch 5 and patch 6 installs are as follows:
1. Disable Auto-close on the ePO Database
2. Use simple characters (alpha and/or numeric) your passwords for SQL and the epo account specified during install.
3. Make sure you are logged on to the ePO Server in Console 0 (not terminal session 1, 2, 3, etc), you can do the install remote, just force the Admin or console switch with MSTSC.EXE.
4. Ensure that you have plently of Room availible in the ePO Database and Transaction log of the epos SQL server. As if the SQL DB/Log gets full durring the setup, a roll bak in SQL will occur and this can cause the setup to exit out.
Hope this helps.
I will try this out,,thanks for the answer
I'm having the same problem. And I've done the recovery and tried again with the same result. :/
Is it so? Im not trying the solution yet, kinda hesitate to do so since you said
the outcome still the same. Did you manage any other module on the epo?
Currently my epo manage VSE and Policy Auditor..
The issues installing a patch on ePO 4.0 are usually due to a java problem, have a look at this:
In the last 3 cases the cause was due to a Microsoft's patch (you can find all the info in this link)
If you see my error log that i attach, there is no java error appear. FYI,
i already run through the installation with Mcafee Tier 1 support. They
also ask me to reinstall the ePO.
I don't have any issues with ePO 4.0, it worked as expected. It's the upgrade process to ePO 4.5 from ePO 4.0 Patch 5 that's the problem. But I'll have a look at it see if it helps.
Another problem is that all of my automation tasks are gone. I've logged a case and the only solution was to roll back the SQL db from backup apparently according to McAfee support
So I'll go ahead with that, see if it helps. So be sure to do a snapshot or similar on both the db and ePO files, as one always should, if upgrading.
Thanks for the suggestions.
epo db restore got my automation tasks back again. Seem to be back at square one again. That's always something.