Troubleshooting
Errors 3000 - 3999
| Error | Severity | Description (Message Text) |
| 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. |
| 3011 | 16 | All backup devices must be of the same general class (for example, DISK and TAPE). |
| 3013 | 16 | %hs is terminating abnormally. |
| 3014 | 10 | %hs 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 and file manipulation operations (such as ALTER DATABASE ADD FILE) on a database must be serialized. Reissue the statement after the current backup 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. |
| 3031 | 16 | Option '%ls' conflicts with option(s) '%ls'. Remove the conflicting option and reissue the statement. |
| 3032 | 16 | One or more of the options (%ls) are 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. Perform a full database backup by reissuing BACKUP DATABASE, 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. |
| 3037 | 16 | Minimally logged operations have occurred prior to this WITH RESTART command. Reissue the BACKUP statement without WITH RESTART. |
| 3038 | 16 | The filename '%ls' is invalid as a backup device name. Reissue the BACKUP statement with a valid filename. |
| 3039 | 16 | Cannot perform a differential backup for file '%ls' because a current file backup does not exist. Reissue BACKUP DATABASE omitting the WITH DIFFERENTIAL option. |
| 3040 | 10 | An error occurred while informing replication of the backup. The backup will continue, but the replication environment should be inspected. |
| 3041 | 16 | BACKUP failed to complete the command %.*ls |
| 3101 | 16 | Exclusive access could not be obtained because the database is in use. |
| 3108 | 16 | RESTORE DATABASE must be used in single user mode when trying to restore the master database. |
| 3110 | 14 | User does not have permission to RESTORE database '%.*ls'. |
| 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. |
| 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 media set for database '%ls' has %d family members but only %d are provided. All members must be provided. |
| 3133 | 16 | The volume on device '%ls' is not a member of the media family. |
| 3135 | 16 | The backup set in file '%ls' was created by %hs and cannot be used for this restore operation. |
| 3136 | 16 | Cannot apply the 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 | File '%ls' cannot be restored over the existing '%ls'. Reissue the RESTORE statement using WITH REPLACE to overwrite pre-existing files. |
| 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. |
| 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. |
| 3234 | 15 | Logical file '%.*ls' is not part of database '%ls'. Use RESTORE FILELISTONLY to list the logical file names. |
| 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 media family on device '%ls' is complete. The device is now being reused for one of the remaining families. |
| 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 multiple family media set. BACKUP WITH FORMAT can be used to form a new media 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 backup data in '%ls' is incorrectly formatted. Backups cannot be appended, but existing backup sets may still be usable. |
| 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. |
| 3273 | 16 | The BUFFERCOUNT parameter must supply a value that allows at least one buffer per backup device. |
| 3274 | 16 | Incorrect checksum computed for the backup set on device %ls. The backup set cannot be restored. |
| 3275 | 16 | I/O request 0x%08x failed I/O verification. See the error log for a description. |
| 3276 | 16 | WITH SNAPSHOT can be used only if the backup set was created WITH SNAPSHOT. |
| 3277 | 16 | WITH SNAPSHOT must be used with only one virtual device. |
| 3278 | 16 | Failed to encrypt string %ls |
| 3279 | 16 | Access is denied due to a password failure |
| 3280 | 16 | Backups on raw devices are not supported. '%ls' is a raw device. |
| 3281 | 16 | Released and initiated rewind on '%ls'. |
| 3301 | 21 | Invalid log record found in the transaction log (logop %d). |
| 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. |
| 3315 | 10 | During rollback, process %d was expected to hold mode %d lock at level %d for row %S_RID in database '%.*ls' under transaction %S_XID. |
| 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 | Database '%.*ls' is read-only or has read-only files and 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 | 16 | Cannot rebuild index 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. |
| 3445 | 21 | File '%ls' is not a valid undo file for database '%.*ls', database ID %d. |
| 3450 | 10 | Recovery of database '%.*ls' (%d) is %d%% complete (approximately %d more seconds) (Phase %d of 3). |
| 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. |
| 3625 | 20 | '%hs' is not yet implemented. |
| 3627 | 16 | Could not create worker thread. |
| 3628 | 24 | A floating point exception occurred in the user process. Current transaction is canceled. |
| 3629 | 10 | This SQL Server has been optimized for %d concurrent queries. This limit has been exceeded by %d queries and performance may be adversely affected. |
| 3630 | 10 | Concurrency violations since %ls%s 1 2 3 4 5 6 7 8 9 10-100 >100%s%6u%6u%6u%6u%6u%6u%6u%6u%6u%8u%6u |
| 3631 | 10 | Concurrency violations will be written to the SQL Server error log. |
| 3632 | 10 | Concurrency violations will not be written to the SQL Server error log. |
| 3701 | 11 | Cannot %S_MSG 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. |
| 3703 | 16 | Cannot detach the %S_MSG '%.*ls' because it is currently in use. |
| 3704 | 16 | User does not have permission to perform this operation on %S_MSG '%.*ls'. |
| 3705 | 16 | Cannot use DROP %ls with '%.*ls' because '%.*ls' is a %S_MSG. Use DROP %ls. |
| 3708 | 16 | Cannot %S_MSG 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 %S_MSG the %S_MSG '%.*ls' because it is being used 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. |
| 3729 | 16 | Cannot %ls '%.*ls' because it is being referenced by object '%.*ls'. |
| 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. |
| 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. |
| 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. |
| 3918 | 16 | Statement must be executed in the context of a user transaction. |
| 3919 | 16 | Cannot enlist in the transaction because the transaction has already been committed or rolled back. |
| 3920 | 10 | The WITH MARK option only applies to the first BEGIN TRAN WITH MARK statement. The option is ignored. |
| 3921 | 16 | Cannot get a transaction token if there is no transaction active. Reissue the statement after a transaction has been started |
| 3922 | 16 | Cannot enlist in the transaction because the transaction does not exist. |
| 3923 | 10 | Cannot use transaction marks on database '%.*ls' with bulk-logged operations that have not been backed up. The mark is ignored. |
| 3924 | 10 | The session was enlisted in an active user transaction while trying to bind to a new transaction. The session has defected from the previous user transaction. |
| 3925 | 16 | Invalid transaction mark name. The 'LSN:' prefix is reserved. |
| 3926 | 10 | The transaction active in this session has been committed or aborted by another session. |
| 3927 | 10 | The session had an active transaction when it tried to enlist in a Distributed Transaction Coordinator transaction. |
| 3928 | 16 | The marked transaction '%.*ls' failed. A Deadlock was encountered while attempting to place the mark in the log. |