Hey ​@evd08 
When did you get this error, is it during the upgrade or before?

You mention domain user… it means that your VBR is linked to a domain. I hope you are using a dedicate domain for your backup environnement otherwyse you are not in the best security best practice.


 

Hi ​@evd08,

Can you confirm that the user you are using to perform the update has the “Backup Administrator” role within Veeam RBAC? And is MFA for this user enabled?

In case not, try to add the account to Veeam with the Admin rights and run the setup again.

Best

Lukas

Thanks ​@Stabz , I know you are right, VBR server is still in production domain. We will remove it anytime soon.

I get the error during the upgrade proces, during the configuration check.

​@lukas.k The user indeed has the backup admin role with MFA temporary disabled since I marked it as a service account. Thanks!

Other point are you using MS SQL ou PostgreSQL ?
if you are using PostgreSQL maybe your account is not in The Authorized Users Lists.

You could use this KB for help: https://www.veeam.com/kb4542

​@Stabz I'm using SQL server on a separe SQL server. The user has sysadmin rights in SQL.

Other than what everyone has said I think your support case will help the best here.   Let us know how that goes and the solution.

Hi, I’m having the same issue. PostGres database.
Didn’t have the issue during the previous version upgrade...

Contact support like the OP did to get help.

I had similiar issue in the past. Solution was added extra administrator role for this specific user. User as part of group or built-in group in console was in some cases not sufficient.

Try whit Local Administrator user.

regards

I’d suggest also checking for any locked files or services that didn’t fully stop during the upgrade. Sometimes, Veeam services (especially Veeam Installer or Veeam Backup Catalog) hang silently in the background — you can spot this using Sysinternals' Process Explorer or by checking the upgrade log in %ProgramData%\Veeam\Setup\Temp.

The upgrade now successfully completed.

It was a combination of 2 suggested solutions from Veeam support: changing the logon account of the Update service to the same as the backup service and setting both to the format DOMAIN\USER.

Next step will be removing the VBR server from the domain . Thanks all!

Great ! Thanks for the feedback.

Glad to hear support got you fixed up.

Thanks for the feedback!