What This Error Means
You're seeing ERROR_TRANSACTION_FREEZE_IN_PROGRESS (0X00001AB8) when trying to run a transaction that needs to freeze the database—typically a backup, snapshot, or replication sync. The message says it all: a freeze is already running, and SQL Server won't let you stack another one.
This is almost always a stuck freeze, not a legitimate concurrent operation. In 14 years of doing this, I've seen it happen when a backup job times out but doesn't clean up its freeze state, or when a user runs a manual BACKUP DATABASE while a maintenance plan is mid-run. The fix is straightforward—start simple, escalate only if needed.
Quick Fix (30 seconds): Find and Kill the Blocking Session
First, check if there's actually another freeze still running. Open SSMS and run this:
SELECT session_id, status, command, wait_type, last_wait_type
FROM sys.dm_exec_requests
WHERE command LIKE '%BACKUP%' OR command LIKE '%DBCC%';
If you see a session with a backup or DBCC command that's been sitting there for a while, that's your blocker. Kill it. Don't hesitate—transaction freezes are not something you want to leave dangling:
KILL <session_id>;
Wait 10 seconds, then retry your original operation. In most cases, this clears it. If not, move on.
Moderate Fix (5 minutes): Clear Orphaned Freeze States
Sometimes the session is already dead, but the freeze flag stuck. This happens when SQL Server crashes or the backup process is force-terminated. You'll see a spid that's no longer active, but the database still thinks a freeze is in progress.
First, check if any sessions are holding a freeze using this DMV:
SELECT request_session_id, resource_type, resource_description
FROM sys.dm_tran_locks
WHERE resource_type = 'DATABASE' AND resource_description LIKE '%FREEZE%';
If that returns nothing, try forcing a checkpoint to nudge the engine:
CHECKPOINT;
If that doesn't help, restart the SQL Server service. It's blunt, but it's the most reliable way to clear a freeze state. Open Services, right-click SQL Server (MSSQLSERVER), and select Restart. You'll lose any active connections, but this error usually happens during off-hours anyway.
Advanced Fix (15+ minutes): Check for Orphaned Backup Jobs or Snapshot Conflicts
If the error keeps coming back, you're dealing with a recurring conflict. Look for scheduled jobs that overlap. I've seen this exact error when a nightly full backup at 2:00 AM overlaps with a log backup that runs every 15 minutes—both try to freeze the database at the same instant.
Open SQL Server Agent, expand Jobs, and check the schedules. Look for any job that could start while another is mid-run. Fix the overlap by adjusting times or adding a condition to skip if a job is already running.
Another culprit: snapshot isolation. If you've got ALLOW_SNAPSHOT_ISOLATION turned on, long-running transactions can hold a freeze-like state. Check with:
SELECT name, snapshot_isolation_state_desc
FROM sys.databases;
If it's enabled and you're not using it, turn it off—it's a known source of freeze conflicts:
ALTER DATABASE YourDB SET ALLOW_SNAPSHOT_ISOLATION OFF;
Finally, if you're using a third-party backup tool (like Veeam or Commvault), check if it's hanging. These tools often use their own freeze commands, and a hung agent can leave the database in a freeze state. Restart the backup service and re-run the job.
When to Give Up and Call Support
If you've tried all this and the error still appears, you might have a bug in SQL Server itself. Check the version—there were known issues with freeze handling in SQL Server 2016 SP1 and early 2017 builds. If you're on one of those, apply the latest cumulative update. But honestly, that's rare. The steps above fix 99% of cases.
One last thing: don't bother with DBCC CHECKDB when this error appears. It's not a corruption issue, and running it will just add more locks and make the freeze worse.