cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

MS Cluster ePO upgrade failed 5.9.0 to 5.9.1 (SQL DB installed MS-Cluster)

Jump to solution

MS Cluster ePO upgrade failed 5.9.0 to 5.9.1 (SQL DB is also MS-Cluster)

Rollback Failed - Orionlog

epo Http 500 internal error

The following extensions are in a partially installed state: [Countermeasures:5.1.3.188, AvertAlerts:5.1.3.188, HostIPSLicense:8.0.8.1082, EPOCore:5.9.1.251, HelpDeskTool:2.0.0.130

helpdesk tool &HostIPSLicense removed 

EPOCORE: 5.9.1.251 - ePO upgrade failed and rollback

Countermeasures & Avertalerts - as chked top 200 rows in DB orionextension the version is same.

1 Solution

Accepted Solutions

Re: MS Cluster ePO upgrade failed 5.9.0 to 5.9.1 (SQL DB installed MS-Cluster)

Jump to solution

The failure happened because of cipher suites which are not loaded properly on operating system. using IIScrypto tool to re-arrange the ciphers resolved the ePO upgrade issue.

 

 

2 Replies
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 3

Re: MS Cluster ePO upgrade failed 5.9.0 to 5.9.1 (SQL DB installed MS-Cluster)

Jump to solution

The orion log should show exactly what it is expecting (what is in the database) vs what it sees in the file system.  For example, EPOCore:5.9.1.251 may show expecting a different build.  Here is how to fix mismatched extensions.

If the database has a lower version than the file system, go to the install directory for epo (turn off epo services first), epolicy orchestrator\server\extensions\installed\epocore (or whatever extension you need to fix).  You will see a higher build folder in there - remove that folder from epo install directory or delete it.  Then go to server\conf\catalina\localhost and find the epocore.xml file, edit it to match the build that is in the database and the folder build that now should be the highest in extensions\installed.  Once you fix all the mismatches, you can restart epo services.

However, if the build in the database shows 5.9.1 instead of the original 5.9.0 before the upgrade attempt, you will need to do a disaster recovery as the rollback left the database in a partially upgraded state.

Any time you plan upgrades, be sure to thoroughly go through KB71825 and run the pre-installation auditor tool to first remediate any issues that could cause a failure.

Re: MS Cluster ePO upgrade failed 5.9.0 to 5.9.1 (SQL DB installed MS-Cluster)

Jump to solution

The failure happened because of cipher suites which are not loaded properly on operating system. using IIScrypto tool to re-arrange the ciphers resolved the ePO upgrade issue.