Hi guys,
Yesterday we attempted to upgrade our VBR server from V12.3.2.4465 to V13.0.2.29 but were met with the below error during the installation process -
The upgrade failed and did not allow us to retry at all. Certain options were greyed out -
Checking Apps and Features, Veeam reported that it was upgraded but the app was inaccessible. -
In the end, we were forced to back out of out upgrade.
Has anyone seen this before?
ShaunB.
Best answer by ShaunB
Firstly, thank you for the warm welcome.
Regarding the upgrade, our VBR server runs as a VM, and fortunately, a VMware snapshot was taken before we started. This turned out to be one of our better life decisions, as it allowed us to successfully roll back when things went sideways.
After encountering the error, we attempted to restart the upgrade but were unable to proceed. We rebooted the server, and then, with time against us, followed guidance from a link that suggested clearing the TEMP directory before retrying the install.
Against my better judgment (and perhaps common sense), we went ahead with this step… which, unsurprisingly, turned out to be a big mistake. Lesson learned: not everything on the internet should be trusted, especially under pressure.
We also opened a support ticket with Veeam, but as mentioned above, we had unfortunately already cleared the files required for proper investigation. On a side note, it was the first time I’ve ever heard a Veeam support agent chuckle… in disbelief, I suppose! Our ticket remains open, incase the same issue pops up.
Fortunately, we were able to get the image back up and the VBR server running to perform some critical restores for our DBAs (who were understandably starting to look at us a bit nervously).
We are planning to reattempt the upgrade next Wednesday. Will keep you all updated on how it goes.
Thanks again for all the excellent advice, much appreciated!
+23Hi
From the looks of the error - “VmaNetExtensionCaller”, it would appear (maybe?) you have outdated or incompatible version of .NET? Installation & upgrade logs are located: %ProgramData%\Veeam\Setup\Temp. Have you looked at the Log here to see what it tells you? Here lists the requirments for Windows:
Aside from those things, unless someone else has suggestions, I advise reaching out to Veeam Support to get you sorted.
+22According to the KB page with upgrade paths your good there - https://www.veeam.com/kb2053
I would suggest checking the requirements as per Shane then open a ticket otherwise.
+5Hi
the best would be if you open a ticket at Veeam support, they should check the logs.
if you are having a configuration backup it’s maybe an option to uninstall Veeam, install 13.0.2 and do a configuration of restore with the configuration backup (if I would be in this situation and should get the backup server really fast back online I would do this).
configuration restore of V12 configuration backup with V13 is possible and supported.
+10I am with
Do your windows patches first and reboot the server Shutdown your jobs on bootup.
Try downloading a clean copy of 13.0.1. Unzip it or mount it and install.
Firstly, thank you for the warm welcome.
Regarding the upgrade, our VBR server runs as a VM, and fortunately, a VMware snapshot was taken before we started. This turned out to be one of our better life decisions, as it allowed us to successfully roll back when things went sideways.
After encountering the error, we attempted to restart the upgrade but were unable to proceed. We rebooted the server, and then, with time against us, followed guidance from a link that suggested clearing the TEMP directory before retrying the install.
Against my better judgment (and perhaps common sense), we went ahead with this step… which, unsurprisingly, turned out to be a big mistake. Lesson learned: not everything on the internet should be trusted, especially under pressure.
We also opened a support ticket with Veeam, but as mentioned above, we had unfortunately already cleared the files required for proper investigation. On a side note, it was the first time I’ve ever heard a Veeam support agent chuckle… in disbelief, I suppose! Our ticket remains open, incase the same issue pops up.
Fortunately, we were able to get the image back up and the VBR server running to perform some critical restores for our DBAs (who were understandably starting to look at us a bit nervously).
We are planning to reattempt the upgrade next Wednesday. Will keep you all updated on how it goes.
Thanks again for all the excellent advice, much appreciated!
+22Best of luck next week and here is to a successful upgrade. 👍
+23Good luck with the retry Shaun. Think I’m gonna give my Windows VBR environment a go after U1 comes out.
Best.
Update -
Finally upgraded!
The issue came down to duplicates in the database, which prevented the installer from running/completing.
Regards
ShaunB.
+23Great news
+22Amazing news
Update -
Finally upgraded!
The issue came down to duplicates in the database, which prevented the installer from running/completing.
Regards
ShaunB.
Could you please let us know which duplicates they were? Something simple, like different proxy servers or something similar?
Thank you in advance!
+23
Correct, working with support, we identified duplicate job entries. Not sure how exactly they were created but once they were removed, the setup could complete. Logs in C:\ProgramData\Veeam\Setup\Temp need to be investigated.
Hello All,
am also facing same issue while upgrading the Veeam backup & replication 12.3. (Build 12.3.2.4854) to VeeamBackup&Replication_13.1.0.411_20260723.
Could you please help to fix this issue. I have take VM Windows Server snapshot before upgrade the application
Windows powershell and microsoft.Net already updated
+23
Sure! I will raise the request. I saw the same kind of issue has been fixed before so that's reason i request for guidance.
+23All good. Doesn’t hurt to ask; but the fix/resolution shared above involves manipulating the VBR config database. And that’s something only Support can take care of.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
