SQL Server Errors or Failures Error: 1833 to Error: 1854
Error: 1833, Severity: 16,
File ‘%ls’ cannot be reused until after the next BACKUP LOG operation. If the database is participating in an availability group, a dropped file can be reused only after the truncation LSN of the primary availability replica has passed the drop LSN of the
Error: 1834, Severity: 16,
The file ‘%ls’ cannot be overwritten. It is being used by database ‘%.*ls’.
Error: 1835, Severity: 16,
Unable to create/attach any new database because the number of existing databases has reached the maximum number allowed: %d.
Error: 1836, Severity: 10,
Cannot create the default files because the name that was supplied is too long.
Error: 1837, Severity: 16,
The file name “%ls” is too long to create an alternate stream name.
Error: 1838, Severity: 10,
Offline database file(s) have been overwritten while being reverted to online state from a database snapshot. The reverted file might contain invalid pages. Please run database consistency checks to assess the data integrity.
Error: 1839, Severity: 16,
Could not create default data files because the name ‘%ls’ is a reserved device name.
Error: 1840, Severity: 16,
Could not create snapshot database because it is not supported on READONLY single-file user databases.
Error: 1841, Severity: 16,
CREATE DATABASE failed. CONTAINMENT clause cannot be used with the FOR ATTACH option.
Error: 1842, Severity: 16,
The file size, max size cannot be greater than 2147483647 in units of a page size. The file growth cannot be greater than 2147483647 in units of both page size and percentage.
Error: 1843, Severity: 10,
Reverting database ‘%ls’ to the point in time of database snapshot ‘%ls’ with split point LSN %.*ls (0x%ls). This is an informational message only. No user action is required.
Error: 1844, Severity: 16,
%ls is not supported on %ls.
Error: 1845, Severity: 16,
Cannot find SQL Volume Shadow Copy Service (VSS) Writer in writer metadata document provided by VSS while creating auto-recovered VSS snapshot for online DBCC check.
Error: 1846, Severity: 16,
Cannot find SQL Volume Shadow Copy (VSS) Writer component for database ‘%ls’ while creating auto-recovered VSS snapshot for online DBCC check.
Error: 1847, Severity: 16,
The current version of the operating system doesn’t support auto-recovered Volume Shadow Copy (VSS) snapshots.
Error: 1848, Severity: 16,
Volume Shadow Copy Service (VSS) failed to create an auto-recovered snapshot of database ‘%ls’ for online DBCC check.
Error: 1851, Severity: 16,
File name ‘%.*ls’ as relative path is too long after prefixed with default path ‘%ls’.
Error: 1852, Severity: 21,
Error occured when shrinking the physical file. Please check ERRORLOG for more detail.
Error: 1853, Severity: 16,
The logical database file ‘%.*ls’ cannot be found. Specify the full path for the file.
Error: 1854, Severity: 16,
The original file name ‘%.*ls’ for logical database file ‘%.*ls’ is too long to be combined with the full path to the new primary data file location.
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.
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.