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

by

Why This Error Happens

Error 5046 in SQL Server 2025 is typically an informational or configuration-state message indicating that a specific server or database property has been successfully modified, but it surfaces as an error when the property change conflicts with an existing session state, a locked configuration file, or insufficient permissions to persist the setting. This often occurs when multiple administrative sessions attempt to modify the same server property simultaneously, or when the SQL Server service account lacks write access to the configuration store on Windows Server 2025 / Windows 11. Corrupted metadata in the msdb or master database can also cause this message to appear repeatedly during property-set operations.

Step-by-Step Resolution Guide

Step 1: Verify the Property Change Context

  • Open SQL Server Management Studio (SSMS) and check the SQL Server Logs (Management > SQL Server Logs) for the full text surrounding Event ID 5046.
  • Identify which property (%ls) triggered the message — common ones include MaxServerMemory, RemoteAccess, or ClrEnabled.
  • Run EXEC sp_configure 'show advanced options', 1; RECONFIGURE; to confirm current configuration values.

Step 2: Check Permissions on Configuration Files

  • Navigate to C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\Binn\ and verify the SQL Server service account has Read/Write permissions.
  • Confirm the service account also has access to C:\ProgramData\Microsoft\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\Log\.
  • Use icacls from an elevated PowerShell prompt to reset permissions if needed:
  icacls "C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\Binn" /grant "NT SERVICE\MSSQLSERVER:(OI)(CI)F"

Step 3: Clear Conflicting Sessions and Reapply the Setting

  • Query sys.dm_exec_sessions to identify any other active sessions attempting to modify the same property.
  • Terminate conflicting sessions using KILL <session_id>;.
  • Reapply the property change using sp_configure or the relevant ALTER SERVER CONFIGURATION / ALTER DATABASE statement, then run RECONFIGURE WITH OVERRIDE;.

Step 4: Restart the SQL Server Service

  • Open Services.msc on Windows Server 2025 / Windows 11.
  • Restart SQL Server (MSSQLSERVER) and SQL Server Agent to flush cached configuration states.
  • Confirm the service starts cleanly without additional errors in the Windows Event Viewer under Application logs.

Alternative or Verification Steps

  • After restarting, re-run sp_configure or query the relevant system view (e.g., sys.configurations) to confirm the property value matches the intended setting and Error 5046 no longer appears in the SQL Server logs.
  • If the error persists, run DBCC CHECKDB against master and msdb to rule out metadata corruption as the underlying cause.