SQL Server Errors or Failures from Error: 5095 to Error: 5123

SQLServerF1

 

Error: 5095, Severity: 16, A database or filegroup cannot be set to read-only mode when any files are subject to a RESTORE PAGE operation. Complete the restore sequence involving file “%ls” before attempting to transition to read-only.
Error: 5096, Severity: 16, The recovery model cannot be changed to SIMPLE when any files are subject to a RESTORE PAGE operation. Complete the restore sequence involving file “%ls” before attempting to transition to SIMPLE.
Error: 5097, Severity: 16, The container cannot be set to the offline state because changes exist that require a log backup. Take a log backup and then retry the ALTER DATABASE statement.
Error: 5098, Severity: 16, The container can not be dropped because changes exist that require a log backup. Take a log backup and then retry the ALTER DATABASE operation.
Error: 5102, Severity: 22, Attempted to open a filegroup for the invalid ID %d in database “%.*ls”.

Error: 5103, Severity: 16, MAXSIZE cannot be less than SIZE for file ‘%ls’.
Error: 5104, Severity: 16, File ‘%.*ls’ already used.
Error: 5105, Severity: 16, A file activation error occurred. The physical file name ‘%.*ls’ may be incorrect. Diagnose and correct additional errors, and retry the operation.
Error: 5108, Severity: 10, Log file ‘%.*ls’ does not match the primary file. It may be from a different database or the log may have been rebuilt previously.
Error: 5110, Severity: 16, The file “%.*ls” is on a network path that is not supported for system database files.
Error: 5111, Severity: 10, File activation failure. The physical file name “%.*ls” may be incorrect.

Error: 5112, Severity: 10, FCB::SetSize dbid %d fileid %d oldSize %d newSize %d. To prevent this informational message from appearing in the error log, use DBCC TRACEOFF to turn off the trace flag.
Error: 5113, Severity: 10, The log cannot be rebuilt because there were open transactions/users when the database was shutdown, no checkpoint occurred to the database, or the database was read-only. This error could occur if the transaction log file was manually deleted or lost due
Error: 5114, Severity: 16, Log files, offline files, restoring files, and defunct files for database snapshots should not be specified. “%.*ls” is not an eligible file for a database snapshot.
Error: 5115, Severity: 16, Only SQL Server database files can be specified for database snapshots. ‘%.*ls’ is not a SQL Server database file.
Error: 5118, Severity: 16, The file “%ls” is compressed but does not reside in a read-only database or filegroup. The file must be decompressed.
Error: 5119, Severity: 16, Cannot make the file “%.*ls” a sparse file. Make sure the file system supports sparse files.
Error: 5120, Severity: 16, Unable to open the physical file “%.*ls”. Operating system error %d: “%ls”.
Error: 5121, Severity: 16, The path specified by “%.*ls” is not in a valid directory.
Error: 5123, Severity: 16, CREATE FILE encountered operating system error %ls while attempting to open or create the physical file ‘%.*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.

Thanks,
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 *