Network Management

The SolarWinds Platform Configuration Wizard is unable to run and shows an "An exception occurred fetching the DB branding version" error

This article contains remediation steps for when the SolarWinds Platform Configuration Wizard fails with a DB branding version error.

First published date

8/27/2024 4:28 AM

Last published date

10/6/2025 3:39 PM

Overview

When running the SolarWinds Platform Configuration Wizard, the wizard is stopped when selecting a database account and throws an error, as shown in the screenshot below:
An exception occurred fetching the DB branding version.

image.png

A record of this error can also be found in the log at C:\ProgramData\SolarWinds\Logs\Orion\ConfigurationWizard.log.

Product section

Network Performance Monitor

Cause

The SQL server is trying to use the domain account during impersonation and failing when utilizing a local account.

Resolution

Resolution 1

Verify that the Branding Version value matches between the Registry and WebSettings Table in the SolarWinds Database.
  1. Press Win + R to open the Run command window, add regedit and press enter to open the registry editor.
  2. Navigate to HKLM>Software>WOW6432Node>Solarwinds\Installer > InstalledBrandingVersion
Registry_Editor_and_Database_Manager.png
  1. Open Database Manager from the SolarWinds Platform folder of the Start menu.
  2. Select Add Orion Server, then expand the SQL server and SolarWinds database in bold.
  3. Navigate to and double-click the WebSettings table.
  4. Click Execute Query in the window on the right to select the first 1000 rows of the table
  5. Check the SettingValue of the SettingName Branding Version and ensure it matches the registry entry. If it does not, select Edit table, double-click the cell in the database to add the entry from the registry, and press enter to confirm the change.
  6. Execute the query again to ensure the change was saved, and run the Configuration Wizard again.

 Resolution 2

To bypass the error, use a domain account for the SQL server, then switch to a local user for the SQL database account. This will allow the Configuration Wizard to complete.