SQL Server Error Messages 3001 to 4000

In this post, we’ll list out the SQL Server Error Messages from the error codes 3001 to 4000 and references to the detailed post to know more about the errors and how to fix them when using SQL Server as database in your application.

SQL Server Error Messages 3001 to 4000

ErrorCodeSeverityErrorMessage
300216Cannot BACKUP or RESTORE a database snapshot.
300310This BACKUP WITH DIFFERENTIAL will be based on more than one file backup. All those file backups must be restored before attempting to restore this differential backup.
300416The primary filegroup cannot be backed up as a file backup because the database is using the SIMPLE recovery model. Consider taking a partial backup by specifying READ_WRITE_FILEGROUPS.
300510The differential partial backup is including a read-only filegroup, ‘%ls’. This filegroup was read-write when the base partial backup was created, but was later changed to read-only access. We recommend that you create a separate file backup of the ‘%ls’ filegroup now, and then create a new partial backup to provide a new base for later differential partial backups.
300616The differential backup is not allowed because it would be based on more than one base backup. Multi-based differential backups are not allowed in the simple recovery model, and are never allowed for partial differential backups.
300716The backup of the file or filegroup “%ls” is not permitted because it is not online. Container state: “%ls” (%d). Restore status: %d. BACKUP can be performed by using the FILEGROUP or FILE clauses to restrict the selection to include only online data.
300816The specified device type is not supported for backup mirroring.
300916Could 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.
301016Invalid backup mirror specification. All mirrors must have the same number of members.
301116All backup devices must be of the same general class (for example, DISK and TAPE).
301217VDI ran out of buffer when SQL Server attempted to send differential information to SQL Writer.
301316%hs is terminating abnormally.
301410%hs successfully processed %I64d pages in %d.%03d seconds (%d.%03d MB/sec).
301510%hs is not yet implemented.
301616Backup of file ‘%ls’ is not permitted because it contains pages subject to an online restore sequence. Complete the restore sequence before taking the backup, or restrict the backup to exclude this file.
301716The restart-checkpoint file ‘%ls’ could not be opened. Operating system error ‘%ls’. Correct the problem, or reissue the command without RESTART.
301810The restart-checkpoint file ‘%ls’ was not found. The RESTORE command will continue from the beginning as if RESTART had not been specified.
301916The restart-checkpoint file ‘%ls’ is from a previous interrupted RESTORE operation and is inconsistent with the current RESTORE command. The restart command must use the same syntax as the interrupted command, with the addition of the RESTART clause. Alternatively, reissue the current statement without the RESTART clause.
302116Cannot perform a backup or restore operation within a transaction.
302210This backup is a file backup of read-write data from a database that uses the simple recovery model. This is only appropriate if you plan to set the filegroup to read-only followed by a differential file backup. Consult Books Online for more information on managing read-only data for the simple recovery model. In particular, consider how partial backups are used.
302316Backup, file manipulation operations (such as ALTER DATABASE ADD FILE) and encryption changes on a database must be serialized. Reissue the statement after the current backup or file manipulation operation is completed.
302416You can only perform a full backup of the master database. Use BACKUP DATABASE to back up the entire master database.
302516Missing database name. Reissue the statement specifying a valid database name.
302716The filegroup “%.*ls” is not part of database “%.*ls”.
302810The restart-checkpoint file ‘%ls’ was corrupted and is being ignored. The RESTORE command will continue from the beginning as if RESTART had not been specified.
303116Option ‘%ls’ conflicts with option(s) ‘%ls’. Remove the conflicting option and reissue the statement.
303216One or more of the options (%ls) are not supported for this statement. Review the documentation for supported options.
303316BACKUP DATABASE cannot be used on a database opened in emergency mode.
303416No files were selected to be processed. You may have selected one or more filegroups that have no members.
303516Cannot 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.
303616The database “%ls” is in warm-standby state (set by executing RESTORE WITH STANDBY) and cannot be backed up until the entire restore sequence is completed.
303816The file name “%ls” is invalid as a backup device name. Reissue the BACKUP statement with a valid file name.
303916Cannot perform a differential backup for file ‘%ls’ because a current file backup does not exist. Reissue BACKUP DATABASE omitting the WITH DIFFERENTIAL option.
304010An error occurred while informing replication of the backup. The backup will continue, but the replication environment should be inspected.
304116BACKUP failed to complete the command %.*ls. Check the backup application log for detailed messages.
304210BACKUP WITH CONTINUE_AFTER_ERROR successfully generated a backup of the damaged database. Refer to the SQL Server error log for information about the errors that were encountered.
304316BACKUP ‘%ls’ detected an error on page (%d:%d) in file ‘%ls’.
304416Invalid zero-length device name. Reissue the BACKUP statement with a valid device name.
304516BACKUP or RESTORE requires the NTFS file system for FILESTREAM and full-text support. The path “%.*ls” is not usable.
304616Inconsistent metadata has been encountered. The only possible backup operation is a tail-log backup using the WITH CONTINUE_AFTER_ERROR or NO_TRUNCATE option.
304716The 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. This path is also used to locate restart checkpoint files for RESTORE.
304916BACKUP detected corruption in the database log. Check the errorlog for more information.
305016SQL Server could not send the differential information for database file ‘%ls’ of database ‘%ls\\%ls’ to the backup application because the differential information is too large to fit in memory, and an attempt to use a temporary file has failed.
305116BACKUP LOG was unable to maintain mirroring consistency for database ‘%ls’. Database mirroring has been suspended.
305216BACKUP LOG was unable to log updates for for database ‘%ls’. Subsequent log backups will be required to advance the backup point from %S_LSN to %S_LSN after log space is made available for logging them.
305316BACKUP ‘%ls’ detected an error on a page in file ‘%ls’.
305416Differential file backups can include only read-only data for databases using the simple recovery model. Consider taking a partial backup by specifying READ_WRITE_FILEGROUPS.
305516Backup destination “%.*ls” supports a FILESTREAM filegroup. This filegroup cannot be used as a backup destination. Rerun the BACKUP statement with a valid backup destination.
305616The backup operation has detected an unexpected file in a FILESTREAM container. The backup operation will continue and include file ‘%ls’.
305716Invalid device name. The length of the device name provided exceeds supported limit (maximum length is:%d). Reissue the BACKUP statement with a valid device name.
305810File or device name exceeds the supported limit (maximum length is:%d) and will be truncated: %.*ls.
305916This BACKUP or RESTORE command is not supported on a database mirror or secondary replica.
306010The restart-checkpoint file ‘%ls’ was corrupted. The restored database can not be recovered.  Restart the RESTORE sequence.
306116The 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.
306216Cannot backup from a HADRON secondary because it is not in Synchronizing or Synchronized state.
306316Write to backup block blob device %ls failed. Device has reached its limit of allowed blocks.
306416Write to backup block blob detected out of order write at offset %ld, last block offset was at %ld.
306516Attempt to commit the block list for a block blob failed. Blob Name is “%.*ls”. Storage Errorcode %ld.
306616Could not find the database file referenced by the file snapshot %.*ls. Please make sure that the URL points to a valid snapshot on a database file.
306716Failed while trying to delete file snapshot %.*ls. Error code %ld.
306816Invalid file snapshot URL. Please make sure that the URL is correctly formed.
306916Striping a backup set across multiple devices is not permitted for file snapshot backups.
307016Specifying the WITH options FORMAT and FILE_SNAPSHOT is not permitted.
307116The database %.*ls is configured for file snapshot point in time restore, log backups are not permitted.
307216Backup encryption is incompatible with file snapshot backup if TDE is not enabled on the database.
307316The option WITH FILE_SNAPSHOT is only permitted if all database files are in Azure Storage.
307416Failed while getting attributes for the file snapshot %.*ls. Error code %ld.
307516Device name ‘%.*ls’ is not a valid MOVE target when restoring from a File Snapshot Backup.
307616File Snapshot Backup is only permitted with a single backup device and no additonal mirrored devices.
307710File snapshot %.*ls not found.
307816The file name “%ls” is invalid as a backup device name for the specified device type. Reissue the BACKUP statement with a valid file name and device type.
307916Could not find the blob file %.*ls. Please make sure that the file name points to a valid blob file.
308016Invalid Backup Path. The length of the default backup path provided exceeds supported limit (maximum length is: %d). Correct the default backup path.
309516The backup cannot be performed because ‘ENCRYPTION’ was requested after the media was formatted with an incompatible structure. To append to this media set, either omit ‘ENCRYPTION’ or create a new media set by using WITH FORMAT in your BACKUP statement. If you use WITH FORMAT on an existing media set, all its backup sets will be overwritten.
309616The Certificate specified for backup encryption has expired.
309716The Backup cannot be performed because the existing media set is formatted with an incompatible version.
309816The backup cannot be performed because ‘%ls’ was requested after the media was formatted with an incompatible structure. To append to this media set, either omit ‘%ls’ or specify ‘%ls’. Alternatively, you can create a new media set by using WITH FORMAT in your BACKUP statement. If you use WITH FORMAT on an existing media set, all its backup sets will be overwritten.
309916Backup Encryption options were specified, Backup Encryption support has not been enabled on this version.
310116Exclusive access could not be obtained because the database is in use.
310216%ls cannot process database ‘%ls’ because it is in use by this session. It is recommended that the master database be used when performing this operation.
310316A partial restore sequence cannot be initiated by this command. To initiate a partial restore sequence, use the WITH PARTIAL clause of the RESTORE statement and provide a backup set which includes a full copy of at least the primary data file. The WITH PARTIAL clause of the RESTORE statement may not be used for any other purpose.
310416RESTORE cannot operate on database ‘%ls’ because it is configured for database mirroring or has joined an availability group. If you intend to restore the database, use ALTER DATABASE to remove mirroring or to remove the database from its availability group.
310516RESTORE cannot restore any more pages into file ‘%ls’ because the maximum number of pages (%d) are already being restored. Either complete the restore sequence for the existing pages, or use RESTORE FILE to restore all pages in the file.
310616The filegroup “%ls” is ambiguous. The identity in the backup set does not match the filegroup that is currently defined in the online database. To force the use of the filegroup in the backup set, take the database offline and then reissue the RESTORE command.
310716The file “%ls” is ambiguous. The identity in the backup set does not match the file that is currently defined in the online database. To force the use of the file in the backup set, take the database offline and then reissue the RESTORE command.
310816To restore the master database, the server must be running in single-user mode. For information on starting in single-user mode, see “How to: Start an Instance of SQL Server (sqlservr.exe)” in Books Online.
310916Master 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.
311014User does not have permission to RESTORE database ‘%.*ls’.
311116Page %S_PGID is a control page which cannot be restored in isolation. To repair this page, the entire file must be restored.
311216Cannot restore any database other than master when the server is in single user mode.
311316Invalid data was detected.
311516The database is using the simple recovery model. It is not possible to restore a subset of the read-write data.
311616The supplied backup is not on the same recovery path as the database, and is ineligible for use for an online file restore.
311716The log or differential backup cannot be restored because no files are ready to rollforward.
311816The database “%ls” does not exist. RESTORE can only create a database when restoring either a full backup or a file backup of the primary file.
311916Problems were identified while planning for the RESTORE statement. Previous messages provide details.
312016This backup set will not be restored because all data has already been restored to a point beyond the time covered by this backup set.
312116The file “%ls” is on a recovery path that is inconsistent with application of this backup set. RESTORE cannot continue.
312216File initialization failed. RESTORE cannot continue.
312316Invalid database name ‘%.*ls’ specified for backup or restore operation.
312516The database is using the simple recovery model. The data in the backup it is not consistent with the current state of the database. Restoring more data is required before recovery is possible. Either restore a full file backup taken since the data was marked read-only, or restore the most recent base backup for the target data followed by a differential file backup.
312716The file ‘%.*ls’ of restored database ‘%ls’ is being left in the defunct state because the database is using the simple recovery model and the file is marked for read-write access. Therefore, only read-only files can be recovered by piecemeal restore.
312816File ‘%ls’ has an unsupported page size (%d).
312916The contents of the file “%ls” are not consistent with a transition into the restore sequence. A restore from a backup set may be required.
313010The filegroup “%ls” is selected. At the time of backup it was known by the name “%ls”‘. RESTORE will continue operating upon the renamed filegroup.
313110The file “%ls” is selected. At the time of backup it was known by the name “%ls”. RESTORE will continue operating upon the renamed file.
313216The media set has %d media families but only %d are provided. All members must be provided.
313316The volume on device “%ls” is sequence number %d of media family %d, but sequence number %d of media family %d is expected. Check that the device specifications and loaded media are correct.
313410The differential base attribute for file ‘%ls’ of database ‘%ls’ has been reset because the file has been restored from a backup taken on a conflicting recovery path. The restore was allowed because the file was read-only and was consistent with the current status of the database. Any future differential backup of this file will require a new differential base.
313516The backup set in file ‘%ls’ was created by %hs and cannot be used for this restore operation.
313616This differential backup cannot be restored because the database has not been restored to the correct earlier state.
313716Database cannot be reverted. Either the primary or the snapshot names are improperly specified, all other snapshots have not been dropped, or there are missing files.
313816The database cannot be reverted because FILESTREAM BLOBs are present.
313916Restore to snapshot is not allowed with the master database.
314016Could not adjust the space allocation for file ‘%ls’.
314116The database to be restored was named ‘%ls’. Reissue the statement using the WITH REPLACE option to overwrite the ‘%ls’ database.
314216File “%ls” cannot be restored over the existing “%ls”. Reissue the RESTORE statement using WITH REPLACE to overwrite pre-existing files, or WITH MOVE to identify an alternate location.
314316The data set on device ‘%ls’ is not a SQL Server backup set.
314416File ‘%.*ls’ was not backed up in file %d on device ‘%ls’. The file cannot be restored from this backup set.
314516The STOPAT option is not supported for databases that use the SIMPLE recovery model.
314716Backup and restore operations are not allowed on database tempdb.
314816This RESTORE statement is invalid in the current context. The ‘Recover Data Only’ option is only defined for secondary filegroups when the database is in an online state. When the database is in an offline state filegroups cannot be specified.
314916The file or filegroup “%ls” is not in a valid state for the “Recover Data Only” option to be used. Only secondary files in the OFFLINE or RECOVERY_PENDING state can be processed.
315010The master database has been successfully restored. Shutting down SQL Server.
315121Failed to restore master database. Shutting down SQL Server. Check the error logs, and rebuild the master database. For more information about how to rebuild the master database, see SQL Server Books Online.
315316The database is already fully recovered.
315416The backup set holds a backup of a database other than the existing ‘%ls’ database.
315516The RESTORE operation cannot proceed because one or more files have been added or dropped from the database since the backup set was created.
315616File ‘%ls’ cannot be restored to ‘%ls’. Use WITH MOVE to identify a valid location for the file.
315916The tail of the log for the database “%ls” has not been backed up. Use BACKUP LOG WITH NORECOVERY to backup the log if it contains work you do not want to lose. Use the WITH REPLACE or WITH STOPAT clause of the RESTORE statement to just overwrite the contents of the log.
316116The primary file is unavailable. It must be restored or otherwise made available.
316316The transaction log was damaged. All data files must be restored before RESTORE LOG can be attempted.
316516Database ‘%ls’ was restored, however an error was encountered while replication was being restored/removed. The database has been left offline. See the topic MSSQL_ENG003165 in SQL Server Books Online.
316616RESTORE DATABASE could not drop database ‘%ls’. Drop the database and then reissue the RESTORE DATABASE statement.
316716RESTORE could not start database ‘%ls’.
316816The backup of the system database on the device %ls cannot be restored because it was created by a different version of the server (%ls) than this server (%ls).
316916The database was backed up on a server running version %ls. That version is incompatible with this server, which is running version %ls. Either restore the database on a server that supports the backup, or use a backup that is compatible with this server.
317016The STANDBY filename is invalid.
317116File %ls is defunct and cannot be restored into the online database.
317216Filegroup %ls is defunct and cannot be restored into the online database.
317316The STOPAT clause provided with this RESTORE statement indicates that the tail of the log contains changes that must be backed up to reach the target point in time. The tail of the log for the database “%ls” has not been backed up. Use BACKUP LOG WITH NORECOVERY to back up the log, or use the WITH REPLACE clause in your RESTORE statement to overwrite the tail of the log.
317416The file ‘%ls’ cannot be moved by this RESTORE operation.
317510RESTORE FILEGROUP=”%ls” was specified, but not all of its files are present in the backup set. File “%ls” is missing. RESTORE will continue, but if you want all files to be restored, you must restore other backup sets.
317616File ‘%ls’ is claimed by ‘%ls'(%d) and ‘%ls'(%d). The WITH MOVE clause can be used to relocate one or more files.
317816File %ls is not in the correct state to have this differential backup applied to it.
317916The system database cannot be moved by RESTORE.
318016This backup cannot be restored using WITH STANDBY because a database upgrade is needed. Reissue the RESTORE without WITH STANDBY.
318110Attempting to restore this backup may encounter storage space problems. Subsequent messages will provide details.
318216The backup set cannot be restored because the database was damaged when the backup occurred. Salvage attempts may exploit WITH CONTINUE_AFTER_ERROR.
318316RESTORE detected an error on page (%d:%d) in database “%ls” as read from the backup set.
318410RESTORE WITH CONTINUE_AFTER_ERROR was successful but some damage was encountered. Inconsistencies in the database are possible.
318516RESTORE cannot apply this backup set because the database is suspect. Restore a backup set that repairs the damage.
318616The backup set has been damaged. RESTORE will not attempt to apply this backup set.
318716RESTORE WITH CHECKSUM cannot be specified because the backup set does not contain checksum information.
318810The backup set was written with damaged data by a BACKUP WITH CONTINUE_AFTER_ERROR.
318916Damage to the backup set was detected.
319016Filegroup ‘%ls’ cannot be restored because it does not exist in the backup set.
319116Restore cannot continue because file ‘%ls’ cannot be written. Ensure that all files in the database are writable.
319210Restore was successful but deferred transactions remain. These transactions cannot be resolved because there are data that is unavailable. Either use RESTORE to make that data available or drop the filegroups if you never need this data again. Dropping the filegroup results in a defunct filegroup.
319316Restore Log operations are not permitted for a Log Backup with FILE_SNAPSHOT if bulk operations were present during the backup period. The Restore can be accomplished by issuing Restore Database from this archive.
319416Page %S_PGID is beyond the end of the file. Only pages that are in the current range of the file can be restored.
319516Page %S_PGID cannot be restored from this backup set. RESTORE PAGE can only be used from full backup sets or from the first log or differential backup taken since the file was added to the database.
319616RESTORE master WITH SNAPSHOT is not supported. To restore master from a snapshot backup, stop the service and copy the data and log file.
319710I/O is frozen on database %ls. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
319810I/O was resumed on database %ls. No user action is required.
319916RESTORE requires MAXTRANSFERSIZE=%u but %u was specified.
320116Cannot open backup device ‘%ls’. Operating system error %ls.
320216Write on “%ls” failed: %ls
320316Read on “%ls” failed: %ls
320416The backup or restore was aborted.
320516Too many backup devices specified for backup or restore; only %d are allowed.
320616Backup device ‘%.*ls’ does not exist. To view existing backup devices, use the sys.backup_devices catalog view. To create a new backup device use either sp_addumpdevice or SQL Server Management Studio.
320716Backup or restore requires at least one backup device. Rerun your statement specifying a backup device.
320816Unexpected 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.
320916Operation is not supported on user instances.
321016The mirror member in drive “%ls” is inconsistent with the mirror member in drive “%ls”.
321110%d percent processed.
321216The mirror device “%ls” and the mirror device “%ls” have different device specifications.
321316Unable to unload one or more tapes. See the error log for details.
321416Too many backup mirrors are specified. Only %d are allowed.
321516Use WITH FORMAT to create a new mirrored backup set.
321616RESTORE REWINDONLY is only applicable to tape devices.
321716Invalid value specified for %ls parameter.
321816Backup mirroring is not available in this edition of SQL Server. See Books Online for more details on feature support in different SQL Server editions.
321916The file or filegroup “%.*ls” cannot be selected for this operation.
322016The specified URL points to a Block Blob. Backup and Restore operations on Block Blobs are not supported when WITH CREDENTIAL syntax is used.
322116The ReadFileEx system function executed on file ‘%ls’ only read %d bytes, expected %d.
322216The WriteFileEx system function executed on file ‘%ls’ only wrote %d bytes, expected %d.
322316Backup To URL failed to write status messages to the operating system error log.
322416Cannot create worker thread.
322516Use of WITH CREDENTIAL syntax is not valid for credentials containing a Shared Access Signature.
322616Failed to create snapshot for file “%ls”.
322716The backup media on “%ls” is part of media family %d which has already been processed on “%ls”. Ensure that backup devices are correctly specified. For tape devices, ensure that the correct volumes are loaded.
322816Writing snapshot metadata to backup set for file “%ls” failed due to invalid format.
322916Request for device ‘%ls’ timed out.
323016Operation on device ‘%ls’ exceeded retry count.
323116The media loaded on “%ls” is formatted to support %d media families, but %d media families are expected according to the backup device specification.
323216The volume mounted on “%ls” does not have the expected backup set identity. The volume may be obsolete due to a more recent overwrite of this media family. In that case, locate the correct volume with sequence number %d of media family %d.
323416Logical file ‘%.*ls’ is not part of database ‘%ls’. Use RESTORE FILELISTONLY to list the logical file names.
323516The file “%.*ls” is not part of database “%ls”. You can only list files that are members of this database.
323816The Estimate for the Backup size exceeds the maximum allowed file size on the remote endpoint.
323916The backup set on device ‘%ls’ uses a feature of the Microsoft Tape Format not supported by SQL Server.
324016Backup to mirrored media sets requires all mirrors to append. Provide all members of the set, or reformat a new media set.
324116The media family on device ‘%ls’ is incorrectly formed. SQL Server cannot process this media family.
324216The file on device ‘%ls’ is not a valid Microsoft Tape Format backup set.
324316The media family on device ‘%ls’ was created using Microsoft Tape Format version %d.%d. SQL Server supports version %d.%d.
324416Descriptor block size exceeds %d bytes. Use a shorter name and/or description string and retry the operation.
324516Could not convert a string to or from Unicode, %ls.
324616The media family on device ‘%ls’ is marked as nonappendable. Reissue the statement using the INIT option to overwrite the media.
324716The volume on device ‘%ls’ has the wrong media sequence number (%d). Remove it and insert volume %d.
324916The 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.
325016The value ‘%d’ is not within range for the %ls parameter.
325110The media family on device ‘%ls’ is complete. The device is now being reused for one of the remaining families.
325216Failed to copy snapshot with name  ‘%ls’, timestamp ‘%ls’ to destination ‘%ls’. Error returned ‘%ls’.
325316The block size parameter must supply a value that is a power of 2.
325416The volume on device ‘%ls’ is empty.
325516The data set on device ‘%ls’ is a SQL Server backup set not compatible with this version of SQL Server.
325616The backup set on device ‘%ls’ was terminated while it was being created and is incomplete. RESTORE sequence is terminated abnormally.
325716There 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.
325816The volume on the device “%ls” is not part of the media set that is currently being processed. Ensure that the backup devices are loaded with the correct media.
325916Failed to copy blob with name  ‘%ls’, to destination ‘%ls’. Error returned ‘%ls’.
326016An internal buffer has become full.
326116SQL Server cannot use the virtual device configuration.
326210The backup set on file %d is valid.
326316Cannot 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.
326416The operation did not proceed far enough to allow RESTART. Reissue the statement without the RESTART qualifier.
326516The login has insufficient authority. Membership of the sysadmin role is required to use VIRTUAL_DEVICE with BACKUP or RESTORE.
326616The backup data at the end of “%ls” is incorrectly formatted. Backup sets on the media might be damaged and unusable. To determine the backup sets on the media, use RESTORE HEADERONLY. To determine the usability of the backup sets, run RESTORE VERIFYONLY. If all of the backup sets are incomplete, reformat the media using BACKUP WITH FORMAT, which destroys all the backup sets.
326716Insufficient resources to create UMS scheduler.
326816Cannot use the backup file ‘%ls’ because it was originally formatted with sector size %d and is now on a device with sector size %d.
326916Cannot restore the file ‘%ls’ because it was originally written with sector size %d; ‘%ls’ is now on a device with sector size %d.
327016An internal consistency error has occurred. This error is similar to an assert. Contact technical support for assistance.
327116A nonrecoverable I/O error occurred on file “%ls:” %ls.
327216The ‘%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.
327316The ambiguity for master has be detected. please specify PHYSMASTER or replicatedmaster database explicitly in action ‘%ls’.
327616WITH SNAPSHOT can be used only if the backup set was created WITH SNAPSHOT.
327716WITH SNAPSHOT must be used with only one virtual device.
327816Failed to encrypt string %ls
327916Access is denied due to a password failure
328016Backups on raw devices are not supported. ‘%ls’ is a raw device.
328110Released and initiated rewind on ‘%ls’.
328316The file “%ls” failed to initialize correctly. Examine the error logs for more details.
328416Filemark on device ‘%ls’ is not aligned. Re-issue the Restore statement with the same blocksize used to create the backupset: ‘%d’ looks like a possible value.
328510Filemark on device ‘%ls’ appears not to be aligned. The restore operation will proceed using less efficient I/O.  To avoid this, re-issue the Restore statement with the same blocksize used to create the backupset: ‘%d’ looks like a possible value.
328616Backup failed because there is a mismatch in file metadata for file %d.
328716The file ID %d on device ‘%ls’ is incorrectly formed and can not be read.
328816Credential name %.*ls does not exist or user does not have permission to access it.
328916A Backup device of type URL was specified without a Credential, Backup/Restore operation cannot proceed.
329016Backup to URL received an exception from the remote endpoint. Exception Message: %.*ls
329116URL device type was specified, and a disallowed option %ls was specified.
329216A failure occurred while attempting to execute Backup or Restore with a URL device specified. Consult the operating system error log for details.
329316An error occurred while Backup/Restore to URL was initializing. Error message: %.*ls.
329416Use of the URL device type is limited to a single device during Backup and Restore operations.
329516Backup To URL error: Exclusive access to the file %.*ls could not be obtained.
329616The file %.*ls exists on the remote endpoint, and WITH FORMAT was not specified. Backup cannot proceed.
329716The URL provided does not meet specified requirements. The URL must be either resolvable as an absolute or relative URI, has or can be composed as an HTTP or HTTPS scheme, and cannot contain a query component.
329816Backup/Restore to URL device error: %.*ls.
329916BackupToUrl initiated.
330121The transaction log contains a record (logop %d) that is not valid. The log has been corrupted. Restore the database from a full backup, or repair the database.
330221Redoing of logged operations in database ‘%.*ls’ failed to reach end of log at log record ID %S_LSN.  This indicates corruption around log record ID %S_LSN. Restore the database from a full backup, or repair the database.
330310Remote harden of transaction ‘%.*ls’ (ID 0x%016I64x %ls) started at %S_DATE in database ‘%ls’ at LSN %S_LSN failed.
331321During redoing of a logged operation in database ‘%.*ls’ (page %S_PGID if any), an error occurred at log record ID %S_LSN. Typically, the specific failure is previously logged as an error in the operating system error log. Restore the database from a full backup, or repair the database.
331421During undoing of a logged operation in database ‘%.*ls’ (page %S_PGID if any), an error occurred at log record ID %S_LSN. Typically, the specific failure is logged previously as an error in the operating system error log. Restore the database or file from a backup, or repair the database.
331521During rollback, the following process did not hold an expected lock: process %d with mode %d at level %d for row %S_RID in database ‘%.*ls’ under transaction %S_XID. Restore a backup of the database, or repair the database.
331621During undo of a logged operation in database ‘%.*ls’, an error occurred at log record ID %S_LSN. The row was not found. Restore the database from a full backup, or repair the database.
340110Errors occurred during recovery while rolling back a transaction. The transaction was deferred. Restore the bad page or file, and re-run recovery.
340210The database ‘%ls’ is marked %ls and is in a state that does not allow recovery to be run.
340310Recovering only master database because traceflag 3608 was specified. This is an informational message only. No user action is required.
340410Failed to check for new installation or a renamed server at startup. The logic for this check has failed unexpectedly. Run setup again, or fix the problematic registry key.
340610%d transactions rolled forward in database ‘%.*ls’ (%d:%d). This is an informational message only. No user action is required.
340710%d transactions rolled back in database ‘%.*ls’ (%d:%d). This is an informational message only. No user action is required.
340810Recovery is complete. This is an informational message only. No user action is required.
340916Performance counter shared memory setup failed with error %d. Reinstall sqlctr.ini for this instance, and ensure that the instance login account has correct registry permissions.
341010Data in filegroup %s is offline, and deferred transactions exist. Use RESTORE to recover the filegroup, or drop the filegroup if you never intend to recover it. Log truncation cannot occur until this condition is resolved.
341121Configuration block version %d is not a valid version number. SQL Server is exiting. Restore the master database or reinstall.
341210Warning: The server instance was started using minimal configuration startup option (-f). Starting an instance of SQL Server with minimal configuration places the server in single-user mode automatically.  After the server has been started with minimal configuration, you should change the appropriate server option value or values, stop, and then restart the server.
341321Database ID %d. Could not mark database as suspect. Getnext NC scan on sys.databases.database_id failed. Refer to previous errors in the error log to identify the cause and correct any associated problems.
341410An error occurred during recovery, preventing the database ‘%ls’ (%d:%d) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
341516Database ‘%.*ls’ cannot be upgraded because it is read-only, has read-only files or the user does not have permissions to modify some of the files. Make the database or files writeable, and rerun recovery.
341616The server contains read-only files that must be made writable before the server can be recollated.
341721Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
341810Recovery is unable to defer error %d. Errors can only be deferred in databases using the full recovery model and an active backup log chain.
341916Recovery for database ‘%.*ls’ is being skipped because it requires an upgrade but is marked for Standby. Use RESTORE DATABASE WITH NORECOVERY to take the database back to a Restoring state and continue the restore sequence.
342021Database snapshot ‘%ls’ has failed an IO operation and is marked suspect.  It must be dropped and recreated.
342110Recovery completed for database %ls (database ID %d) in %I64d second(s) (analysis %I64d ms, redo %I64d ms, undo %I64d ms [system undo %I64d ms, regular undo %I64d ms].) This is an informational message only. No user action is required.
342210Database %ls was shutdown due to error %d in routine ‘%hs’. Restart for non-snapshot databases will be attempted after all connections to the database are aborted.
342310Info: The server instance was started using multiuser, minimal configuration startup option (-M).
342910Recovery could not determine the outcome of a cross-database transaction %S_XID, named ‘%.*ls’, in database ‘%.*ls’ (database ID %d:%d). The coordinating database (database ID %d:%d) was unavailable. The transaction was assumed to be committed. If the transaction was not committed, you can retry recovery when the coordinating database is available.
343121Could not recover database ‘%.*ls’ (database ID %d) because of unresolved transaction outcomes. Microsoft Distributed Transaction Coordinator (MS DTC) transactions were prepared, but MS DTC was unable to determine the resolution. To resolve, either fix MS DTC, restore from a full backup, or repair the database.
343420Cannot change sort order or locale. An unexpected failure occurred while trying to reindex the server to a new collation. SQL Server is shutting down. Restart SQL Server to continue with the sort order unchanged. Diagnose and correct previous errors and then retry the operation.
343721An error occurred while recovering database ‘%.*ls’. Unable to connect to Microsoft Distributed Transaction Coordinator (MS DTC) to check the completion status of transaction %S_XID. Fix MS DTC, and run recovery again.
344121During startup of warm standby database ‘%.*ls’ (database ID %d), its standby file (‘%ls’) was inaccessible to the RESTORE statement. The operating system error was ‘%ls’. Diagnose the operating system error, correct the problem, and retry startup.
344321Database ‘%ls’ (database ID %d:%d) was marked for standby or read-only use, but has been modified. The RESTORE LOG statement cannot be performed. Restore the database from a backup.
344521File ‘%ls’ is not a valid undo file for database ‘%.*ls (database ID %d). Verify the file path, and specify the correct file.
344616Primary log file is not available for database ‘%ls’ (%d:%d).  The log cannot be backed up.
344716Could not activate or scan all of the log files for database ‘%.*ls’.
344821Rollback encountered a page with a log sequence number (LSN) less than the original log record LSN. Could not undo log record %S_LSN, for transaction ID %S_XID, on page %S_PGID, database ‘%ls’ (%d:%d). Page information: LSN = %S_LSN, type = %ld. Log information: OpCode = %ld, context %ld. Restore or repair the database.
344921SQL 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 restore the database.
345010Recovery 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.
345210Recovery of database ‘%.*ls’ (%d) detected possible identity value inconsistency in table ID %d. Run DBCC CHECKIDENT (‘%.*ls’).
345316This version cannot redo any index creation or non-logged operation done by SQL Server 7.0.  Further roll forward is not possible.
345410Recovery is writing a checkpoint in database ‘%.*ls’ (%d). This is an informational message only. No user action is required.
345621Could 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 from a backup of the database, or repair the database.
345721Transactional file system resource manager ‘%.*ls’ failed to recover. For more information, see the accompanying error message, which determines the appropriate user action.
345816Recovery cannot scan database “%.*ls” for dropped allocation units because an unexpected error has occurred. These allocation units cannot be cleaned up.
345916Recovery of database “%.*ls” failed to redo a file add for file “%.*ls”. Please delete the file and retry.
346021Failed to shutdown a database (database ID %d) that contains memory-optimized data. Restart SQL Server to bring the database to a consistent state. If the database fails to recover after restart, repair or restore the database.
346121Failed to wait for XTP %ls to complete during recovery.
346210Redo observed a higher LSN on the PFS page %S_PGID for transaction ID %S_XID, database ‘%.*ls’ (database ID %d). Redo LSN: %S_LSN, Page: LSN = %S_LSN, PrevPageLSN: %S_LSN. This can happen in the presence of concurrent PFS updates. No user action is required.
346321An error occurred while recovering database ‘%.*ls’. Transaction outcome could not be resolved.
346416An error occurred while resolving the deferred transaction. Transaction outcome: %d, IsDeferred: %ls.
346516An error occurred while resolving the deferred transaction. Transaction not found.
346610Restore was successful but deferred transactions remain. These transactions cannot be resolved because there are data or keys in the enclave that is unavailable. Either use sp_enclave_send_keys to send keys to the enclave, or use RESTORE to make that data available or drop the filegroups if you never need this data again. Dropping the filegroup results in a defunct filegroup.
346710Restore was successful but deferred transactions remain. These transactions cannot be resolved because there are data or keys in the enclave that is unavailable. For keys, since there is no enclave configured, SQL may resolve deferred transactions by invalidating indexes on encrypted columns; please check the error log.For the data, either use RESTORE to make that data available or drop the filegroups if you never need this data again. Dropping the filegroup results in a defunct filegroup.
350514Only the owner of database “%.*ls” or someone with relevant permissions can run the CHECKPOINT statement.
360410Duplicate key was ignored.
360516Schema verification failed for database ‘%.*ls’.
360610Arithmetic overflow occurred.
360710Division by zero occurred.
360816Cannot allocate a GUID for the token.
360916The transaction ended in the trigger. The batch has been aborted.
361110%hs SQL Server Execution Times:%hs   CPU time not measured under fiber mode,  elapsed time = %lu ms.
361210%hs SQL Server Execution Times:%hs   CPU time = %lu ms,  elapsed time = %lu ms.
361310SQL Server parse and compile time: %hs   CPU time = %lu ms, elapsed time = %lu ms.
361510Table ‘%.*ls’. Scan count %d, logical reads %d, physical reads %d, page server reads %d, read-ahead reads %d, page server read-ahead reads %d, lob logical reads %d, lob physical reads %d, lob page server reads %d, lob read-ahead reads %d, lob page server read-ahead reads %d.
361616An error was raised during trigger execution. The batch has been aborted and the user transaction, if any, has been rolled back.
361910Could not write a checkpoint record in database %ls because the log is out of space. Contact the database administrator to truncate the log or allocate more space to the database log files.
362010Automatic checkpointing is disabled in database ‘%.*ls’ because the log is out of space. Automatic checkpointing will be enabled when the database owner successfully checkpoints the database. Contact the database owner to either truncate the log file or add more disk space to the log. Then retry the CHECKPOINT statement.
362110The statement has been terminated.
362210Warning: An invalid floating point operation occurred.
362316An invalid floating point operation occurred.
362420A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a Hotfix from Technical Support.
362520‘%hs’ is not yet implemented.
362717New parallel operation cannot be started due to too many parallel operations executing at this time. Use the “max worker threads” configuration option to increase the number of allowable threads, or reduce the number of parallel operations running on the system.
362824The Database Engine received a floating point exception from the operating system while processing a user request. Try the transaction again. If the problem persists, contact your system administrator.
363316The operating system returned the error ‘%ls’ while attempting ‘%ls’ on ‘%ls’ at ‘%hs'(%d).
363416The operating system returned the error ‘%ls’ while attempting ‘%ls’ on ‘%ls’.
363516An error occurred while processing ‘%ls’ metadata for database id %d, file id %d, and transaction=’%.*ls’. Additional Context=’%ls’. Location=’%hs'(%d). Retry the operation; if the problem persists, contact the database administrator to review locking and memory configurations. Review the application for possible deadlock conflicts.
363616An error occurred while processing ‘%ls’ metadata for database id %d file id %d.
363716A parallel operation cannot be started from a DAC connection.
364110Total logical reads %lu, physical reads %lu, remote reads %lu, writes %lu.
364210Table ‘%.*ls’. Segment reads %u, segment skipped %u.
364316The operation elapsed time exceeded the maximum time specified for this operation. The execution has been stopped.
364410Prefaulter task failed for file %ls with error %d.
370111Cannot %S_MSG the %S_MSG ‘%.*ls’, because it does not exist or you do not have permission.
370216Cannot drop database “%.*ls” because it is currently in use.
370316Cannot detach the %S_MSG ‘%.*ls’ because it is currently in use.
370516Cannot use DROP %ls with ‘%.*ls’ because ‘%.*ls’ is a %S_MSG. Use %ls.
370616Cannot %S_MSG a database snapshot.
370716Cannot detach a suspect or recovery pending database. It must be repaired or dropped.
370816Cannot %S_MSG the %S_MSG ‘%.*ls’ because it is a system %S_MSG.
370916Cannot %S_MSG the database while the database snapshot “%.*ls” refers to it. Drop that database first.
371016Cannot detach an opened database when the server is in minimally configured mode.
371616The %S_MSG ‘%.*ls’ cannot be dropped because it is bound to one or more %S_MSG.
371716Cannot drop a default constraint by DROP DEFAULT statement. Use ALTER TABLE to drop a constraint default.
372116Type ‘%.*ls’ cannot be renamed because it is being referenced by object ‘%.*ls’.
372316An explicit DROP INDEX is not allowed on index ‘%.*ls’. It is being used for %ls constraint enforcement.
372416Cannot %S_MSG the %S_MSG ‘%.*ls’ because it is being used for replication.
372516The constraint ‘%.*ls’ is being referenced by table ‘%.*ls’, foreign key constraint ‘%.*ls’.
372616Could not drop object ‘%.*ls’ because it is referenced by a FOREIGN KEY constraint.
372710Could not drop constraint. See previous errors.
372816‘%.*ls’ is not a constraint.
372916Cannot %ls ‘%.*ls’ because it is being referenced by object ‘%.*ls’.
373016Cannot drop the default constraint ‘%.*ls’ while it is being used by a foreign key as SET DEFAULT referential action.
373216Cannot drop type ‘%.*ls’ because it is being referenced by object ‘%.*ls’. There may be other objects that reference this type.
373316Constraint ‘%.*ls’ does not belong to table ‘%.*ls’.
373416Could not drop the primary key constraint ‘%.*ls’ because the table has an XML or spatial index.
373516The primary key constraint ‘%.*ls’ on table ‘%.*ls’ cannot be dropped because change tracking is enabled on the table. Change tracking requires a primary key constraint on the table. Disable change tracking before dropping the constraint.
373716Could not delete file ‘%ls’. See the SQL Server error log for more information.
373810Deleting database file ‘%ls’.
373911Cannot %ls the index ‘%.*ls’ because it is not a statistics collection.
374016Cannot drop the %S_MSG ‘%.*ls’ because at least part of the table resides on a read-only filegroup.
374116Cannot drop the %S_MSG ‘%.*ls’ because at least part of the table resides on an offline filegroup.
374316The database ‘%.*ls’ is enabled for database mirroring. Database mirroring must be removed before you drop the database.
374416Only a single clause is allowed in a statement where an index is dropped online.
374516Only a clustered index can be dropped online.
374616Cannot drop the clustered index of view ‘%.*ls’ because the view is being used for replication.
374716Cannot drop a clustered index created on a view using drop clustered index clause. Clustered index ‘%.*ls’ is created on view ‘%.*ls’.
374816Cannot drop non-clustered index ‘%.*ls’ using drop clustered index clause.
374916Cannot drop XML Index ‘%.*ls’ using old ‘Table.Index’ syntax, use ‘Index ON Table’ syntax instead.
375010Warning: Index ‘%.*ls’ on %S_MSG ‘%.*ls’ was disabled as a result of disabling the clustered index on the %S_MSG.
375116Cannot use SP_DROPEXTENDEDPROC or DBCC DROPEXTENDEDPROC with ‘%.*ls’ because ‘%.*ls’ is a %S_MSG. Use %ls.
375216The database ‘%.*ls’ is currently joined to an availability group.  Before you can drop the database, you need to remove it from the availability group.
375316Cannot %S_MSG the federation member ‘%.*ls’, because the federation root does not exist.
375416TRUNCATE TABLE statement failed. Index ‘%.*ls’ uses partition function ‘%.*ls’, but table ‘%.*ls’ uses non-equivalent partition function ‘%.*ls’. Index and table must use an equivalent partition function.
375516Cannot drop a database with file snapshots on it. Please detach the database instead of dropping or delete the file snapshots and retry the drop.
375616TRUNCATE TABLE statement failed. Index ‘%.*ls’ is not partitioned, but table ‘%.*ls’ uses partition function ‘%.*ls’. Index and table must use an equivalent partition function.
375716WAIT_AT_LOW_PRIORITY clause is not permitted without ONLINE = ON option, for drop clustered %S_MSG ‘%.*ls’ on Table ‘%.*ls’.
375816Multiple %S_MSG cannot be dropped when WAIT_AT_LOW_PRIORITY clause is specified.
375916%.*ls constraint ‘%.*ls’ cannot be dropped when WAIT_AT_LOW_PRIORITY clause is used.
376016Cannot drop index ‘%.*ls’ on view ‘%.*ls’ that has SNAPSHOT_MATERIALIZATION.
376116Could not delete SBS backed file ‘%ls’. See the SQL Server error log for more information.
380016Column name ‘%.*ls’ is not sufficiently different from the names of other columns in the table ‘%.*ls’.
380110Warning: The index “%.*ls” on “%.*ls”.”%.*ls” may be impacted by the collation upgrade. Run DBCC CHECKTABLE.
380210Warning: The constraint “%.*ls” on “%.*ls”.”%.*ls” may be impacted by the collation upgrade. Disable and enable WITH CHECK.
380310Warning: The index “%.*ls” on “%.*ls”.”%.*ls” is disabled because the implementation of the checksum function has changed.
380410Warning: The check constraint “%.*ls” on table “%.*ls”.”%.*ls” is disabled because the implementation of the checksum function has changed.
380510Warning: Index “%.*ls” on table “%.*ls”.”%.*ls” might be corrupted because it references computed column “%.*ls” containing a non-deterministic conversion from string to date. Run DBCC CHECKTABLE to verify index. Consider using explicit CONVERT with deterministic date style such as 121. Computed column indexes referencing non-deterministic expressions can’t be created in 90 compatibility mode. See Books Online topic “Creating Indexes on Computed Columns” for more information.
380610Warning: Indexed view “%.*ls”.”%.*ls” might be corrupted because it contains a non-deterministic conversion from string to date. Run DBCC CHECKTABLE to verify view. Consider using explicit CONVERT with deterministic date style such as 121. Indexed views referencing non-deterministic expressions can’t be created in 90 compatibility mode. See Books Online topic “Creating Indexed Views” for more information.
380717Create failed because all available identifiers have been exhausted.
380810Warning: The index “%.*ls” on “%.*ls”.”%.*ls” is disabled because the index is defined on a view with ignore_dup_key index option. Drop the index and, if possible, recreate it without ignore_dup_key option. You may need to change the logical structure of the view to ensure all rows are unique.
380916Upgrade of database “%.*ls” failed because index “%.*ls” on object ID %d has the same name as that of another index on the same table.
381010Event notification “%.*ls” on assembly is dropped.
381110Event notification “%.*ls” on service queue is dropped as broker instance is not specified.
381210Event notification “%.*ls” on object is dropped.
381316Upgrade of login ‘%.*ls’ failed because its name or sid is a duplicate of another login or server role.
381416Local login mapped to remote login ‘%.*ls’ on server ‘%.*ls’ is invalid. Drop and recreate the remote login before upgrade.
381516Local login mapped to linked login ‘%.*ls’ on server ‘%.*ls’ is invalid. Drop and recreate the linked login before upgrade.
381616Upgrade of login ‘%.*ls’ failed because its password hash is invalid. Update the login password before upgrade.
381710Warning: The index “%.*ls” on “%.*ls”.”%.*ls” was disabled because the implementation of “%.*ls” have changed.
381910Warning: The check constraint “%.*ls” on “%.*ls”.”%.*ls” was disabled and set as not trusted because the implementation of “%.*ls” have changed.
382110Warning: The foreign key constraint “%.*ls” on “%.*ls”.”%.*ls” was disabled because the implementation of ‘%.*ls’ have changed.
382210Warning: The heap “%.*ls”.”%.*ls” has persisted computed columns that depends on a geometry or geography methods and may contain out-of-date information. Because of this, DBCC may report inconsistencies on this table.  The persisted computed columns depending on geometry or geography methods should be unpersisted and persisted again to refresh the data.
382310Warning: The object “%.*ls”.”%.*ls” could not be bound and was ignored during upgrade. Consider reviewing and correcting its definition.
382710Warning: The table “%.*ls”.”%.*ls” is unavailable because it contains a persisted computed column that depends on “%.*ls”, the implementation of which has changed. Rebuild the table offline and reconstruct the persisted computed column.
383010Metadata cache coherency check for database ID(%d) did not find any inconsistency.
385110An invalid row (%ls) was found in the system table sys.%ls%ls.
385210Row (%ls) in sys.%ls%ls does not have a matching row (%ls) in sys.%ls%ls.
385310Attribute (%ls) of row (%ls) in sys.%ls%ls does not have a matching row (%ls) in sys.%ls%ls.
385410Attribute (%ls) of row (%ls) in sys.%ls%ls has a matching row (%ls) in sys.%ls%ls that is invalid.
385510Attribute (%ls) exists without a row (%ls) in sys.%ls%ls.
385610Attribute (%ls) exists but should not for row (%ls) in sys.%ls%ls.
385710The attribute (%ls) is required but is missing for row (%ls) in sys.%ls%ls.
385810The attribute (%ls) of row (%ls) in sys.%ls%ls has an invalid value.
385910Warning: The system catalog was updated directly in database ID %d, most recently at %S_DATE.
386010Cannot upgrade database ID 32767. This ID value is reserved for SQL Server internal use.
386210CLR type ‘%.*ls’.’%.*ls’ is disabled because the on disk format for this CLR type has been changed. Use DROP TYPE to remove this disabled type.
386423Could not find an entry for index with ID %d on object with ID %d in database with ID %d. Possible schema corruption. Run DBCC CHECKDB.
386516The operation on object ‘%.*ls’ is blocked. The object is a FileTable system defined object and user modifications are not allowed.
386610The operation on FileTable system defined object ‘%.*ls’ was allowed because of traceflag settings. To prevent this informational message from appearing in the error log, use DBCC TRACEOFF to turn off the trace flag.
386710The FileTable object ‘%.*ls’ contains system defined constraints that cannot be modified as long as the FILETABLE_NAMESPACE option is enabled on the table. Only user defined constraints have been updated.
386810Failed to start tempdb metadata memory-optimized mode. Continuing tempdb startup in SQL mode. Please run ALTER SERVER CONFIGURATION TEMPDB METADATA MEMORY_OPTIMIZED ON once again and restart to retry.
386910The desired memory-optimized configuration is already set. No further action is necessary.
387010The tempdb metadata memory-optimized configuration has been set to ‘%S_MSG’. Restart SQL server for the new setting to take effect.
387110Tempdb started with memory-optimized metadata.
387210The hybrid buffer pool memory-optimized configuration has been set to ‘%S_MSG’. Restart SQL server for the new setting to take effect.
387310Hybrid buffer pool started with memory-optimized metadata.
387416Resource pool ‘%.*ls’ does not exist or resource governor has not been reconfigured.
387516Internal resource pool cannot be used for tempdb
387616Resource pool setting for tempdb failed. Retry with a valid pool.
390116The transaction name must be specified when it is used with the mark option.
390216The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION.
390316The ROLLBACK TRANSACTION request has no corresponding BEGIN TRANSACTION.
390421Cannot unsplit logical page %S_PGID in object ‘%.*ls’, in database ‘%.*ls’. Both pages together contain more data than will fit on one page.
390516The number of nested transactions has reached the maximum allowed value of 4294967296.
390616Failed to update database “%.*ls” because the database is read-only.
390716Transaction aborted when accessing versioned row in table ‘%.*ls’ in database ‘%.*ls’. Requested versioned row was not found in persistent version store. Your database is probably out of space. Please refer to BOL on how to configure database size.
390816Could not run BEGIN TRANSACTION in database ‘%.*ls’ because the database is in emergency mode or is damaged and must be restarted.
390916Session binding token is invalid.
391016Transaction context in use by another session.
391116Persistent version store is full. New version(s) could not be added. A transaction that needs to access the version store may be rolled back. Please refer to BOL on how to increase database max size.
391216Cannot bind using an XP token while the server is not in an XP call.
391316TDS reset connection protocol error. Client driver requested both ResetConnectionKeepLocalXact and ResetConnectionKeepDTCXact at the same time. This is not expected in server.
391416The data type “%s” is invalid for transaction names or savepoint names. Allowed data types are char, varchar, nchar, varchar(max), nvarchar, and nvarchar(max).
391516Cannot use the ROLLBACK statement within an INSERT-EXEC statement.
391616Cannot use the COMMIT statement within an INSERT-EXEC statement unless BEGIN TRANSACTION is used first.
391716Session is bound to a transaction context that is in use. Other statements in the batch were ignored.
391816The statement or function must be executed in the context of a user transaction.
391916Cannot enlist in the transaction because the transaction has already been committed or rolled back.
392010The WITH MARK option only applies to the first BEGIN TRAN WITH MARK statement. The option is ignored.
392116Cannot get a transaction token if there is no transaction active. Reissue the statement after a transaction has been started
392216Cannot enlist in the transaction because the transaction does not exist.
392310Cannot use transaction marks on database ‘%.*ls’ with bulk-logged operations that have not been backed up. The mark is ignored.
392410The 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.
392516Invalid transaction mark name. The ‘LSN:’ prefix is reserved.
392610The transaction active in this session has been committed or aborted by another session.
392710The session had an active transaction when it tried to enlist in a Distributed Transaction Coordinator transaction.
392816The marked transaction “%.*ls” failed. A timeout occurred while attempting to place a mark in the log by committing the marked transaction. This can be caused by contention with Microsoft Distributed Transaction Coordinator (MS DTC) transactions or other local marked transaction that have prepared, but not committed or aborted. Try the operation again and if the error persists, determine the source of the contention.
392916No distributed or bound transaction is allowed in single user database.
393016The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction.
393116The current transaction cannot be committed and cannot be rolled back to a savepoint. Roll back the entire transaction.
393216The save point name “%.*ls” that was provided is too long. The maximum allowed length is %d characters.
393316Cannot promote the transaction to a distributed transaction because there is an active save point in this transaction.
393414The current user cannot use this FILESTREAM transaction context. To obtain a valid FILESTREAM transaction context, use GET_FILESTREAM_TRANSACTION_CONTEXT.
393516A FILESTREAM transaction context could not be initialized. This might be caused by a resource shortage. Retry the operation. Error code: 0x%x.
393616The transaction could not be committed because an error occurred while tyring to flush FILESTREAM data to disk. A file may have been open at commit time or a disk I/O error may have occurred. ‘%.*ls’ was one of the one or more files involved.  ErorrCode: 0x%x
393716While rolling back a transaction, an error occurred while trying to deliver a rollback notification to the FILESTREAM filter driver.  Error code: 0x%0x.
393818The transaction has been stopped because it conflicted with the execution of a FILESTREAM close operation using the same transaction.  The transaction will be rolled back.
393916An uncommittable transaction was detected at the beginning of the batch. The transaction was rolled back. This was caused by an error that occurred during the processing of a FILESTREAM request in the context of this transaction.
394016Failed to acquire necessary locks during commit and the transaction was rolled back.
394116The transaction cannot modify an object that is published for replication or has Change Data Capture enabled because the transaction started before replication or Change Data Capture was enabled on the database. Retry the transaction.
394710The transaction was aborted because the secondary compute failed to catch up redo. Retry the transaction.
394816The transaction was terminated because of the availability replica config/state change or because ghost records are being deleted on the primary and the secondary availability replica that might be needed by queries running under snapshot isolation. Retry the transaction.
394916Transaction aborted when accessing versioned row in table ‘%.*ls’ in database ‘%.*ls’. Requested versioned row was not found because the readable secondary access is not allowed for the operation that attempted to create the version. This might be timing related, so try the query again later.
395016Version store scan timed out when attempting to read the next row. Please try the statement again later when the system is not as busy.
395116Transaction failed in database ‘%.*ls’ because the statement was run under snapshot isolation but the transaction did not start in snapshot isolation. You cannot change the isolation level of the transaction to snapshot after the transaction has started unless the transaction was originally started under snapshot isolation level.
395216Snapshot isolation transaction failed accessing database ‘%.*ls’ because snapshot isolation is not allowed in this database. Use ALTER DATABASE to allow snapshot isolation.
395316Snapshot isolation transaction failed in database ‘%.*ls’ because the database was not recovered when the current transaction was started. Retry the transaction after the database has recovered.
395416Snapshot isolation transaction failed to start in database ‘%.*ls’ because the ALTER DATABASE command that disallows snapshot isolation had started before this transaction began. The database is in transition to OFF state. You will either need to change the isolation level of the transaction or re-enable the snapshot isolation in the database.
395516Snapshot isolation transaction failed in database ‘%.*ls’ because the recovery was skipped for this database. You must recover the database before you can run a transaction under snapshot isolation.
395616Snapshot isolation transaction failed to start in database ‘%.*ls’ because the ALTER DATABASE command which enables snapshot isolation for this database has not finished yet. The database is in transition to pending ON state. You must wait until the ALTER DATABASE Command completes successfully.
395716Snapshot isolation transaction failed in database ‘%.*ls’ because the database did not allow snapshot isolation when the current transaction started. It may help to retry the transaction.
395816Transaction aborted when accessing versioned row in table ‘%.*ls’ in database ‘%.*ls’. Requested versioned row was not found. Your tempdb is probably out of space. Please refer to BOL on how to configure tempdb for versioning.
395910Version store is full. New version(s) could not be added. A transaction that needs to access the version store may be rolled back. Please refer to BOL on how to configure tempdb for versioning.
396016Snapshot isolation transaction aborted due to update conflict. You cannot use snapshot isolation to access table ‘%.*ls’ directly or indirectly in database ‘%.*ls’ to update, delete, or insert the row that has been modified or deleted by another transaction. Retry the transaction or change the isolation level for the update/delete statement.
396116Snapshot isolation transaction failed in database ‘%.*ls’ because the object accessed by the statement has been modified by a DDL statement in another concurrent transaction since the start of this transaction.  It is disallowed because the metadata is not versioned. A concurrent update to metadata can lead to inconsistency if mixed with snapshot isolation.
396216Bind to another transaction while executing SQL Server internal query is not supported. Check your logon trigger definition and remove any sp_bindsession usage if any. If this error is not happening during logon trigger execution, contact production support team.
396316Transaction failed in database ‘%.*ls’ because distributed transactions are not supported under snapshot isolation.
396416Transaction failed because this DDL statement is not allowed inside a snapshot isolation transaction. Since metadata is not versioned, a metadata change can lead to inconsistency if mixed within snapshot isolation.
396516The PROMOTE TRANSACTION request failed because there is no local transaction active.
396617Transaction is rolled back when accessing version store. It was earlier marked as victim when the version store was shrunk due to insufficient space in tempdb. This transaction was marked as a victim earlier because it may need the row version(s) that have already been removed to make space in tempdb. Retry the transaction
396717Insufficient space in tempdb to hold row versions.  Need to shrink the version store to free up some space in tempdb. Transaction (id=%I64d xsn=%I64d spid=%d elapsed_time=%d) has been marked as victim and it will be rolled back if it accesses the version store. If the problem persists, the likely cause is improperly sized tempdb or long running transactions. Please refer to BOL on how to configure tempdb for versioning.
396810Snapshot isolation or read committed snapshot is not available in database ‘%.*ls’ because SQL Server was started with one or more undocumented trace flags that prevent enabling database for versioning. Transaction started with snapshot isolation will fail and a query running under read committed snapshot will succeed but will resort back to lock based read committed.
396916Distributed transaction is not supported while running SQL Server internal query. Check your logon trigger definition and remove any distributed transaction usage if any. If this error is not happening during logon trigger execution, contact production support team.
397016This operation conflicts with another pending operation on this transaction. The operation failed.
397116The server failed to resume the transaction. Desc:%I64x.
397220Incoming Tabular Data Stream (TDS) protocol is incorrect. Transaction Manager event has wrong length. Event type: %d. Expected length: %d. Actual length: %d.
397316The database is currently being used by another thread under the same workspace in exclusive mode. The operation failed.
397416The number of databases in exclusive mode usage under a workspace is limited. Because the limit has been exceeded, the operation failed.
397516The varchar(max) data type is not supported for sp_getbindtoken. The batch has been aborted.
397616The transaction name has the odd length %d. The batch has been aborted.
397716The savepoint name cannot be NULL. The batch has been aborted.
397816Beginning a new transaction after rollback to save point is not allowed.
397916The TM request is longer than expected. The request is not processed.
398016The request failed to run because the batch is aborted, this can be caused by abort signal sent from client, or another request is running in the same session, which makes the session busy.
398116The transaction operation cannot be performed because there are pending requests working on this transaction.
398216New transaction is not allowed to be started while DTC or bound transaction is active.
398316The operation failed because the session is not single threaded.
398416Cannot acquire a database lock during a transaction change.
398516An error occurred during the changing of transaction context. This is usually caused by low memory in the system. Try to free up more memory.
398619The transaction timestamps ran out. Restart the server.
398710SNAPSHOT ISOLATION is always enabled in this database.
398816New transaction is not allowed because there are other threads running in the session.
398916New request is not allowed to start because it should come with valid transaction descriptor.
399016Transaction is not allowed to commit inside of a user defined routine, trigger or aggregate because the transaction is not started in that CLR level. Change application logic to enforce strict transaction nesting.
399116The context transaction which was active before entering user defined routine, trigger or aggregate “%.*ls” has been ended inside of it, which is not allowed. Change application logic to enforce strict transaction nesting.
399216Transaction count has been changed from %d to %d inside of user defined routine, trigger or aggregate “%.*ls”. This is not allowed and user transaction will be rolled back. Change application logic to enforce strict transaction nesting.
399316The user transaction that has been started in user defined routine, trigger or aggregate “%.*ls” is not ended upon exiting from it. This is not allowed and the transaction will be rolled back. Change application logic to enforce strict transaction nesting.
399416User defined routine, trigger or aggregate tried to rollback a transaction that is not started in that CLR level. An exception will be thrown to prevent execution of rest of the user defined routine, trigger or aggregate.
399516Unknown transaction isolation level %d, valid value range is 0 to 5.
399616Snapshot isolation level is not supported for distributed transaction. Use another isolation level or do not use distributed transaction.
399716A transaction that was started in a MARS batch is still active at the end of the batch. The transaction is rolled back.
399816Uncommittable transaction is detected at the end of the batch. The transaction is rolled back.
399917Failed to flush the commit table to disk in dbid %d due to error %d. Check the errorlog for more information.