"Cannot drop the procedure 'dbm_CreateFilegroup', because it does not exist or you do not have permission" error in the Configuration Wizard when upgrading to SolarWinds Platform 2025.2

This error prevents successful completion of the upgrade to 2025.2. The Configuration Wizard fails with the below message, indicating either a permissions issue or a mismatch in the database schema.

 "Cannot drop the procedure 'dbm_CreateFilegroup', because it does not exist or you do not have permission"

• The SQL account used for the upgrade may lack the necessary permissions to drop or modify database objects.
• The database schema for the relevant objects may not be set to the expected owner (typically dbo).

• Use an SA (System Administrator) account to run the Configuration Wizard, or
• If using a non-SA account, ensure it has the required permissions as outlined in the following articles:
  • Why I Need SQL SA Level Account Credentials for Configuration Wizard
  • SQL Permission Role Requirement

• If the account permissions are correct but the error persists, check the schema ownership of the database objects involved.
• Ensure the schema is set to dbo for the procedure dbm_CreateFilegroup and related objects. You can verify and change the schema using SQL Server Management Studio (SSMS) with commands similar to:

-- 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.

ALTER SCHEMA dbo TRANSFER [schema_name].[dbm_CreateFilegroup];

Replace [schema_name] with the current schema name if different from dbo.

• After confirming permissions and correcting the schema, re-run the Configuration Wizard to complete the upgrade process.