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

by

Troubleshooting Guide: SQL Server Error 1080 — “The integer value %.*ls is out of range”

Why This Error Happens

This error typically occurs when SQL Server 2025 encounters a configuration value, parameter, or registry entry that exceeds the acceptable integer boundary defined for that setting. It is commonly triggered by corrupted or manually edited configuration files, invalid startup parameters, or registry keys that were modified outside of SQL Server Configuration Manager. In some cases, this also surfaces when a legacy configuration value from a previous SQL Server version is incompatible with new boundary limits enforced in SQL Server 2025 on Windows Server 2025 / Windows 11.

Step-by-Step Resolution Guide

Step 1: Identify the Source of the Invalid Integer Value

  • Open the SQL Server Error Log located at C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\Log\ERRORLOG to find the exact configuration key or parameter referenced alongside Error 1080.
  • Cross-reference the value with sys.configurations by running: SELECT name, value, value_in_use, maximum FROM sys.configurations;
  • Note any custom startup parameters passed via SQL Server Configuration Manager.

Step 2: Validate and Reset Registry Configuration Values

  • Open regedit and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQLServer
  • Inspect DWORD values for settings like AffinityMask, NetworkPacketSize, or RecoveryInterval — ensure none exceed their documented maximum range.
  • If a corrupted value is found, delete the key and allow SQL Server to regenerate it with default values on next restart.

Step 3: Reset sp_configure Values to Defaults

  • Open SQL Server Management Studio (SSMS) and run: EXEC sp_configure 'show advanced options', 1; RECONFIGURE;
  • Identify the offending parameter and reset it: EXEC sp_configure 'parameter_name', DEFAULT; RECONFIGURE WITH OVERRIDE;
  • Restart the SQL Server service via Services.msc or net stop MSSQLSERVER && net start MSSQLSERVER.

Step 4: Rebuild Startup Parameters in Configuration Manager

  • Open SQL Server Configuration Manager → SQL Server Services → right-click the instance → Properties → Startup Parameters tab.
  • Remove any manually added -T trace flags or custom parameters that contain unusually large or malformed integer values.
  • Apply changes and restart the SQL Server service to confirm the instance starts cleanly.

Alternative or Verification Steps

  • Verify the fix by checking the Windows Event Viewer (Application Log) and confirming Error 1080 no longer appears after the service restarts successfully.
  • If the issue persists, restore the master database from a last-known-good backup, as persistent integer range errors can indicate deeper corruption in system configuration tables.