LockTimeOut not working?

[wfvdijk]

I am running the integritycheck with 'CHECKTABLE' , @tablock = 'Y', a @LockTimeout of 5 and a @LockMessageSeverity of 10. However, when running and hitting a table which is being used I get error 5245 (which is almost the same as error 1222). Since this error is not handled in the stored procedure, it's always returning severity 16 resulting in a failed operation. Am I doing something wrong, or should I classify this as a bug? (using SQL 2022)

Date and time: 2026-04-13 16:35:01
Database context: [DBNAME]
Command: SET LOCK_TIMEOUT 5000; DBCC CHECKTABLE ('[dbo].[TABLENAME]') WITH ALL_ERRORMSGS, PHYSICAL_ONLY, TABLOCK
Msg 5245, Level 16, State 1, Line 1
Object ID 64719283 (object 'dbo.TABLENAME'): DBCC could not obtain a lock on this object because the lock request timeout period was exceeded. This object has been skipped and will not be processed.
Outcome: Failed
Duration: 00:00:05
Date and time: 2026-04-13 16:35:06

[olahallengren]

I have a feature called LockMessageSeverity: https://ola.hallengren.com/sql-server-index-and-statistics-maintenance.html#LockMessageSeverity

This basically changes the severity of lock timeouts and deadlocks from 16 to 10 to prevent the job from reporting failure. Currently it checks for (1205, 1222). I will add 5245 to the list of error numbers here as well.

As for why you get the error in the first place, I don't know. For that I would recommend opening a support case with Microsoft.

[olahallengren]

I have added 5245 as a locking error number. Thank you for reporting this issue.