How to fix Error 5043 on Windows Server 2025 / Windows 11

by

Troubleshooting Guide: SQL Server Error 5043

Why This Error Happens

Error 5043 occurs when SQL Server cannot locate a specified resource—such as a filegroup, partition scheme, partition function, or configuration object—within the referenced database or scope. This typically stems from a mismatched or misspelled object name in a T-SQL command, a filegroup that was dropped or never created, or metadata corruption following an incomplete restore, upgrade, or migration process. It can also surface when scripts written for one database are executed against another database that lacks the referenced object.

Step-by-Step Resolution Guide

Step 1: Verify the Exact Object Name and Scope

  • Run SELECT name FROM sys.filegroups; (or sys.partition_schemes / sys.partition_functions depending on the error context) to confirm the exact name SQL Server expects.
  • Check for case sensitivity or trailing whitespace issues if the instance uses a case-sensitive collation.
  • Confirm you are connected to the correct database using SELECT DB_NAME(); before re-running the failing command.

Step 2: Cross-Check the Script Against the Target Database

  • Open the script that triggered Error 5043 and compare the referenced object name against the output from Step 1.
  • If the script was copied from another environment (e.g., staging to production), update the filegroup/partition names to match the current database’s actual schema.
  • Re-run the corrected statement using SQL Server Management Studio (SSMS) 21 or sqlcmd on Windows Server 2025.

Step 3: Inspect for Metadata Corruption

  • Run DBCC CHECKDB('YourDatabaseName') WITH NO_INFOMSGS, ALL_ERRORMSGS; to rule out underlying corruption in system catalogs.
  • If corruption is found, review the latest clean backup and restore it to a test instance to confirm object integrity.
  • Check the SQL Server Error Log (C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\Log\ERRORLOG) for related warnings around the time the object was last modified or dropped.

Step 4: Rebuild or Recreate the Missing Object

  • If the filegroup or partition function was mistakenly dropped, recreate it using ALTER DATABASE YourDB ADD FILEGROUP [FilegroupName];.
  • For partition schemes, re-issue the original CREATE PARTITION FUNCTION and CREATE PARTITION SCHEME statements from your deployment scripts.
  • Ensure the SQL Server Agent service account has appropriate permissions under Services.msc on Windows Server 2025 to execute DDL changes.

Alternative or Verification Steps

  • Re-execute the original failing query or stored procedure and confirm it completes without raising Error 5043 in SSMS or the Windows Event Viewer (Application log, source “MSSQLSERVER”).
  • If the issue persists, restore a known-good backup to a separate instance and compare sys.filegroups and sys.partition_schemes output against production to identify what’s missing.