The upgraded ICE version cannot be less error - Kinetic Database Upgrade (On-Prem)

[mto29 (Mic)]

Hi all,

Hope you’re well.

Just swinging back to my original post on this…

Kinetic Upgrade 2024.2 On Premise

Hey all, Hope you’re well. Sorry this might be a super simple one… we are trying to upgrade our Test environment to 2024.2 release, first time doing an upgrade without support. I’ve mounted the file to the VM server and ready to run through the installation as per the release instructions but hesitant to proceed if this could update our UAT environment which also sits on the same VM server. Does anyone know if there is a way to push the release to only one environment please? As we don’t wan…

We successfully upgraded 1 out of 3 environments and has been running without issue and have since done an update patch to the latest version. We now need to upgrade another environment to the latest version making it 2 out of 3 running 2024.2 and the other still on 2024.1.

I’m reading through the documentation, skipping the installation step as this is already done (with the previous first install), the 2024.2 directory and installs exist. So I thought, it would just be a case of upgrading the database as per the below…

(If the Database Server Manager dialog does not open automatically, you can manually upgrade
your database.
To do this:
a. Right-click on the Database Server Management node and select Add Kinetic Database
Server. If prompted to select a Snap-In Version, select the version of the database server
you want to add. Click OK.
b. In the Server\Instance field, enter the SQL Server name and the SQL Instance ID. Select
the Authentication mode to connect to the SQL Server.
c. Click the Verify Server button. Click OK twice.
d. After the server is added, the server/instance is displayed as a node under Database Server
Management in the Tree View. Right-click on the database server and select Register
Existing Database. You must select the Deployment Path to point to the current path. For
example, if your current version is 2024.2 (build 11.3.200), use the browse button to
change to C:\Epicor\ERP11\11.2.300.0.
e. Select the database. Choose Upgrade Database.)

But when trying to do this, I get the below error, because it still sees the database as running 4.3.100.11 / 11.3.100.0

Looping back to my first upgrade (in the previous topic) when I originally got to this step of upgrading the admin console, I selected 2 out of the 3 environments as ‘Install Components’ so it didn’t upgrade and the 1 being upgraded as ‘Import’

When I check the application server config, I tried changing the deployment directory but it fails because the database upgrade portion hasn’t been done.

I’ve tried going to the database properties and changing the deployment path, but it just reverts back to ERP11.3.100.0 upon saving.

So I guess the issue I’m facing… is that I can’t find a way to get UAT to look at the new install directory so I can hit ‘Upgrade database’

Just wondering has anyone came across this please when installing across different versions/environments? Or I could definitely be missing a step? Unless maybe I need to go through the complete installation again rather than just trying to get UAT to point to the new version?

Many thanks in advance!!

[Chad_Smith]

First thought: The error message says the common database is the problem. Did you try the Update Common Database option under Database Management?

I am sure there is a “cleaner” way to do this, but I have found that at times either the EAC or me get so confused that I can’t seem to get it to finally upgrade said environment.

Enter the nuclear option.

You can remove the db and/or the application server from the EAC (do not delete db in SQL!) and then use the register existing db/application server option to add them back in. At that point, I point them to the newest deployment folder and kick off said upgrades. This is an ugly approach, but I have done it out of a lack of other options in the past. I think the app server part is the really awful part so avoid that part if you can.

[mto29 (Mic)]

Thanks so much Chad!

When I go to update common database, it asks me to select the snap in version, so I select 11.3.100.0

which then goes to the below

which when I did a release upgrade previously, there was a bunch more tasks to Execute here…

I saw this in the documentation in ref to an upgrade and wondered about removing/re-registering the app server, but was a bit hesitant to do it at first.

[mto29 (Mic)]

So far so good by removing db server and re-registering it, thanks so much!! Just out of interest, were there a load of issues that you ran into when re-registering the app server?

[Chad_Smith]

@mto29

were there a load of issues that you ran into when re-registering the app server?

Yeah, it’s always a bit of a hassle. I always make sure to grab screenshots of everything before I nuke it. I think these are the cleanup items:

• Remove physical file path of deployment: ie c:\inetpub\wwwroot\appservername
• Remove web site in IIS for the appservername (NOT the default web site!!!)
• Remove custom application pool in IIS for the appserver
• Remove LocalClient folder for the appserver

Again, ONLY do that if it refuses to deploy the newly re-created app server. It’s also possible that you could have custom stuff in the phyiscal deployment folder so always a good idea to check and/or do a backup first.