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

by

Troubleshooting Guide: SQL Server Error 9655 – Transmission Queue Table Structure Inconsistency

Why This Error Happens

Error 9655 occurs when the internal system table structure of a Service Broker transmission queue becomes corrupted or inconsistent, typically caused by abrupt database shutdowns, disk-level I/O failures, or storage subsystem errors that interrupted a write operation mid-transaction. This can also surface after an improper failover in an Always On Availability Group where the transaction log was not fully synchronized before the queue metadata was committed. In rare cases, antivirus or backup software locking database files during active I/O on Windows Server 2025 can trigger partial writes that corrupt the internal queue schema.

Step-by-Step Resolution Guide

Step 1: Verify the Scope of Corruption

  • Open SQL Server Management Studio (SSMS) and run DBCC CHECKDB ('YourDatabaseName') WITH NO_INFOMSGS, ALL_ERRORMSGS; to confirm whether corruption is isolated to the transmission queue or affects other system tables.
  • Check the SQL Server Error Log (default path: C:\Program Files\Microsoft SQL Server\MSSQL17.MSSQLSERVER\MSSQL\Log\ERRORLOG) for correlating I/O or storage warnings around the same timestamp as Error 9655.
  • Note the exact queue name referenced in the error message (e.g., sys.transmission_queue) for targeted repair.

Step 2: Disable Service Broker Temporarily

  • Run ALTER DATABASE YourDatabaseName SET DISABLE_BROKER; to stop active message transmission and prevent further writes to the corrupted queue structure.
  • Confirm Service Broker is disabled by querying SELECT is_broker_enabled FROM sys.databases WHERE name = 'YourDatabaseName'; (result should return 0).
  • This step prevents additional data loss while repair operations are performed.

Step 3: Run Targeted Repair with DBCC CHECKDB

  • Put the database into single-user mode: ALTER DATABASE YourDatabaseName SET SINGLE_USER WITH ROLLBACK IMMEDIATE;
  • Execute DBCC CHECKDB ('YourDatabaseName', REPAIR_ALLOW_DATA_LOSS); — note this may clear orphaned or corrupted queue entries, so ensure a current backup exists first.
  • Revert to multi-user mode: ALTER DATABASE YourDatabaseName SET MULTI_USER;

Step 4: Restore from Backup if Repair Fails

  • If DBCC CHECKDB cannot resolve the inconsistency, restore the database from the last known good full backup using RESTORE DATABASE YourDatabaseName FROM DISK = 'E:\Backups\YourDatabaseName.bak' WITH REPLACE;
  • Apply subsequent transaction log backups to minimize data loss up to the point of corruption.
  • Re-enable Service Broker afterward with ALTER DATABASE YourDatabaseName SET ENABLE_BROKER;

Step 5: Check Storage and Driver Health

  • On Windows Server 2025, open Event Viewer (eventvwr.msc) and review the System log under Disk and NTFS sources for hardware-level warnings.
  • Update storage controller drivers via Device Manager and run chkdsk E: /f /r (replace E: with your data drive) during a maintenance window to rule out underlying disk corruption.

Alternative or Verification Steps

  • After remediation, re-run DBCC CHECKDB ('YourDatabaseName') WITH NO_INFOMSGS; and confirm it returns zero allocation or consistency errors, then monitor the SQL Server Error Log for 24–48 hours to ensure Error 9655 does not recur.
  • If corruption persists after repair and restore attempts, engage Microsoft Customer Support Services (CSS) with the DBCC CHECKDB output and a database backup for advanced forensic recovery.