SQL Server Errors or Failures Error: 3054 to Error: 3110



Error: 3054, Severity: 16, Differential 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.,
Error: 3055, Severity: 16, Backup destination “%.*ls” supports a FILESTREAM filegroup. This filegroup cannot be used as a backup destination. Rerun the BACKUP statement with a valid backup destination.,
Error: 3056, Severity: 16, The backup operation has detected an unexpected file in a FILESTREAM container. The backup operation will continue and include file ‘%ls’.,
Error: 3057, Severity: 16, Invalid 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.,

Error: 3058, Severity: 10, File or device name exceeds the supported limit (maximum length is:%d) and will be truncated: %.*ls.,
Error: 3059, Severity: 16, This BACKUP or RESTORE command is not supported on a database mirror or secondary replica.,
Error: 3060, Severity: 10, The restart-checkpoint file ‘%ls’ was corrupted. The restored database can not be recovered. Restart the RESTORE sequence.,
Error: 3061, Severity: 16, The restart-checkpoint file ‘%ls’ could not be opened. Operating system error ‘%ls’. Make the file available and retry the operation or, restart the RESTORE sequence.,
Error: 3062, Severity: 16, Cannot backup from a HADRON secondary because it is not in Synchronizing or Synchronized state.,

Error: 3098, Severity: 16, The 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,
Error: 3101, Severity: 16, Exclusive access could not be obtained because the database is in use.,
Error: 3102, Severity: 16, %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.,
Error: 3103, Severity: 16, A 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 PA,
Error: 3104, Severity: 16, RESTORE 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 gro,
Error: 3105, Severity: 16, RESTORE 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.,
Error: 3106, Severity: 16, The 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 com,
Error: 3107, Severity: 16, The 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.,
Error: 3108, Severity: 16, To 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.,
Error: 3109, Severity: 16, Master can only be restored and fully recovered in a single step using a full database backup. Options such as NORECOVERY, STANDBY, and STOPAT are not supported.,
Error: 3110, Severity: 14, User does not have permission to RESTORE database ‘%.*ls’.,

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.


Leave a Reply

Your email address will not be published. Required fields are marked *