SolarWinds Platform Install or Upgrade Error on Config Wizard Invalid object name dbo.CiscoBuffers_Daily

Full Error on ConfigurationWizard.log (C:\ProgramData\SolarWinds\Logs\Orion):

ERROR DBConfigProcessor - Error while executing script - Invalid object name 'dbo.CiscoBuffers_Daily'.
Invalid object name 'CiscoBuffers_upg'..
Error details: System.Data.SqlClient.SqlException (0x80131904): Invalid object name 'dbo.CiscoBuffers_Daily'.
Invalid object name 'CiscoBuffers_upg'.

The Configuration Wizard is trying to run a script wherein the table is missing or does not exist.

Note: Please ensure there is a recent database backup prior to making direct changes to the database. See Back up and restore SQL database instance using a .BAK file for the SolarWinds Platform for more information.
This issue is resolved in SolarWinds Platform 2024.2 and above. If upgrading is not feasible, consider the following workarounds:

Workaround 1

• Connect to the SolarWinds Platform server.
• Open SQL Server Management Studio (SSMS). If it is not installed, download it from the Microsoft SSMS page.
• Connect to the SQL instance using the SA account or, if applicable, the SolarWindsOrionDatabaseUser account.
• Expand the SQL server instance, right-click on the SolarWinds database, and select New Query.
• Paste the following SQL script: 

  -- Scripts are not supported under any SolarWinds support program or service.
  -- Scripts are provided AS IS without warranty of any kind. SolarWinds further
  -- disclaims all warranties including, without limitation, any implied warranties
  -- of merchantability or of fitness for a particular purpose. The risk arising
  -- out of the use or performance of the scripts and documentation stays with you.
  -- In no event shall SolarWinds or anyone else involved in the creation,
  -- production, or delivery of the scripts be liable for any damages whatsoever
  -- (including, without limitation, damages for loss of business profits, business
  -- interruption, loss of business information, or other pecuniary loss) arising
  -- out of the use of or inability to use the scripts or documentation.
  
  IF EXISTS (SELECT * FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_NAME = 'CPULoad_Detail' AND TABLE_TYPE = 'VIEW' ) 
     AND NOT EXISTS (SELECT * FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_NAME = 'CPULoad_Daily' AND TABLE_TYPE = 'VIEW' ) 
  BEGIN
          DECLARE @sql NVARCHAR(MAX) = 'CREATE VIEW [dbo].[CPULoad_Daily] AS SELECT * FROM CPULoad_Detail WHERE NodeID = -1';
          EXEC sp_executesql @sql;
  END
  GO
  -- missing LoadAverage_Daily view
  IF EXISTS (SELECT * FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_NAME = 'LoadAverage_Detail' AND TABLE_TYPE = 'VIEW' ) 
     AND NOT EXISTS (SELECT * FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_NAME = 'LoadAverage_Daily' AND TABLE_TYPE = 'VIEW' ) 
  BEGIN
          DECLARE @sql NVARCHAR(MAX) = 'CREATE VIEW [dbo].[LoadAverage_Daily] AS SELECT * FROM LoadAverage_Detail WHERE NodeID = -1';
          EXEC sp_executesql @sql;
  END
  GO
  -- missing ResponseTime_Daily view
  IF EXISTS (SELECT * FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_NAME = 'ResponseTime_Detail' AND TABLE_TYPE = 'VIEW' ) 
     AND NOT EXISTS (SELECT * FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_NAME = 'ResponseTime_Daily' AND TABLE_TYPE = 'VIEW' ) 
  BEGIN
          DECLARE @sql NVARCHAR(MAX) = 'CREATE VIEW [dbo].[ResponseTime_Daily] AS SELECT * FROM ResponseTime_Detail WHERE NodeID = -1';
          EXEC sp_executesql @sql;
  END
  GO
  -- missing VolumeUsage_Daily view
  IF EXISTS (SELECT * FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_NAME = 'VolumeUsage_Detail' AND TABLE_TYPE = 'VIEW' ) 
     AND NOT EXISTS (SELECT * FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_NAME = 'VolumeUsage_Daily' AND TABLE_TYPE = 'VIEW' ) 
  BEGIN
          DECLARE @sql NVARCHAR(MAX) = 'CREATE VIEW [dbo].[VolumeUsage_Daily] AS SELECT * FROM VolumeUsage_Detail WHERE NodeID = -1';
          EXEC sp_executesql @sql;
  END

• Execute the script.
• Run the Configuration Wizard again.

Workaround 2

1. Connect to the SolarWinds Platform server.
2. Open SQL Server Management Studio. If you need to install it, the download is available from the Microsoft SSMS page.
3. Connect to the SQL instance with the SA account or, if it is an administrator, the SolarWindsOrionDatabaseUser account.
4. Expand the SQL server and right-click on the SolarWinds database then select New Query.
5. Identify the failing script in the ConfigurationWizard.log located at C:\ProgramData\Solarwinds\Logs\Orion by doing a search for "Failing SQL Command".
6. Copy the failing script into the query and click Execute.
7. Run the Configuration Wizard again.