Comprehensive data protection for all workloads
Post Reply
Wayneywoo
Influencer
Posts: 17
Liked: 1 time
Joined: Feb 24, 2021 1:10 pm
Full Name: Wayne Trevena
Contact:

Upgrade failing - V12.2 to v12.3.1

Post by Wayneywoo »

Hi all,

Has anyone seen this before?

I've downloaded the 12.3 ISO, mounted and I get the same error as when I extract the ISO and manually run the setup.exe

"An error has occurred. The system cannot open the device or file specified"

I was able to upgrade from 12.1 > 12.2 but I get this error trying to go to 12.3

I'm re-downloading the ISO in the hope there may be some corruption in the previous download.

Many thanks all!
W
Mildur
Product Manager
Posts: 10642
Liked: 2867 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: Switzerland
Contact:

Re: Upgrade failing - V12.2 to v12.3.1.....

Post by Mildur »

Hello Wayne,

Upgrades worked for me on 3 backup servers in our labs, and we have tens of thousands of customers who have successfully upgraded already. I suggest checking the checksum of the downloaded ISO and possibly disabling your Malware Protection application while running the update, as it may have interfered with the upgrade process.

KB: https://www.veeam.com/kb4696
Latest ISO for upgrading v12.2 to v12.3.1: VeeamBackup&Replication_12.3.1.1139_20250331.iso
MD5: AEEBD18EAE0BB0257E5682325065F78A

If the upgrade still doesn't work, please contact our customer support team for further troubleshooting.

Best,
Fabian
Product Management Analyst @ Veeam Software
Wayneywoo
Influencer
Posts: 17
Liked: 1 time
Joined: Feb 24, 2021 1:10 pm
Full Name: Wayne Trevena
Contact:

Re: Upgrade failing - V12.2 to v12.3.1.....

Post by Wayneywoo »

Hi Fabian,

Thanks for the reply!

I'll double check the ISO after it has downloaded, hoping it was corrupt in some way. Strange how it extracted and mounted without issue.

I've not had much luck getting support to help on the community version, having submitted tickets in the past that just lapse and close automatically :-(

Currently downloading the ISO again after it being deleted this morning by another engineer due to disk space alert! Will update the ticket once I've checked the ISO.

All the best,
Wayne
Wayneywoo
Influencer
Posts: 17
Liked: 1 time
Joined: Feb 24, 2021 1:10 pm
Full Name: Wayne Trevena
Contact:

Re: Upgrade failing - V12.2 to v12.3.1.....

Post by Wayneywoo »

Well......download finished, MD5 matches and the error still occurs

In the setup log (SuiteEngine_16_04_2025_08_19_04.log) I get this:

#MOD: Log removed, please do not upload them to the forum as stated in our Forum Policy.
Wayneywoo
Influencer
Posts: 17
Liked: 1 time
Joined: Feb 24, 2021 1:10 pm
Full Name: Wayne Trevena
Contact:

Re: Upgrade failing - V12.2 to v12.3.1.....

Post by Wayneywoo »

Logged support ticket 07673864
Mildur
Product Manager
Posts: 10642
Liked: 2867 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: Switzerland
Contact:

Re: Upgrade failing - V12.2 to v12.3.1.....

Post by Mildur »

Hello Wayne,

I removed the logs from your comment. Please comply with our forum policy and do not upload log snippets in this forum. The forum is not an alternative way to get technical support for such issues. The Veeam team in the forum cannot assist in troubleshooting log files and environmental issues.

Thanks for the case number.
Considering you have the community edition, you may also just consider to just re-deploy the backup server on a new machine (or use the same machine after uninstalling the old version) and restore a configuration backup to retain the configuration. But I would first wait to see if your case get picket up from the case queue (support on best effort for our free product offering).

Thank you for understanding,
Fabian Kessler
Product Management Analyst @ Veeam Software
RubinCompServ
Service Provider
Posts: 386
Liked: 114 times
Joined: Mar 16, 2015 4:00 pm
Full Name: David Rubin
Contact:

Re: Upgrade failing - V12.2 to v12.3.1

Post by RubinCompServ »

One of our customers is having this same issue (Case #07646787). We were able to "bypass" the issue by manually running the Server.x64.msi file, which then ran us through the entire setup wizard successfully. There is a suspicion that it was caused by the Catalog service to be an older version than the rest of the components (it was still the 11a version, for some reason); we had to manually update that but won't know if it resolved the issue until we try to go to v13.
Post Reply

Who is online

Users browsing this forum: Bing [Bot] and 8 guests