| Error |
Severity |
Description |
| 3009 |
16 |
Could not insert a backup or restore history/detail record in the msdb database. This may indicate a problem with the msdb database. The backup/restore operation was still successful. |
| 3013 |
16 |
Backup or restore operation terminating abnormally. |
| 3014 |
10 |
Backup or restore operation successfully processed %d pages in %d.%03d seconds (%d.%03d MB/sec). |
| 3015 |
10 |
%hs is not yet implemented. |
| 3016 |
16 |
File '%ls' of database '%ls' has been removed or shrunk since this backup or restore operation was interrupted. The operation cannot be restarted. |
| 3017 |
16 |
Could not resume interrupted backup or restore operation. See the SQL Server error log for more information. |
| 3018 |
16 |
There is no interrupted backup or restore operation to restart. Reissue the statement without the RESTART clause. |
| 3019 |
16 |
The checkpoint file was for a different backup or restore operation. Reissue the statement without the RESTART clause. |
| 3020 |
16 |
The backup operation cannot be restarted as the log has been truncated. Reissue the statement without the RESTART clause. |
| 3021 |
16 |
Cannot perform a backup or restore operation within a transaction. |
| 3023 |
16 |
Backup, CHECKALLOC, bulk copy, SELECT INTO, and file manipulation (such as CREATE FILE) operations on a database must be serialized. Reissue the statement after the current backup, CHECKALLOC, or file manipulation operation is completed. |
| 3024 |
16 |
You can only perform a full backup of the master database. Use BACKUP DATABASE to back up the entire master database. |
| 3025 |
16 |
Missing database name. Reissue the statement specifying a valid database name. |
| 3026 |
16 |
Could not find filegroup ID %d in sysfilegroups for database '%ls'. |
| 3027 |
16 |
Could not find filegroup '%.*ls' in sysfilegroups for database '%.*ls'. |
| 3028 |
16 |
Operation checkpoint file is invalid. Could not restart operation. Reissue the statement without the RESTART option. |
| 3029 |
16 |
Database file '%ls' is subject to logical recovery and must be among the files to be backed up as part of the file or filegroup backup. |
| 3030 |
16 |
Database file '%ls' is subject to logical recovery and must be among the files to be restored. |
| 3031 |
16 |
The statement has inconsistent or conflicting options. Remove the conflicting option and reissue the statement. |
| 3032 |
16 |
One or more of the options is not supported for this statement. Review the documentation for supported options. |
| 3033 |
16 |
BACKUP DATABASE cannot be used on a database opened in emergency mode. |
| 3034 |
16 |
No files were selected to be processed. You may have selected one or more filegroups that have no members. |
| 3035 |
16 |
Cannot perform a differential backup for database '%ls', because a current database backup does not exist. Reissue the statement omitting the WITH DIFFERENTIAL option. |
| 3036 |
16 |
Database '%ls' is in warm-standby state (set by executing RESTORE WITH STANDBY) and cannot be backed up until the entire load sequence is completed. |
| 3101 |
16 |
Database in use. The system administrator must have exclusive use of the database to run the restore operation. |
| 3106 |
16 |
The specified file '%ls' is in an obsolete backup database format (version %d) and cannot be upgraded to current server version %d. |
| 3108 |
16 |
RESTORE DATABASE must be used in single user mode when trying to restore the master database. |
| 3110 |
14 |
Only members of the sysadmin role or the database owner of '%.*ls' can run RESTORE DATABASE. |
| 3112 |
16 |
Cannot restore any database other than master when the server is in single user mode. |
| 3113 |
21 |
The database owner (DBO) does not have an entry in sysusers in database '%.*ls'. |
| 3114 |
21 |
Database '%.*ls' does not have an entry in sysdatabases. |
| 3115 |
10 |
User '%.*ls' in database '%.*ls' has SUID %d, which is the same as the SUID of the database owner (as defined in sysdatabases). User '%.*ls' will be given SUID %d. |
| 3116 |
10 |
When all restore transactions have been completed for database '%.*ls', user '%.*ls' should be given the next available SUID. |
| 3117 |
10 |
Database '%.*ls' already has a user with SUID %d. |
| 3120 |
16 |
The database you are attempting to restore was backed up under a different sort order ID (%d) than the one currently running on this server (%d), and at least one of them is a non-binary sort order. |
| 3123 |
16 |
Invalid database name '%.*ls' specified for backup or restore operation. |
| 3127 |
16 |
Temporary Message: The backup set does not contain pages for file '%ls'. |
| 3128 |
16 |
File '%ls' has an unsupported page size (%d). |
| 3129 |
16 |
Temporary Message: File '%ls' has changed size from %d to %d bytes. |
| 3132 |
16 |
The RAID set for database '%ls' is missing member number %d. |
| 3133 |
16 |
The volume on device '%ls' is not a member of the media family. |
| 3135 |
16 |
Cannot use the backup set in file '%ls' for this restore operation. |
| 3136 |
16 |
Cannot apply the differential backup on device '%ls' to database '%ls'. |
| 3138 |
16 |
One or more files in the backup set are no longer part of database '%ls'. |
| 3140 |
16 |
Could not adjust the space allocation for file '%ls'. |
| 3141 |
16 |
The database to be restored was named '%ls'. Reissue the statement using the WITH REPLACE option to overwrite the '%ls' database. |
| 3142 |
16 |
One or more devices or files already exist. Reissue the statement using the WITH REPLACE option to overwrite these files and devices. |
| 3143 |
16 |
The data set on device '%ls' is not a SQL Server backup set. |
| 3144 |
16 |
File '%.*ls' was not backed up in file %d on device '%ls'. The file cannot be restored from this backup set. |
| 3145 |
16 |
The STOPAT option is not supported for RESTORE DATABASE. You can use the STOPAT option with RESTORE LOG. |
| 3146 |
16 |
None of the newly-restored files had been modified after the backup was taken, so no further recovery actions are required. The database is now available for use. |
| 3147 |
16 |
Backup and restore operations are not allowed on database tempdb. |
| 3148 |
16 |
Media recovery for ALTER DATABASE is not yet implemented. The database cannot be rolled forward. |
| 3149 |
16 |
The database you are attempting to restore was backed up under a different Unicode locale ID (%d) or Unicode comparison style (%d) than the Unicode locale ID (%d) or Unicode comparison style (%d) currently running on this server. |
| 3150 |
10 |
The master database has been successfully restored. Shutting down SQL Server. |
| 3151 |
21 |
The master database failed to restore. Use the rebuildm utility to rebuild the master database. Shutting down SQL Server. |
| 3152 |
16 |
Cannot overwrite file '%ls' because it is marked as read-only. |
| 3153 |
16 |
The database is already fully recovered. |
| 3154 |
16 |
The backup set holds a backup of a database other than the existing '%ls' database. |
| 3155 |
16 |
The RESTORE operation cannot proceed because one or more files have been added or dropped from the database since the backup set was created. |
| 3156 |
16 |
The file '%ls' cannot be used by RESTORE. Consider using the WITH MOVE option to identify a valid location for the file. |
| 3157 |
16 |
The logical file (%d) is named '%ls'. RESTORE will not overwrite it from '%ls'. |
| 3158 |
16 |
Could not create one or more files. Consider using the WITH MOVE option to identify valid locations. |
| 3159 |
16 |
The tail of the log for database '%ls' has not been backed up. Back up the log and rerun the RESTORE statement specifying the FILE clause. |
| 3160 |
16 |
Could not update primary file information in sysdatabases. |
| 3161 |
16 |
The primary file is unavailable. It must be restored or otherwise made available. |
| 3162 |
16 |
The database has on-disk structure version %d. The server supports version %d and can only restore such a database that was inactive when it was backed up. This database was not inactive. |
| 3163 |
16 |
The transaction log was damaged. All data files must be restored before RESTORE LOG can be attempted. |
| 3164 |
16 |
Cannot roll forward the database with on-disk structure version %d. The server supports version %d. Reissue the RESTORE statement WITH RECOVERY. |
| 3165 |
16 |
Could not adjust the replication state of database '%ls'. The database was successfully restored, however its replication state is indeterminate. See the Troubleshooting Replication section in SQL Server Books Online. |
| 3166 |
16 |
RESTORE DATABASE could not drop database '%ls'. Drop the database and then reissue the RESTORE DATABASE statement. |
| 3167 |
16 |
RESTORE could not start database '%ls'. |
| 3201 |
16 |
Cannot open backup device '%ls'. Device error or device off-line. See the SQL Server error log for more details. |
| 3202 |
16 |
Write on '%ls' failed, status = %ld. See the SQL Server error log for more details. |
| 3203 |
16 |
Read on '%ls' failed, status = %ld. See the SQL Server error log for more details. |
| 3204 |
16 |
Operator aborted backup or restore. See the error messages returned to the console for more details. |
| 3205 |
16 |
Too many backup devices specified for backup or restore; only %d are allowed. |
| 3206 |
16 |
No entry in sysdevices for backup device '%.*ls'. Update sysdevices and rerun statement. |
| 3207 |
16 |
Backup or restore requires at least one backup device. Rerun your statement specifying a backup device. |
| 3208 |
16 |
Unexpected end of file while reading beginning of backup set. Confirm that the media contains a valid SQL Server backup set, and see the console error log for more details. |
| 3209 |
16 |
'%.*ls' is not a backup device. Check sysdevices. |
| 3211 |
10 |
%d percent %hs. |
| 3217 |
16 |
Invalid value specified for %ls parameter. |
| 3221 |
16 |
The ReadFileEx system function executed on file '%ls' only read %d bytes, expected %d. |
| 3222 |
16 |
The WriteFileEx system function executed on file '%ls' only wrote %d bytes, expected %d. |
| 3224 |
16 |
Could not create worker thread. |
| 3227 |
16 |
The volume on device '%ls' is a duplicate of stripe set member %d. |
| 3229 |
16 |
Request for device '%ls' timed out. |
| 3230 |
16 |
Operation on device '%ls' exceeded retry count. |
| 3234 |
16 |
File '%.*ls' is not a database file for database '%ls'. |
| 3235 |
16 |
File '%ls' is not part of database '%ls'. You can only list files that are members of this database. |
| 3237 |
16 |
Option not supported for Named Pipe-based backup sets. |
| 3239 |
16 |
The backup set on device '%ls' uses a feature of the Microsoft Tape Format not supported by SQL Server. |
| 3241 |
16 |
The media family on device '%ls' is incorrectly formed. SQL Server cannot process this media family. |
| 3242 |
16 |
The file on device '%ls' is not a valid Microsoft Tape Format backup set. |
| 3243 |
16 |
The media family on device '%ls' was created using Microsoft Tape Format version %d.%d. SQL Server supports version %d.%d. |
| 3244 |
16 |
Descriptor block size exceeds %d bytes. Use a shorter name and/or description string and retry the operation. |
| 3245 |
16 |
Could not convert a string to or from Unicode, %ls. |
| 3246 |
16 |
The media family on device '%ls' is marked as nonappendable. Reissue the statement using the INIT option to overwrite the media. |
| 3247 |
16 |
The volume on device '%ls' has the wrong media sequence number (%d). Remove it and insert volume %d. |
| 3248 |
25 |
>>> VOLUME SWITCH <<< (not for output!) |
| 3249 |
16 |
The volume on device '%ls' is a continuation volume for the backup set. Remove it and insert the volume holding the start of the backup set. |
| 3250 |
16 |
The value '%d' is not within range for the %ls parameter. |
| 3251 |
10 |
The RAID stream on device '%ls' has been finished. The device will now be reused for one of the remaining RAID streams. |
| 3252 |
16 |
Passwords on media and/or data sets are not supported in this release of SQL Server. |
| 3253 |
16 |
The block size parameter must supply a value that is a power of 2. |
| 3254 |
16 |
The volume on device '%ls' is empty. |
| 3255 |
16 |
The data set on device '%ls' is a SQL Server backup set not compatible with this version of SQL Server. |
| 3256 |
16 |
The backup set on device '%ls' was terminated while it was being created and is incomplete. RESTORE sequence is terminated abnormally. |
| 3257 |
16 |
There is insufficient free space on disk volume '%ls' to create the database. The database requires %I64u additional free bytes, while only %I64u bytes are available. |
| 3258 |
16 |
The volume on device '%ls' belongs to a different media set. |
| 3259 |
16 |
The volume on device '%ls' is not part of a multifamily (RAID) media set. Use WITH FORMAT to form a new RAID set. |
| 3260 |
16 |
An internal buffer has become full. |
| 3261 |
16 |
SQL Server cannot use the virtual device configuration. |
| 3262 |
10 |
The backup set is valid. |
| 3263 |
16 |
Cannot use the volume on device '%ls' as a continuation volume. It is sequence number %d of family %d for the current media set. Insert a new volume, or sequence number %d of family %d for the current set. |
| 3264 |
16 |
The operation did not proceed far enough to allow RESTART. Reissue the statement without the RESTART qualifier. |
| 3265 |
16 |
The login has insufficient authority. Membership of the sysadmin role is required to use VIRTUAL_DEVICE with BACKUP or RESTORE. |
| 3266 |
10 |
The Microsoft Tape Format (MTF) soft filemark database on backup device '%ls' cannot be read, inhibiting random access. |
| 3267 |
16 |
Insufficient resources to create UMS scheduler. |
| 3268 |
16 |
Cannot use the backup file '%ls' because it was originally formatted with sector size %d and is now on a device with sector size %d. |
| 3269 |
16 |
Cannot restore the file '%ls' because it was originally written with sector size %d; '%ls' is now on a device with sector size %d. |
| 3270 |
16 |
An internal consistency error occurred. Contact Technical Support for assistance. |
| 3271 |
16 |
Nonrecoverable I/O error occurred on file '%ls'. |
| 3272 |
16 |
The '%ls' device has a hardware sector size of %d, but the block size parameter specifies an incompatible override value of %d. Reissue the statement using a compatible block size. |
| 3301 |
21 |
Invalid log record found in the transaction log (logop %d). |
| 3307 |
21 |
Process %d was expected to hold logical lock on page %S_PGID. |
| 3313 |
21 |
Error while redoing logged operation in database '%.*ls'. Error at log record ID %S_LSN. |
| 3314 |
21 |
Error while undoing logged operation in database '%.*ls'. Error at log record ID %S_LSN. |
| 3405 |
10 |
Recovering database '%.*ls'. |
| 3406 |
10 |
%d transactions rolled forward in database '%.*ls' (%d). |
| 3407 |
10 |
%d transactions rolled back in database '%.*ls' (%d). |
| 3408 |
10 |
Recovery complete. |
| 3413 |
21 |
Database ID %d. Could not mark database as suspect. Getnext NC scan on sysdatabases.dbid failed. |
| 3414 |
10 |
Database '%.*ls' (database ID %d) could not recover. Contact Technical Support. |
| 3415 |
16 |
Read-only database '%.*ls' must be made writable before it can be upgraded. |
| 3417 |
21 |
Cannot recover the master database. Exiting. |
| 3429 |
10 |
Warning: The outcome of transaction %S_XID, named '%.*ls' in database '%.*ls' (database ID %d), could not be determined because the coordinating database (database ID %d) could not be opened. The transaction was assumed to be committed. |
| 3430 |
10 |
Warning: Could not determine the outcome of transaction %S_XID, named '%.*ls' in database '%.*ls' (with ID %d) because the coordinating database (ID %d) did not contain the outcome. The transaction was assumed to be committed. |
| 3431 |
21 |
Could not recover database '%.*ls' (database ID %d) due to unresolved transaction outcomes. |
| 3432 |
16 |
Warning: syslanguages is missing. |
| 3433 |
16 |
Name is truncated to '%.*ls'. The maximum name length is %d. |
| 3434 |
20 |
Cannot change sort order or locale. Server shutting down. Restart SQL Server to continue with sort order unchanged. |
| 3435 |
20 |
Sort order or locale cannot be changed because user objects or user databases exist. |
| 3436 |
20 |
Cannot rebuild index ID %d for the '%.*ls' table in the '%.*ls' database. |
| 3437 |
21 |
Error recovering database '%.*ls'. Could not connect to MSDTC to check the completion status of transaction %S_XID. |
| 3438 |
10 |
Database '%.*ls' (database ID %d) failed to recover because transaction first LSN is not equal to LSN in checkpoint. Contact Technical Support. |
| 3439 |
10 |
Database '%.*ls' (database ID %d). The DBCC RECOVERDB statement failed due to previous errors. |
| 3440 |
21 |
Database '%.*ls' (database ID %d). The DBCC RECOVERDB statement can only be run after a RESTORE statement that used the WITH NORECOVERY option. |
| 3441 |
21 |
Database '%.*ls' (database ID %d). The RESTORE statement could not access file '%ls'. Error was '%ls'. |
| 3442 |
21 |
Database '%.*ls' (database ID %d). The size of the undo file is insufficient. |
| 3443 |
21 |
Database '%.*ls' (database ID %d) was marked for standby or read-only use, but has been modified. The RESTORE LOG statement cannot be performed. |
| 3444 |
21 |
Database '%.*ls' (database ID %d). Could not find start of previous recovery operation. The RESTORE LOG statement cannot be performed. |
| 3445 |
21 |
Database '%.*ls' (database ID %d). The file '%ls' is not a valid undo file. |
| 3446 |
16 |
Primary file not available for database '%.*ls'. |
| 3447 |
16 |
Could not activate or scan all of the log files for database '%.*ls'. |
| 3448 |
21 |
Could not undo log record %S_LSN, for transaction ID %S_XID, on page %S_PGID, database '%.*ls' (database ID %d). Page information: LSN = %S_LSN, type = %ld. Log information: OpCode = %ld, context %ld. |
| 3449 |
21 |
An error has occurred indicating potential database corruption. SQL Server is shutting down so that recovery can be performed on database ID %d. |
| 3450 |
10 |
Recovery progress on database '%.*ls' (%d): %d percent. |
| 3451 |
16 |
Recovery has failed because reexecution of CREATE INDEX found inconsistencies between target filegroup '%ls' (%d) and source filegroup '%ls' (%d). Restore both filegroups before attempting further RESTORE LOG operations. |
| 3452 |
10 |
Recovery of database '%.*ls' (%d) detected possible identity value inconsistency in table ID %d. Run DBCC CHECKIDENT ('%.*ls'). |
| 3453 |
21 |
Recovery has failed because a nonlogged operation could not be redone. Use the RESTORE statement to restore all data in filegroup '%ls' (%d) to a point beyond the nonlogged changes. |
| 3501 |
21 |
Could not find row in sysdatabases for database ID %d at checkpoint time. |
| 3505 |
14 |
Only the owner of database '%.*ls' can run the CHECKPOINT statement. |
| 3508 |
25 |
Could not get an exclusive lock on the database '%.*ls'. Make sure that no other users are currently using this database, and rerun the CHECKPOINT statement. |
| 3509 |
14 |
Could not set database '%.*ls' %ls read-only user mode because you could not exclusively lock the database. |
| 3510 |
16 |
Database '%.*ls' cannot be changed from read-only because the primary and/or log file(s) are not writable. |
| 3604 |
10 |
Duplicate key was ignored. |
| 3605 |
10 |
Duplicate row was ignored. |
| 3606 |
10 |
Arithmetic overflow occurred. |
| 3607 |
10 |
Division by zero occurred. |
| 3608 |
16 |
Cannot allocate a GUID for the token. |
| 3612 |
10 |
%hsSQL Server Execution Times:%hs CPU time = %lu ms, elapsed time = %lu ms. |
| 3613 |
10 |
SQL Server parse and compile time: %hs CPU time = %lu ms, elapsed time = %lu ms. |
| 3615 |
10 |
Table '%.*ls'. Scan count %d, logical reads %d, physical reads %d, read-ahead reads %d. |
| 3618 |
10 |
The transaction has been terminated. |
| 3619 |
10 |
Could not write a CHECKPOINT record in database ID %d because the log is out of space. |
| 3620 |
10 |
Automatic checkpointing is disabled in database '%.*ls' because the log is out of space. It will continue when the database owner successfully checkpoints the database. Free up some space or extend the database and then run the CHECKPOINT statement. |
| 3621 |
10 |
The statement has been terminated. |
| 3622 |
10 |
A domain error occurred. |
| 3623 |
10 |
A transaction on a no_log table was undone. See the SQL Server errorlog for details. |
| 3625 |
20 |
'%hs' is not yet implemented. |
| 3627 |
16 |
Could not create worker thread. |
| 3701 |
11 |
Cannot drop the %S_MSG '%.*ls', because it does not exist in the system catalog. |
| 3702 |
16 |
Cannot drop the %S_MSG '%.*ls' because it is currently in use. |
| 3704 |
16 |
Only the owner or members of the sysadmin role can drop the %S_MSG '%.*ls'. |
| 3705 |
16 |
Cannot use DROP %ls with '%.*ls' because '%.*ls' is a %S_MSG. Use DROP %ls. |
| 3708 |
16 |
Cannot drop the %S_MSG '%.*ls' because it is a system %S_MSG. |
| 3716 |
16 |
The %S_MSG '%.*ls' cannot be dropped because it is bound to one or more %S_MSG. |
| 3718 |
11 |
Could not drop index '%.*ls' because the table or clustered index entry cannot be found in the sysindexes system table. |
| 3723 |
16 |
An explicit DROP INDEX is not allowed on index '%.*ls'. It is being used for %ls constraint enforcement. |
| 3724 |
16 |
Cannot drop the %S_MSG '%.*ls' because it is published for replication. |
| 3725 |
16 |
The constraint '%.*ls' is being referenced by table '%.*ls', foreign key constraint '%.*ls'. |
| 3726 |
16 |
Could not drop object '%.*ls' because it is referenced by a FOREIGN KEY constraint. |
| 3727 |
10 |
Could not drop constraint. See previous errors. |
| 3728 |
16 |
'%.*ls' is not a constraint. |
| 3733 |
16 |
Constraint '%.*ls' does not belong to table '%.*ls'. |
| 3736 |
16 |
Cannot drop the %S_MSG '%.*ls' because it is being used for distribution. |
| 3737 |
16 |
Could not delete file '%ls'. See the SQL Server error log for more information. |
| 3738 |
16 |
Deleting database file '%ls'. |
| 3739 |
15 |
Cannot %ls the index '%.*ls' because it is not a statistics collection. |
| 3740 |
16 |
Cannot drop the %S_MSG '%.*ls' because at least part of the table resides on a read-only filegroup. |
| 3902 |
13 |
The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION. |
| 3903 |
13 |
The ROLLBACK TRANSACTION request has no corresponding BEGIN TRANSACTION. |
| 3904 |
21 |
Cannot unsplit logical page %S_PGID in object '%.*ls', in database '%.*ls'. Both pages together contain more data than will fit on one page. |
| 3906 |
16 |
Could not run BEGIN TRANSACTION in database '%.*ls' because the database is read-only. |
| 3908 |
16 |
Could not run BEGIN TRANSACTION in database '%.*ls' because the database is in bypass recovery mode. |
| 3909 |
16 |
Session binding token is invalid or corrupt. |
| 3910 |
16 |
Transaction context in use by another session. |
| 3912 |
16 |
Cannot bind using an XP token while the server is not in an XP call. |
| 3914 |
16 |
The data type '%s' is invalid for transaction names or savepoint names. Allowed data types are char, varchar, nchar, or nvarchar. |
| 3915 |
16 |
Cannot use the ROLLBACK statement within an INSERT-EXEC statement. |
| 3916 |
16 |
Cannot use the COMMIT statement within an INSERT-EXEC statement unless BEGIN TRANSACTION is used first. |
| 3917 |
16 |
Session is bound to a transaction context that is in use. Other statements in the batch were ignored. |