MSSQL error table

MSSQL error table
Error Code 3000-3999
Error severity description (message text)
3009 16 failed to insert backup or restore history/detailed records in the MSDB database. This may indicate a problem with the MSDB database. The backup/restore operation is still successful.
3011 all backup devices must belong to the same category (such as disk and tape ).
3013 16% 1! The operation is terminated abnormally.
3014 10% 1! % 2 is successfully processed! Page, spent % 3 !. % 4! Seconds (% 5 !. % 6! MB/second ).
3015 10% 1! Not implemented yet.
3016 since the backup or restoration operation was interrupted, database ''% 2! ''File'' % 1! ''Deleted or shrunk. This operation cannot be restarted.
3017 failed to start the interrupted backup or restoration operation again. For more information, see SQL server error logs.
3018 there are no interrupted backup or restoration operations that can be restarted. Remove the restart clause and then issue the statement again.
3019 16 this checkpoint file is another backup or restoration operation. Remove the restart clause and then issue the statement again.
3020 the backup operation cannot be restarted because the log has been truncated. Remove the restart clause and then issue the statement again.
3021 the backup or restoration operations cannot be performed within the transaction.
3023 16 database backup and file operations (such as alter database add file) must be serialized. Issue the statement again after the current backup or file operation is complete.
3024 a full backup can only be performed on the master database. Use Backup database to back up the entire master database.
3025 the database name is missing. Issue the statement again and specify a valid database name in the statement.
3026 16 database ''% 2 not found in sysfilegroups! ''File group ID % 1 !.
3027 16 database ''% 3 not found in sysfilegroups! ''File group'' % 1! ''.
3028 the checkpoint file is invalid. Failed to restart operation. Remove the restart option and issue the statement again.
3031 16 option ''% 1! ''And option'' % 2! ''Conflict. Delete the conflicting option and then issue the statement again.
3032 16 one or more options (% 1 !) This statement is not supported. Please refer to the documentation for the supported options.
3033 16 backup database cannot be used for databases opened in emergency mode.
3034 the file to be processed is not selected. You may have selected one or more file groups without any members.
Database ''% 1 cannot be executed in 3035 16! ''Differential backup because the current database backup does not exist. Remove the with differential option and re-issue the backup database to perform the full backup of the database.
3036 16 database ''% 1! ''In STANDBY state (set by executing restore with standby), the backup can be performed only after the entire loading sequence is complete.
3037 16 the minimum logging operation has occurred before this with restart command. Remove with restart and issue the backup statement again.
3038 16 file name ''% 1! ''Is invalid when used as the backup device name. Use a valid file name to re-issue the backup statement.
3039 16 file ''% 1 cannot be executed! ''Differential backup because the current file backup does not exist. Remove the with differential option and re-issue the backup database.
3040 An error occurred while notifying the backup to the copy operation. The backup will continue, but the replication environment should be checked.
3041 16 backup failed to complete command % 1!
3101 because the database is in use, it cannot obtain access to the database.
3108 when trying to restore the master database, you must use the Restore database in single-user mode.
3110 14 the user does not have a Restore database ''% 1! ''Permission.
3112 16 when the server is in single-user mode, it cannot restore any database other than the master database.
3113 21 in database ''% 1! '''Sysusers does not have any database owner (DBO) entries.
3114 21 no database ''% 1 in sysdatabases! .
3123 the database name ''% 1 specified for the backup or restoration operation! ''Is invalid.
3127 16 temporary message: the backup set does not contain the file ''% 1! ''Page.
File ''% 1 is not supported in 3128 16! ''Page size (% 2 !).
3129 16 temporary message: file ''% 1! ''Size has exceeded % 2! Bytes changed to % 3! Bytes.
3132 16 database ''% 1! ''Media set has % 2! Only % 3 members are provided! . All members must be provided.
3133 16 device ''% 1! The volume on ''is not a member of the Media family.
3135 16 file ''% 1! The backup set in ''is from % 2! Created, cannot be used for this restore operation.
3136 16 unable to change device ''% 1! The backup on ''is applied to the database'' % 2! ''.
One or more files in the 3138 16 backup set are no longer database ''% 1! .
3140 16 failed to adjust file ''% 1! .
3141 16 the database to be restored was previously named ''% 1! ''. Issue the statement again and use the with replace option to override the database ''% 2! ''.
3142 16 cannot be found in the existing ''% 2! ''Restore file'' % 1! ''. Re-issue the restore statement and use with replace to overwrite the existing file.
3143 16 device ''% 1! The dataset on ''is not an SQL Server backup set.
3144 16 file ''% 1! ''Device not backed up ''% 4! ''File % 3! . The file cannot be restored from this backup set.
3145 the stopat option is not supported for restore databases. You can use the stopat option for restore log.
3146 after the backup operation is performed, no new restored files have been changed, so further recovery is not required. The database can be used now.
3147 you are not allowed to back up or restore the tempdb database.
3148 16 media recovery for alter database has not yet been implemented. The database cannot be rolled forward.
3150 the master database has been restored successfully. Disabling SQL Server.
3151 21 failed to restore the master database. Use the rebuildm utility to recreate the master database. Disabling SQL Server.
3234 15 logical file ''% 1! ''Not database'' % 3! . Use restore filelistonly to list logical file names.
3241 16 device ''% 1! The structure of the Media family on ''is incorrect. SQL Server cannot process this media family.
3242 16 device ''% 1! ''File is not a valid Microsoft tape format backup set.
3243 16 device ''% 1! The media family on ''is in version % 2 !. % 3! . SQL Server supports version % 4 !. % 5 !.
3244 16 descriptor block size exceeds % 1! Bytes. Use a short name and/or description string, and then try the operation again.
3245 16 failed to convert between a common string and a unicode string, % 1 !.
3246 16 device ''% 1! . Use the init option to re-issue the statement to overwrite the media.
3247 16 device ''% 1! ''Media Serial number of the volume (% 2 !) Error. Please retrieve this volume and insert volume % 3 !.
3248 25 >>> volume switch <(not used for output !)
3249 16 device ''% 1! ''Is the continuation volume of the Backup set. Remove the volume and insert the volume that contains the start part of the Backup set.
3250 16 value ''% 1! ''Is not in parameter % 2! .
3251 10 devices ''% 1! . The device is re-applied to one of the other families.
The value provided by 16 block size parameters of 3253 must be the power of 2.
3254 16 device ''% 1! .
3255 16 device ''% 1! The dataset on ''is an SQL Server backup set, but this backup set is not compatible with this version of SQL Server.
3256 16 device ''% 1! The backup set on ''is terminated when it is created. The backup set is incomplete. The restore sequence has ended abnormally.
3257 16 disk volume ''% 1! . The database still needs % 2! Bytes available space, but only % 3! Bytes available.
3258 16 device ''% 1! The volume on ''belongs to another media set.
3259 16 device ''% 1! The volume on ''is not part of a multi-family media set. Backup with format can be used to construct a new media set.
3260 the internal buffer is full.
3261 SQL Server cannot use virtual device configuration.
3262 the backup set is valid.
3263 16 unable to change device ''% 1! . Its serial number is % 2 !, % 3 of the current media set !. Please insert a new volume, or the serial number is % 4! . % 5 of the current media set !.
3264 16 this operation has not been performed to the extent that restart is allowed. Remove the restart Qualifier and then issue the statement again.
3265 16 the logon does not have sufficient permissions. Virtual_device can be used for backup or restore only when the SysAdmin role is qualified.
3266 10 ''% 1! The backup data in ''is incorrectly formatted. The backup cannot be appended, but the existing backup set may still be available.
3267 the UMS scheduling program cannot be created due to insufficient resources.
The backup file ''% 1 cannot be used in 3268 16! '', Because the size of the slice used to format the file is % 2 !, The slice size of the current device is % 3 !.
3269 files cannot be restored ''% 1! '', Because the size of the slice used to write the file is % 2 !, Currently, ''% 3! ''The slice size of the device is % 4 !.
3270 internal consistency error occurs. Contact the technical support staff for assistance.
3271 16 in file ''% 1! .
3272 16 ''% 1! ''The hardware sector size of the device is % 2 !, However, the block size parameter specifies the incompatible substitution value % 3 !. Use a compatible block size value to issue the statement again.
The value provided by the 3273 16 buffercount parameter must allow each backup device to have at least one buffer zone.
3274 16 pairs of devices % 1! The check value calculated by the backup set on is incorrect. The backup set cannot be restored.
3275 16 I/O Request 0x % 08x I/O Verification Failed. See the description in the error log.
3276 16 with snapshot can be used only when with snapshot is used during database creation.
3277 16 with snapshot must be used only for one virtual device.
3278 16 encrypted string % 1! Failed
3279 access denied due to wrong password
3280 16 backup on the original device is not supported. ''% 1! ''Is the original device.
3281 16 at ''% 1! .
3301 21 invalid log records found in transaction logs (logop % 1 !).
3313 21 restore database ''% 1! . The error location is in log ID % 3 !.
3314 21 undo database ''% 1! . The error location is in log ID % 3 !.
3315 process % 1 during rollback! It should be in transaction % 7! Database ''% 5 under control! ''Row % 4! The level is % 3! , Mode % 2! .
3405 10 recovering database ''% 1! ''.
% 1 rolled before 3406! Transactions (in database ''% 2! ''(% 4 !) ).
3407 10 rolled back % 1! Transactions (in database ''% 2! ''(% 4 !) ).
3408 the restoration is complete.
3413 21 Database ID % 1 !. Failed to mark the database as questionable. Getnext NC scan for sysdatabases. dbid failed.
3414 10 database ''% 1! ''(Database ID % 3 !) Failed to recover. Contact the technical support staff.
3415 16 database ''% 1! ''Is read-only or contains read-only files. You can upgrade the database only after writing.
3417 21 the master database cannot be restored. Exiting.
3429 10 warning: Transaction % 1 cannot be determined! (Name: ''% 2! '', In database'' % 4! '', Database ID % 6 !) Because the coordinated database cannot be opened (Database ID % 7 !). It is assumed that the transaction has been committed.
3430 10 warning: Transaction % 1 cannot be determined! (Name: ''% 2! '', In database'' % 4! '', Database ID % 6 !) Because of the database coordination (Database ID % 7 !) This result is not included. It is assumed that the transaction has been committed.
3431 21 failed to restore database ''% 1 because transaction results could not be parsed! ''(Database ID % 3 !).
3432 16 warning: syslanguages is missing.
3433 16 names have been truncated to ''% 1! ''. The maximum name length is % 3 !.
3434 20 the sorting order or region settings cannot be changed. Shutting down the server. Restart SQL Server to use the unchanged sorting order.
3435 20 because a user object or user database exists, you cannot change the sorting order or region settings.
3436 database reconstruction failed ''% 3! ''Table'' % 1! ''Index.
3437 21 restore database ''% 1! ''Error. Failed to connect to MSDTC to check transaction % 3! .
3438 10 database ''% 1! ''(Database ID % 3 !) Recovery failed because the first lsn of the transaction is not equal to the LSN in the checkpoint. Contact the technical support staff.
3439 10 database ''% 1! ''(Database ID % 3 !). DBCC recoverdb statement failed due to the preceding error.
3440 21 Database ''% 1! ''(Database ID % 3 !). The DBCC recoverdb statement can only run after the restore statement with the norecovery option is used.
3441 21 Database ''% 1! ''(Database ID % 3 !). The restore statement failed to access the file ''% 4! ''. Error: ''% 5! ''.
3442 21 Database ''% 1! ''(Database ID % 3 !). The size of the Undo file is insufficient.
3443 21 Database ''% 1! ''(Database ID % 3 !) Although marked as standby or read-only, it has been changed. The restore log statement cannot be executed.
3445 21 file ''% 1! ''Not database'' % 2! '', Database ID % 4 !.
3450 10 database ''% 1! ''(% 3 !) Recovery completed % 4! % (About % 5 yet! Seconds) (% 6! (Three phases in total ).
3604 duplicate keys are ignored.
3605 duplicate rows are ignored.
3606 10 Arithmetic overflow.
3607 a division-by-zero error occurs.
The GUID cannot be assigned to the token in 3608 16.
3612 10% 1! SQL Server execution time: % 2! CPU time = % 3! Millisecond, time consumed = % 4! Milliseconds.
3613 10 SQL Server Analysis and Compilation Time: % 1! CPU time = % 2! Millisecond, time consumed = % 3! Milliseconds.
3615 10 Table ''% 1! ''. Scan count % 3 !, Logical read % 4! Times, physical read % 5! Times, pre-read % 6! Times.
3618 10 the transaction has been terminated.
3619 10 failed to write the database ID % 1 because the log space is exhausted! Checkpoint record in.
3620 10 because the log space is exhausted, the log space in the database ''% 1! . When the database owner successfully performs the database checkpoint operation, the automatic execution of the checkpoint will continue. Release some space or expand the database size, and then run the checkpoint statement.
Statement 3621 10 has been terminated.
A domain error occurs on 3622 10.
3625 20 has not implemented ''% 1! ''.
3627 failed to create a working thread.
3628 a floating point exception occurs in the user process. The current transaction has been canceled.
3629 10 SQL Server is % 1! Concurrent queries are optimized. % 2! Queries exceed this limit, so the performance may be adversely affected.
3630 10 from % 1! % 2! Number of concurrent violations

3631 concurrent violations will write SQL server error logs.
3632 concurrent violations will not write SQL server error logs.
3701 11 failed % 1! % 2! ''% 3! ''Because it does not exist in the system directory.
% 1 cannot be removed in 3702 16! ''% 2! ''Because it is currently in use.
3703 16 cannot be separated % 1! ''% 2! ''Because it is currently in use.
3704 16 users are not in % 1! ''% 2! .
3705 16 failed to drop % 1! Used for ''% 2! ''Because'' % 4! ''Is % 6 !. Use drop % 7 !.
3708 16 failed % 1! % 2! ''% 3! ''Because it is SYSTEM % 5 !.
% 1 cannot be removed in 3716 16! ''% 2! ''Because it is bound to one or more % 4! .
3718 11 failed to remove index ''% 1! ''Because the table or clustered index entries cannot be found in the system table sysindexes.
3723 16 the index ''% 1! ''Explicitly uses drop index. This index is being used for % 3! Constraint.
3724 16 failed % 1! % 2! ''% 3! ''Because it is used for replication.
3725 16 constraint ''% 1! ''Forward table ''% 3! ''Foreign key constraint'' % 5! ''Reference.
The object ''% 1 could not be removed in 3726 16! ''Because the object is being referenced by a foreign key constraint.
3727 constraints cannot be removed. See the preceding error.
3728 16 ''% 1! ''Is not a constraint.
3729 16 failed % 1! ''% 2! ''Because the object'' % 4! ''Is referencing it.
3733 16 constraint ''% 1! ''Does not belong to table'' % 3! ''.
% 1 cannot be removed in 3736 16! ''% 2! ''Because it is used for distribution.
3737 16 failed to delete file ''% 1! ''. For more information, see SQL server error logs.
3738 deleting database file ''% 1! ''.
3739 15 failed % 1! Index ''% 2! ''Because the index is not a statistical set.
3902 13 The commit transaction request does not have the corresponding begin transaction.
3903 13 the rollback transaction request does not have the corresponding begin transaction.
3904 21 unable to undo logical Page % 1! Split, the logical page is located in the object ''% 2! '', Database'' % 4! . The total data contained in the split two pages is more than the data that one page can hold.
3906 16 failed in database ''% 1! '', Because the database is read-only.
3908 16 failed in database ''% 1! '', Because the database is in avoidance recovery mode.
The session bound to the token 3909 is invalid.
3910 16 other sessions are using the transaction context.
3912 when the server is not in an XP call, it cannot be bound with an XP token.
3914 16 Data Type ''% 1! ''Is invalid for the transaction name or retention point name. The data types are char, varchar, nchar, and nvarchar.
3915 the rollback statement cannot be used in the insert-exec statement.
3916 16 The commit statement cannot be used in the insert-exec statement, unless the begin transaction statement is used first.
3917 16 sessions are bound to the transaction context in use. Other statements in the batch processing are ignored.
The 3918 16 statement must be executed in the context of the user transaction.
3919 a transaction cannot be registered because the transaction has been committed or rolled back.
The 3920 with Mark option applies only to the first Tran in TRAN mark statement. This option is ignored.
3921 if no active transaction exists, the transaction token cannot be obtained. Please re-issue this statement after starting the transaction
3922 a transaction cannot be registered because the transaction does not exist.
3923 10 failed to pair database ''% 1! ''Use the transaction tag. The database has large-capacity log records that have not been backed up. This flag is ignored.
3924 10 when attempting to bind to a new transaction, the session is registered to the active user transaction. The session has been detached from the previous user transaction.
3925 16 invalid transaction tag name. The prefix ''lsn: ''is retained.
3926 10 active transactions in this session have been committed or terminated by another session.
3927 this session has active transactions, but still tries to register distributed transactions to process the Coordinator transactions.
3928 16 marked transactions ''% 1! ''Failed. A deadlock occurred when trying to put the mark into the log.