Skip to main content
  • EN

Hello guys, I have been stuck with a Veeam Data Platform Premium installation for Veeam Recovery Orchestrator… Each time I do the installation, it rolls back and fails. I suspected it was a database configuration issue from the log extracts below: 

>29.05.2025 18:32:18]:ERROR] System.ComponentModel.Win32Exception (1603): Fatal error during installation.
   at Veeam.Setup.MsiLibrary.VmMsiCommon.CheckError(VmMsiDatabase db, UInt32 result)
   at Veeam.Setup.MsiLibrary.VmMsiInstall.DoActionCheckError(String action)
   at Veeam.Setup.Wizard.VmInstallProduct.ExecuteCustomDialog(VmMsiInstall install, String Dialog)
 

/29.05.2025 18:34:49]5WARNING] Unable to proceed with the setup: invalid database configuration detected.
The following registry keys will not be created:

EntraIdSqlHostName (REG_SZ)
EntraIdSqlHostPort (REG_DWORD)
EntraIdSqlUserName (REG_SZ)
EntraIdSqlPassword (REG_SZ)

 

I corrected the configuration issue by installing Microsoft SQL Server 2019 (Enterprise Edition) and using that instance for the installation but still failed. Anybody who has encountered a similar issue?

Hi ​@Madi.Cristil ​@safiya ...this question would probably be best to be in the VRO Den page. Maybe ​@ertelle1 can provide assistance ​@ian.gatundu , or at the very least contact Support. 

Hi ​@coolsport00, I have already raised a case with support cause it’s a weird occurence, given I had done this a while back in my labs and I was successful. 

Hi ​@ian.gatundu ...understood. Unless someone chimes in who's had a similar issue, it's probably best to continue to work with Support 

​@ian.gatundu the only time I had this issue I had to perform a few reboots and it finally cleared for me. Is this a brand new install or an upgrade? 

The most recent issue had to deal with the package missing for entra -- https://www.veeam.com/kb4725

Hello ​@coolsport00 ​@ertelle1,

I finally got a solution to this problem, we were installing VRO on a server that was previously running VBR alone, after reviewing logs and engaging with support, the solution was to take a configuration backup and format the backup server then do a clean install and restore the configuration.

The reason for the failure to install is because of the previous VBR installation that had instances that were colliding with the existing database that was being used by Veeam B&R.

 

Alternatively, you can perform a migration to a new server, do a clean installation of VRO and then restore the configurations. 

Woohooo! I can finally get to mark this as solved and I hope it will help someone in the future.✅

Glad to hear you got it sorted ​@ian.gatundu 🙌🏻

Comment


Terms & Conditions