SQL Server Errors or Failures Error: 3449 to Error: 3615



Error: 3449, Severity: 21, SQL Server must shut down in order to recover a database (database ID %d). The database is either a user database that could not be shut down or a system database. Restart SQL Server. If the database fails to recover after another startup, repair or resto,
Error: 3450, Severity: 10, Recovery of database ‘%.*ls’ (%d) is %d%% complete (approximately %d seconds remain). Phase %d of 3. This is an informational message only. No user action is required.,
Error: 3452, Severity: 10, Recovery of database ‘%.*ls’ (%d) detected possible identity value inconsistency in table ID %d. Run DBCC CHECKIDENT (‘%.*ls’).,

Error: 3453, Severity: 16, This version cannot redo any index creation or non-logged operation done by SQL Server 7.0. Further roll forward is not possible.,
Error: 3454, Severity: 10, Recovery is writing a checkpoint in database ‘%.*ls’ (%d). This is an informational message only. No user action is required.,
Error: 3456, Severity: 21, Could not redo log record %S_LSN, for transaction ID %S_XID, on page %S_PGID, allocation unit %I64d, database ‘%.*ls’ (database ID %d). Page: LSN = %S_LSN, allocation unit = %I64d, type = %ld. Log: OpCode = %ld, context %ld, PrevPageLSN: %S_LSN. Restore f,
Error: 3457, Severity: 21, Transactional file system resource manager ‘%.*ls’ failed to recover. For more information, see the accompanying error message, which determines the appropriate user action.,

Error: 3458, Severity: 16, Recovery cannot scan database “%.*ls” for dropped allocation units because an unexpected error has occurred. These allocation units cannot be cleaned up.,
Error: 3459, Severity: 16, Recovery of database “%.*ls” failed to redo a file add for file “%.*ls”. Please delete the file and retry.,
Error: 3505, Severity: 14, Only the owner of database “%.*ls” or someone with relevant permissions can run the CHECKPOINT statement.,
Error: 3604, Severity: 10, Duplicate key was ignored.,
Error: 3605, Severity: 16, Schema verification failed for database ‘%.*ls’.,
Error: 3606, Severity: 10, Arithmetic overflow occurred.,
Error: 3607, Severity: 10, Division by zero occurred.,
Error: 3608, Severity: 16, Cannot allocate a GUID for the token.,
Error: 3609, Severity: 16, The transaction ended in the trigger. The batch has been aborted.,
Error: 3611, Severity: 10, %hs SQL Server Execution Times:%hs CPU time not measured under fiber mode, elapsed time = %lu ms.,
Error: 3612, Severity: 10, %hs SQL Server Execution Times:%hs CPU time = %lu ms, elapsed time = %lu ms.,
Error: 3613, Severity: 10, SQL Server parse and compile time: %hs CPU time = %lu ms, elapsed time = %lu ms.,
Error: 3615, Severity: 10, Table ‘%.*ls’. Scan count %d, logical reads %d, physical reads %d, read-ahead reads %d, lob logical reads %d, lob physical reads %d, lob read-ahead reads %d.,

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.


Leave a Reply

Your email address will not be published. Required fields are marked *