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

by

Troubleshooting Guide: SQL Server Error 3951 – Snapshot Isolation Mismatch

Why This Error Happens

This error occurs because a transaction was initiated under a standard isolation level (such as READ COMMITTED or REPEATABLE READ), but a statement within that same transaction attempted to execute using SNAPSHOT isolation. SQL Server 2025 does not allow the isolation level of an active transaction to be switched to SNAPSHOT mid-execution; the SET TRANSACTION ISOLATION LEVEL SNAPSHOT command must be issued before the BEGIN TRANSACTION statement. This is typically caused by application connection pooling reusing a session where isolation levels were not reset, or by stored procedures that assume a specific isolation context that the calling application does not honor.

Step-by-Step Resolution Guide

Step 1: Audit the Transaction Code Order

  • Locate the specific stored procedure or application code block referenced in the error’s database name (%.*ls).
  • Verify that SET TRANSACTION ISOLATION LEVEL SNAPSHOT; is placed strictly before the BEGIN TRAN keyword in the T-SQL script.
  • Check for any nested transactions where an outer transaction might have already started with a different isolation level.

Step 2: Enable Database-Level Snapshot Support

  • Confirm that the target database actually has the snapshot isolation framework enabled, as a disabled setting can sometimes cause conflicting session behaviors.
  • Run the following query in SQL Server Management Studio (SSMS) to check the status:
  SELECT name, snapshot_isolation_state_desc 
  FROM sys.databases 
  WHERE name = 'YourDatabaseName';
  • If the result shows OFF, enable it using: ALTER DATABASE YourDatabaseName SET ALLOW_SNAPSHOT_ISOLATION ON;

Step 3: Reset Connection Pooling Isolation Levels

  • Since connection pooling in IIS or .NET applications reuses sessions, ensure the application explicitly resets the isolation level at the start of every new logical transaction rather than relying on the default state of a pooled connection.
  • In your connection string (for .NET apps), ensure Enlist=false is set if you are manually managing distributed transactions to avoid ambient transaction scope conflicts.
  • Restart the IIS Application Pool or Windows Service via Server Manager on Windows Server 2025 to clear any hung sessions holding an incorrect isolation state.

Step 4: Isolate the Specific Query Batch

  • Use SQL Server Profiler or Extended Events (XEvents) to trace the exact batch text that triggers Error 3951.
  • Filter the trace by the Error event class with Error number 3951 to capture the exact T-SQL statement causing the mismatch.
  • Modify the specific query to run in a separate, dedicated transaction scope rather than inheriting the parent transaction’s isolation level.

Alternative or Verification Steps

  • Verification: Re-run the failed transaction after modifying the code order; check the SQL Server Error Log (via SSMS > Management > SQL Server Logs) to confirm Error 3951 no longer appears for that session ID.
  • Alternative: If modifying the application code is not immediately feasible, set the database’s default isolation level using a Resource Governor workload group to force READCOMMITTEDSNAPSHOT ON at the database level, which handles row versioning without requiring an explicit mid-transaction isolation switch.