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:18.104.22.168 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.
Was my reply helpful? If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.