SQL Server Errors or Failures from Error: 5171 to Error: 5191

SQLServerF1

 

Error: 5171, Severity: 16, %.*ls is not a primary database file.
Error: 5172, Severity: 16, The header for file ‘%ls’ is not a valid database file header. The %ls property is incorrect.
Error: 5173, Severity: 16, One or more files do not match the primary file of the database. If you are attempting to attach a database, retry the operation with the correct files. If this is an existing database, the file may be corrupted and should be restored from a backup.
Error: 5174, Severity: 16, Each file size must be greater than or equal to 512 KB.
Error: 5175, Severity: 10, The file %.*ls has been expanded to allow recovery to succeed. After recovery completes, you can increase the size of the files in the database. Contact the system administrator for assistance.

Error: 5176, Severity: 10, To allow recovery to succeed, the log file ‘%.*ls’ has been expanded beyond its maximum size. After recovery completes, you should either increase the size of the log file in the database or schedule more frequent backups of the log (under the full or bul
Error: 5177, Severity: 16, An unexpected error occurred while checking the sector size for file ‘%.*ls’. Move the file to a local NTFS volume, where the sector size can be retrieved. Check the SQL Server error log for more information.
Error: 5178, Severity: 16, Cannot use file ‘%.*ls’ because it was originally formatted with sector size %d and is now on a volume with sector size %d. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.
Error: 5179, Severity: 16, Cannot use file ‘%.*ls’, because it is on a volume with sector size %d. SQL Server supports a maximum sector size of 4096 bytes. Move the file to a volume with a compatible sector size.

Error: 5180, Severity: 22, Could not open File Control Block (FCB) for invalid file ID %d in database ‘%.*ls’. Verify the file location. Execute DBCC CHECKDB.
Error: 5181, Severity: 16, Could not restart database “%.*ls”. Reverting to the previous status.
Error: 5182, Severity: 10, New log file ‘%.*ls’ was created.
Error: 5183, Severity: 16, Cannot create the file “%ls”. Use WITH MOVE to specify a usable physical file name. Use WITH REPLACE to overwrite an existing file.
Error: 5184, Severity: 16, Cannot use file ‘%.*ls’ for clustered server. Only formatted files on which the cluster resource of the server has a dependency can be used. Either the disk resource containing the file is not present in the cluster group or the cluster resource of the Sq
Error: 5185, Severity: 16, Cannot find the matching log file for FILESTRAM file ‘%.*ls’.
Error: 5186, Severity: 16, Encountered an error (NT status code 0x%x) while attempting to start the Transactional File System Resource Manager ‘%.*ls’.
Error: 5188, Severity: 16, Encountered error (NT status code 0x%x) while attempting to perform redo for transactional file system resource manager ‘%.*ls’.
Error: 5189, Severity: 16, Encountered error (NT status code 0x%x) while attempting to perform undo for transactional file system resource manager ‘%.*ls’.
Error: 5190, Severity: 16, Encountered error (NT status code 0x%x) while attempting to checkpoint transactional file system resource manager ‘%.*ls’.
Error: 5191, Severity: 10, Local directory ‘%.*ls’ is used for tempdb in a clustered server. This directory must exist on each cluster node and SQL Server service has read/write permission on it.

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 *