[v13] Upgrade keeps crashing out

[Gatt]

Anyone else having issues starting the upgrade from 12.3 to 13?
It starts and gets as far as doing a System Configuration check - then it just closes with no sign of any error messages

it just closes, as if it had finished all it was meant to do, leaving the system upgraded

is there some prereq for Server 2025 that's needed that I'm missing

[Mildur]

All prerequisites are listed in the upgrade checklist in our help center.
If you run into issues, then a case with our customer support will be required.

Thank you,
Fabian

[Gatt]

[POSSIBLE BUG!]

I've raised this with case #07896172 as it would appear there is a slight bug in VBR 13

I was reviewing the Windows Event Log to find a reason as to why the setup was crashing and found this entry:

Code: Select all

Application: Veeam.Setup.Wizard.exe
CoreCLR Version: 8.0.2125.47513
.NET Version: 8.0.21
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Reflection.TargetInvocationException: An exception occurred during the operation, making the result invalid.  Check InnerException for exception details.
 ---> System.ComponentModel.Win32Exception (1608): Unknown property.
   at Veeam.Setup.MsiLibrary.VmMsiCommon.GetProductInfo(String strProductCode, String strProperty)
   at Veeam.Setup.PrereqEngine.Helpers.PackageVersionCollectors.PackageVersionCollectorPowershell7.Collect()
   at Veeam.Setup.PrereqEngine.PackageProcessors.PackageProcessorPowershell7.CheckStatus()
   at Veeam.Setup.PrereqEngine.PackageInstaller.CheckStatus(VmProductPrereqItem prereq)
   at Veeam.Setup.PrereqEngine.PrereqEngine.SetPrereqList(List`1 prereqList)
   at Veeam.Setup.Wizard.VmPrereqEngineHandler.SetPrereqList(List`1 prereqList)
   at Veeam.Setup.Wizard.WPF.Pages.SystemConfigurationPageViewModel._initializeWorker_DoWork(Object sender, DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
   --- End of inner exception stack trace ---
   at System.ComponentModel.AsyncCompletedEventArgs.RaiseExceptionIfNecessary()
   at System.ComponentModel.RunWorkerCompletedEventArgs.get_Result()
   at Veeam.Setup.Wizard.WPF.Pages.SystemConfigurationPageViewModel._initializeWorker_RunWorkerCompleted(Object sender, RunWorkerCompletedEventArgs e)
   at System.Threading.ExecutionContext.RunForThreadPoolUnsafe[TState](ExecutionContext executionContext, Action`1 callback, TState& state)
   at System.Threading.QueueUserWorkItemCallback`1.Execute()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
   at System.Threading.PortableThreadPool.WorkerThread.WorkerThreadStart()

This struck me as odd, as I had Powershell 7 installed - Version 7.5.4 to be exact

So, I extracted the ISO and had a look at the files - which led me to \Setup\VBRSettings.xml

In that file there is this line (Line 224 I think):

Code: Select all

      <req name="Powershell7" version="7.4.13" />

So, to test this I tried to downgrade to 7.4.13, but the older version refused to install as it still thought 7.5.4 was still present

So next, I edited that leine to read:

Code: Select all

      <req name="Powershell7" version="7.5.4" />

And, amazingly, this appears to have resolved the issue and I am now in the process of upgrading B&R to v13 - fingers crossed!

[Mildur]

Hi,

Please note, this is fully unsupported, as Veeam Backup & Replication v13.0.1 relies on Microsoft Windows PowerShell 7.4.13 (Help Center - System Requirements).
The installer process should have deployed 7.4.13 in case its missing.

Best,
Fabian

[Gatt]

Ok thanks - missed that when I was looking into the requirements - in fact I may have gotten confused as right underneath that box, there is another one that refers to PowerShell 7.5.1 - but looking again, this refers to the "Remote PowerShell Console.

It may be helpful for the installer to flag this, rather than for it to blindly terminate itself

In the meantime, I'll look to downgrade the version of PowerShell to 7.4.13 to get it back into support

[Mildur]

Strange, let me check tomorrow with our help center team.
It‘s confusing that we deploy PowerShell 7.4, but for Remote PowerShell we require 7.5.1.

Please wait for now, I‘ll provide you an update which versions are officially supported.

Best,
Fabian