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

by

Troubleshooting Guide: SQL Server Error 8128

Why This Error Happens

Error 8128 is a purely informational message generated by SQL Server 2025 whenever an extended stored procedure (XP) is invoked, logging the DLL name and version being used to service the call. It is not indicative of a failure, corruption, or permissions issue — it exists solely for auditing and diagnostic traceability. This message typically surfaces in the SQL Server Error Log or Extended Events trace when verbose logging levels are enabled, or when third-party/custom extended stored procedures are loaded into the sqlservr.exe process space.

Step-by-Step Resolution Guide

Step 1: Confirm the Message Is Informational

  • Open SQL Server Management Studio (SSMS) and navigate to Management > SQL Server Logs.
  • Locate the Error 8128 entry and verify the severity level — it should report as Severity 10 (Informational), not Severity 16 or higher.
  • Cross-reference the timestamp with any user-reported symptoms to confirm no actual failure accompanies it.

Step 2: Identify the Source Extended Stored Procedure

  • Run the following query to list registered extended stored procedures:
  • SELECT name, dll FROM sys.extended_procedures;
  • Note the %s placeholders in the message — these resolve to the XP name, DLL version, and procedure name, helping you trace which legacy component (e.g., xp_cmdshell, xp_logininfo, or a custom DLL) triggered the log entry.

Step 3: Adjust Logging Verbosity (Optional)

  • If the volume of Error 8128 messages is cluttering logs, reduce verbosity via SQL Server Configuration Manager > SQL Server Services > Startup Parameters.
  • Remove or adjust the -T3613 or related trace flags that control extended procedure logging detail.
  • Restart the SQL Server service (net stop MSSQLSERVER && net start MSSQLSERVER) for changes to take effect.

Step 4: Validate Extended Procedure DLL Integrity

  • On Windows Server 2025 or Windows 11, navigate to the SQL Server Binn directory, typically:
  • C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\Binn\
  • Confirm the DLL referenced in the message exists and matches the expected version using Get-Item <path> | Select-Object VersionInfo in PowerShell.
  • Replace or re-register any outdated DLL only if accompanied by a genuine error (not just the informational 8128 message).

Alternative or Verification Steps

  • Verify normal operation by executing the extended stored procedure manually (e.g., EXEC master..xp_fixeddrives;) and confirming it returns expected results without triggering Severity 16+ errors.
  • If logs remain noisy, suppress Error 8128 specifically using Extended Events filtering rules rather than disabling SQL Server logging entirely, preserving visibility into genuine issues.