Database Engine Errors
SQL Server diagnostic error codes organized by severity level and category. Each error includes error number, severity classification, and description.
Configure Client Protocols Troubleshoot connectivity issues in SQL Server 0200 Consistent Network Issue Connect to an Always On availability group listener Always On Failover Cluster Instances (SQL Se
The information below outlines the more common scenarios but isn't an exhaustive list of troubleshooting steps.
Description See the topic MSSQL_ENG003165 in SQL Server Books Online. 3166 16 No RESTORE DATABASE could not drop database '%ls'. Drop the database and then reissue the RESTORE DATABASE statement. 3167
Description 1001 16 No Line %d: Length or precision specification %d is invalid. 1002 16 No Line %d: Specified scale %d is invalid. 1003 15 No Line %d: %ls clause allowed only for %ls. 1004 16 No Inva
Description 1021 10 No FIPS Warning: Line %d has the non-ANSI statement '%ls'. 1022 10 No FIPS Warning: Line %d has the non-ANSI clause '%ls'. 1023 15 No Invalid parameter %d specified for %ls. 1024 1
Description 1040 15 No The value %d used with MAX_OUTSTANDING_IO_PER_VOLUME is not valid; MAX_OUTSTANDING_IO_PER_VOLUME must be greater than 0 and less than or equal to %d.
Description 1059 15 No Cannot set or reset the 'parseonly' option within a procedure or function.
'Description 1081 16 No %s does not allow specifying the database name as a prefix to the assembly name. 1082 15 No "%.*ls" does not support synchronous trigger registration. 1083 15 No OWNER is not a '
Description Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.
The examples with OS 483 and 1117 indicate I/O device failure. Check for malfunction or damage of the storage media.
Description elastic pool cannot exceed (%d) MBs. 1133 17 Yes The managed instance has reached its storage limit. The storage usage for the managed instance cannot exceed (%d) MBs. 1134 17 Yes Cannot r
Deadlocks are in most cases application-related issues and require application developers to make code changes. One approach when you receive is to execute the queries again.
You enabled Trace flags 1211 , 1224 , or both on your SQL Server to control lock escalation behavior, and you're executing queries that require many locks. If you suspect that SQL Server can't allocat
Description 1213 21 Yes Error spawning Lock Monitor thread: %ls 1214 17 Yes Internal Error. There are too many parallel transactions.
Description reasons including transient service failure. 1401 21 Yes Startup of the database-mirroring master thread routine failed for the following reason: %ls.
Description command when the remote database is started. 1414 16 No The database is being closed before database mirroring is fully initialized. The ALTER DATABASE command failed.
Description command failed. 1430 16 No Database '%.*ls' is in an unstable state for removing database mirroring, so recovery may fail. Verify the data after recovery.
In most cases, you connect to the Database Engine on another computer by using the TCP protocol. To get the TCP port of the instance, follow these steps: 1.
Description 1444 10 Yes Bypassing recovery for database '%ls' because it is marked as a mirror database, which cannot be recovered. This is an informational message only. No user action is required. 1
Output If you run into this scenario, follow the steps in this article to resolve: OS errors 665 and 1450 are reported for SQL Server files In this case, the underlying OS indicates the disk device h
Description Verify that the server is connected, and try again. 1457 23 Yes Synchronization of the mirror database, '%.*ls', was interrupted, leaving the database in an inconsistent state. The ALTER D
'Description operations are not allowed on a database that is participating in a database mirroring session or in an availability group. 1469 16 No Database "%.*ls" is an auto-close database on one of '
Description column of the sys.database_mirroring catalog view.
Description duplicate key value is %ls. 1509 20 Yes Row comparison failed during sort because of an unknown data type on a key column. Metadata might be corrupt. Contact Technical Support. 1510 17 No
Description 1702 16 No CREATE TABLE failed because column '%.*ls' in table '%.*ls' exceeds the maximum of %d columns.
Description 1721 16 No Altering table '%.*ls' failed because the row size using vardecimal storage format exceeds the maximum allowed table row size of %d bytes. 1722 16 No Cannot %S_MSG %S_MSG '%.*ls
Description cannot be added to a table if the table contains a sparse column. 1735 16 No Duplicate range-partitioning function specified for the table being created. Remove one of the range-partitioni
Description 1758 16 No Only a single constraint can be added or dropped online with no other operations in the same statement.
Description 1775 16 No Cannot create foreign key '%.*ls' because it references object '%.*ls' whose PRIMARY KEY index '%.*ls' is disabled.
If you cannot re-attach a database that resides on network-attached storage, a message like this may be logged in the Application log. This problem occurs because SQL Server resets the file permission
'Description 1826 16 No User-defined filegroups are not allowed on "%ls". 1827 16 No CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed l'
Description action is required. 1844 16 No %ls is not supported on %ls.
Description 1858 16 No Could not create snapshot database because user database is still in recovery. 1859 16 No Create database is not allowed in the model database context. Switch context to other d
Description 1914 16 No Index cannot be created on object '%.*ls' because the object is not a user table or view. 1915 16 No Cannot alter a non-unique index with ignore_dup_key index option. Index '%.*
Description 1935 16 No Cannot create index. Object '%.*ls' was created with the following SET options off: '%.*ls'. 1937 16 No Cannot create %S_MSG on view '%.*ls' because it references another view '
Description 1952 16 No Index on view '%.*ls' cannot be created because the view contains an imprecise expression in a join.
Description 1971 16 No Cannot disable index '%.*ls' on table '%.*ls'. Permission denied to disable foreign key '%.*ls' on table '%.*ls' that uses this index.
Description length of '%d' bytes. 1985 16 No Cannot create %S_MSG on view '%.*ls'. It contains one or more XML data type methods. 1986 10 No Cannot replace non-hypothetical index '%.*ls' with a hypoth
didn't include functionality, so the error isn't caught before upgrade unless is specifically executed against the database in SQL Server 2000 (8.x). You might see any of the following errors together
Walters Rob Tool Designer 2001-08-09 A unique index can not be created on the column combinations or , because of duplicate values in the rows. Less obvious is the potential for a uniqueness violation
prevent the use of the machine account for remote authentication requests. , select the option if the setting is disabled, and then select . Note : As detailed on the tab, this policy is enabled in Wi
'Description ''publication_compatibility_level'' of less than "90RTM" (SQL Server 2005). Specify a ''publication_compatibility_level'' greater than or equal to "90RTM" by using sp_addmergepublication or sp'
When SQL Server is configured for mixed mode authentication, and an ODBC connection uses named pipes, and the credentials the client used to open the named pipe are used to automatically impersonate t
committed process memory. As a result this warning is printed.
To check the issue, follow these steps: 1. If a network trace isn't available, check the functions value under this registry key: Use the following PowerShell command to find the TLS functions. PowerS
'2. Select the SQL Server instance in SQL Server Services . 3. Right-click the instance, and then select . 4. Select the tab. 5. Use the field to add the trace flag. Type "-T902" (without quotes) and c'
For more information about this scenario, see Applications experience forcibly closed TLS connection errors when connecting SQL Servers in Windows . In systems with high workloads on SQL Server 2017 a
Ensure you configure TLS correctly for SQL Server. For information on updates needed, see TLS 1.2 support for Microsoft SQL Server 3. Another common issue is the misconfiguration of TLS/SSL certificat
see: Diagnostic Connection for Database Administrators . To check whether DAC is enabled, review the SQL Server error log. Look for a message similar to this example: 2020-02-09 16:17:44.150 Server De
Applies to: SQL Server Product Name SQL Server Event ID 3183 Event Source MSSQLSERVER Component SQLEngine Symbolic Name LDDB_PAGE_ERROR_DURING_RESTORE Message Text RESTORE detecte
Applies to: SQL Server Product Name SQL Server Event ID 42108 Event Source MSSQLSERVER Component SQLEngine Symbolic Name GATEWAY_SQL_POOL_CONNECT_ACTIVATION_BLOCKED Message Text C
Applies to: Azure SQL Managed Instance Product Name SQL Server Event ID 41962 Event Source MSSQLSERVER Component SQLEngine Message Text Operation was aborted as replication to Azu
non-operational state. This can lead to the lease timeout expiration between SQL Server and the cluster processes.
Description 2203 16 No %sOnly 'http://www.w3.org/2001/XMLSchema#decimal?', 'http://www.w3.org/2001/XMLSchema#boolean?' or 'node()*' expressions allowed as predicates, found '%ls' 2204 16 No %sOnly 'ht
Description 2260 16 No %sThere is no element named '%ls' 2261 16 No %sThere is no element named '%ls' in the type '%ls'.
Description 2292 16 No %sWhen a type with simple content restricts a type with mixed content, it must have an embedded simple type definition. Location: '%ls'.
Description 2321 16 No %sFacets cannot follow attribute declarations. Found facet '%ls' at location '%ls'. 2322 16 No %sThe element type is not a subclass of the substitution group's head 2323 16 No %
Description 2350 16 No %sInvalid XML element content 2351 16 No %sExpected 'first' or 'last' 2353 16 No %s'to' or 'insert' or 'delete' expected 2354 16 No %sInvalid source character encoding 2355 16 N
Description 2373 16 No %s%ls is not supported with constructed XML 2374 16 No %sA node or set of nodes is required for %ls 2375 16 No %sAggregate function '%ls' expects a sequence argument 2376 16 No
If you have persistent data corruption problems, try to swap out different hardware components to isolate the problem.
'Description 2530 16 No The index "%.*ls" on table "%.*ls" is disabled. 2531 16 No Table error: object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) B-tree level mismatch, pa'
If you have persistent data corruption problems, try to swap out different hardware components to isolate the problem.
caching enabled on the disk controller. If you suspect write-caching to be the problem, contact your hardware vendor. Finally, you might find it useful to switch to a new hardware system. This switch
'Description 2549 10 No DBCC: Defrag phase of index ''%.*ls'' is %d%% complete. 2550 16 No The index "%.*ls" (partition %ld) on table "%.*ls" cannot be reorganized because it is being reorganized by anot'
Description 2568 16 No Page %S_PGID is out of range for this database or is in a log file. 2569 16 No Parameter %d is incorrect for this DBCC statement: %ls. 2570 16 No Page %S_PGID, slot %d in object
Invalid or out-of-range data may have been stored in the SQL Server database for the following reasons: Invalid data was inserted into SQL Server through remote procedure call (RPC) events.
Description 2587 16 No The invalid partition number %ld was specified. 2588 16 No Cannot find partition number %ld for index ID %d, object ID %d.
Description 2703 16 No Cannot use duplicate column names in the partition columns list. Column name '%.*ls' appears more than once. 2704 16 No Invalid partition scheme '%.*ls' specified. 2705 16 No Co
Description DROP_EXISTING is used, the column could be part of a new or old index. The operation must be performed offline. 2726 16 No Partition function '%.*ls' uses %d columns which does not match w
Description 2748 16 No Cannot specify %ls data type (parameter %d) as a substitution parameter.
Description 2774 16 No Collation ID %d is invalid. 2775 16 No The code page %d is not supported by the server. 2778 16 No Only System Administrator can specify %s option for %s command. 2779 16 No The
Description removing column from index or statistics key, marking computed column persisted, or using non-CLR-derived column in key. 2799 16 No Cannot create index or statistics '%.*ls' on table '%.*l
1. Determine the port your SQL instance is running on, see Get the TCP port of the instance . 2. Try to connect to the named instance by using the port number appended to the server name in the format
Description 3001 16 No obsolete 3002 16 No Cannot BACKUP or RESTORE a database snapshot. 3003 10 No This BACKUP WITH DIFFERENTIAL will be based on more than one file backup.
Description MB/sec). 3015 10 No %hs is not yet implemented. 3016 16 No Backup of file '%ls' is not permitted because it contains pages subject to an online restore sequence.
, State: 1. <Datetime> Backup BACKUP failed to complete the command BACKUP DATABASE MyDatabase WITH DIFFERENTIAL. Check the backup application log for detailed messages.
Description 3031 16 No Option '%ls' conflicts with option(s) '%ls'. Remove the conflicting option and reissue the statement.
Description 3047 16 No The BackupDirectory registry key is not configured correctly. This key should specify the root path where disk backup files are stored when full path names are not provided. Thi
1. Terminate your backups and ensure previous backups for this database aren't overwritten or lost 2. Run a full DBCC CHECKB against the database for which the backup failed with . Don't use with 3. R
Description 3061 16 No The restart-checkpoint file '%ls' could not be opened. Operating system error '%ls'. Make the file available and retry the operation or, restart the RESTORE sequence. 3062 16 No
Description device type. 3079 16 No Could not find the blob file %.*ls. Please make sure that the file name points to a valid blob file. 3080 16 No Invalid Backup Path.
Description 3097 16 No The Backup cannot be performed because the existing media set is formatted with an incompatible version.
Description 3109 16 No Master can only be restored and fully recovered in a single step using a full database backup. Options such as NORECOVERY, STANDBY, and STOPAT are not supported. 3110 14 No User
'Description 3128 16 No File ''%ls'' has an unsupported page size (%d). 3129 16 No The contents of the file "%ls" are not consistent with a transition into the restore sequence. A restore from a backup s'
Description 3144 16 No File '%.*ls' was not backed up in file %d on device '%ls'. The file cannot be restored from this backup set.
'trying to restore the backup. If the builds are different, the statement issues a "3168" error message, and the restore operation terminates abnormally. Some scenarios in which this problem might occu'
Description 3182 16 No The backup set cannot be restored because the database was damaged when the backup occurred. Salvage attempts may exploit WITH CONTINUE_AFTER_ERROR. 3183 16 No RESTORE detected
Description 3197 10 Yes I/O is frozen on database %ls. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup. 3198 10 Yes I/O was resumed on database %ls. No
Description 3218 16 No Backup mirroring is not available in this edition of SQL Server. See Books Online for more details on feature support in different SQL Server editions.
'Description 3235 16 No The file "%.*ls" is not part of database "%ls". You can only list files that are members of this database. 3236 16 No Write to S3 object storage device %ls failed. Device has re'
Description 3255 16 No The data set on device '%ls' is a SQL Server backup set not compatible with this version of SQL Server.
'Description 3271 16 No A nonrecoverable I/O error occurred on file "%ls:" %ls. 3272 16 No The ''%ls'' device has a hardware sector size of %d, but the block size parameter specifies an incompatible over'
Description 3292 16 No A failure occurred while attempting to execute Backup or Restore with a URL device specified. Consult the operating system error log for details.
This error can be caused by a transient condition that existed on the system during an attempt to recover a database.
This error can be caused by a transient condition that existed on the system during an attempt to recover a database.
Description 3316 21 Yes During undo of a logged operation in database '%.*ls', an error occurred at log record ID %S_LSN. The row was not found.
This error can be caused by a transient condition that existed on the system during a given attempt to start up the server instance or to recover a database. This error can also be caused by a permane
Description known good backup. If errors are not corrected or expected, contact Technical Support. 3415 16 Yes Database '%.*ls' cannot be upgraded because it is read-only, has read-only files or the u
To find the cause of the issue, follow these steps: 1. Locate and open the SQL Server Errorlog . 2.
In certain situations SQL Server attempts to restart the database at runtime and perform recovery, or it may restart itself (the entire service).