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

by

Troubleshooting Guide: SQL Server Error 13176 (“Getting Data” Component Failure)

Why This Error Happens

Error 13176 in Microsoft SQL Server 2025 typically occurs when the Policy-Based Management (PBM) or SQL Server Agent component fails to retrieve configuration data due to a broken or inaccessible metadata cache. This is often triggered by corrupted MSDB system tables, insufficient permissions on the service account accessing the “Getting Data” component, or a mismatch between the SQL Server engine version and the Management Object Framework (SMO) libraries on Windows Server 2025 / Windows 11. In some cases, this error surfaces when WMI providers used by SQL Server to enumerate configuration data are not properly registered after an OS or SQL patch update.

Step-by-Step Resolution Guide

Step 1: Verify Service Account Permissions

  • Open SQL Server Configuration Manager and confirm the SQL Server Agent/Database Engine is running under a valid domain or managed service account.
  • Ensure the account has db_datareader rights on the msdb database.
  • Run the following query to check permissions:
  USE msdb;
  EXEC sp_helprotect NULL, 'ServiceAccountName';

Step 2: Re-register WMI Providers

  • On Windows Server 2025 / Windows 11, open an elevated Command Prompt.
  • Navigate to the SQL Server binary directory, typically:
    C:\Program Files\Microsoft SQL Server\170\Shared\
  • Re-register the WMI provider using:
  mofcomp sqlmgmproviderxpsp2up.mof
  • Restart the Windows Management Instrumentation (WMI) service.

Step 3: Repair the MSDB System Database

  • Stop the SQL Server service via Services.msc or:
  NET STOP MSSQLSERVER
  • Restart SQL Server in single-user mode using the -m startup parameter in Configuration Manager.
  • Run a consistency check:
  DBCC CHECKDB('msdb') WITH NO_INFOMSGS, ALL_ERRORMSGS;
  • Restart the service normally afterward.

Step 4: Update SMO and Native Client Libraries

  • Confirm you are running the latest SQL Server Management Objects (SMO) package compatible with SQL Server 2025.
  • Download and install the updated Microsoft ODBC Driver and Native Client from the official Microsoft Download Center.
  • Reboot the server to finalize library registration.

Alternative or Verification Steps

  • Open SQL Server Management Studio (SSMS), navigate to Management > Policy Management, and attempt to evaluate a policy; if no error 13176 appears, the fix was successful.
  • If the issue persists, use the SQL Server Error Log (ERRORLOG file located in MSSQL17.MSSQLSERVER\MSSQL\Log\) to cross-reference timestamps and isolate whether the fault lies in WMI, MSDB, or third-party management tools, then consider running a full repair installation via the SQL Server Installation Center.