We are trying to patch 2024.1 from .4 to .5 and we are receiving the below error message. Any one know what we might be doing wrong, we have followed the instructions from Epicor.
IceCommon Database version 11.3.100.4 does not match targeted install version of 11.3.100.5.
The IceCommon Database will need to be updated to be targeted install using DBMigration before continuing with the server update
Having issues installing the .5 patch. Following the official instructions and still getting errors afterâŚ
a restart pool and computer restart,
DB model regen,
Admin Console updates,
removing the DB from the Admin Console and adding back,
changing the Epicor DB deployment folder to 11.3.100.0
âUpgrade Kinetic Databaseâ option fails with Upgraded ICS Version 4.3.100.0 cannot be less than the current Ice Version 4.3.100.4.
Itâs like it wants the Ice DB to be at .5 before you run the .5 update.
I am encountering the same error. I even verified the DLL versions for the DB Manager Extension seem to be correct and reran the .5 Admin Console updater
I hit this on my initial install of 2024.1.4 and found that Update Common Database was supposed to fix it, but it did not. I added a demo database which made the ICECommon database below and then deleted and reinstall the app server and was able to update the database.
Iâve seen the Update Common DB fail (well not update) when the files arenât installed to C:\Program Files (x86)\Common Files\Epicor Software\Database Manager Extensions\4.3.100\DB Migration\PatchCommonDB (or AV prevents them getting written). There should be a folder under there for each version.
Iâm having the same issue when going from 2021.2 to 2024.1.9. If I install it as the base patch it goes ok, but trying .9 gives me the database version error. In a KB it says to Update Common Database, but it says itâs already up to date.
Funny thing is that we were having the same issue. We didnât realize that we had to check the âEXECâ checkbox in the upper-left of the screen before we clicked on the upgrade button. After we selected this, it worked fine. Not sure if this is your issue, but I mention it just in case.
The common dB is read only in Sql so Iâm wondering if itâs not changing the status or sql is taking too long to respond to the change before the upgrade. Pure speculation on my part, I have tried a patch update on my demo environment. Iâll have to try it out
I have a test server and I did 23.2.45 and 24.1.10 from 21.2.10. We are going to move production up to 23.2 and I am going to start moving 400+ dashboards up to 24 for the next round.