Loading...
Loading...
The Veeam Backup & Replication Console displays the following error when attempting to connect to a Veeam Software Appliance that was recently updated: Unable to perform OAuth authorization: interaction_required. The Veeam Backup & Replication Console will report that it successfully auto-updated, however the connection still fails.
This issue occurs because some of Veeam Backup & Replication Console files were not updated. This can happen because the Veeam Backup & Replication Console has a configuration file, ClientUpdate.config, that contains excludeRules entries for the following files: Veeam.Backup.UI.Launcher.dll Veeam.Backup.Shell.exe Veeam Backup & Replication 13.0.1 included a fix that resolves the OAuth interaction_required error, and delivered in Veeam.Backup.UI.Launcher.dll. However, because this file is excluded by the Console's auto-update rules, the updated version is not retrieved and the OAuth failure persists even after the patch has been applied to the Backup Server.
The recommended solution is to remove the exclusion entries from the ClientUpdate.config file, then reconnect to the Veeam Software Appliance to trigger the download of the updated files. On the Windows machine where the Veeam Backup & Replication Console is installed: Close the Veeam Backup & Replication Console and ensure no Console or Shell processes are running. Open the Veeam Backup & Replication Console install folder. Default path: C:\Program Files\Veeam\Backup and Replication\Console\ Create a backup copy of ClientUpdate.config (for example, ClientUpdate.config.bak). Open the ClientUpdate.config file and remove the following two lines from the <excludeRules> section: <fileName>Veeam.Backup.UI.Launcher.dll</fileName> <fileName>Veeam.Backup.Shell.exe</fileName> Save the modified ClientUpdate.config file. Relaunch the Veeam Backup & Replication Console and attempt to connect to the Veeam Software Appliance, the auto-update will retrieve the previously excluded binaries. The OAuth error should no longer occur, and the connection to the VSA should succeed.(You may need to close and reopen the Veeam Backup & Replication Console to load the updated files.)
Click on a version to see all relevant bugs
Veeam Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.