SQL Server Errors or Failures from Error: 8975 to Error: 8994

SQLServerF1

 

Error: 8975, Severity: 10, DBCC cross-rowset check failed for object ‘%.*ls’ (object ID %d) due to internal query error %d, severity %d, state %d. Refer to Books Online for more information on this error.
Error: 8976, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Page %S_PGID was not seen in the scan although its parent %S_PGID and previous %S_PGID refer to it. Check any previous errors.
Error: 8977, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Parent node for page %S_PGID was not encountered.

Error: 8978, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Page %S_PGID is missing a reference from previous page %S_PGID. Possible chain linkage problem.
Error: 8979, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Page %S_PGID is missing references from parent (unknown) and previous (page %S_PGID) nodes. Possible bad root entry in system catalog.
Error: 8980, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Index node page %S_PGID, slot %d refers to child page %S_PGID and previous child %S_PGID, but they were not encountered.
Error: 8981, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The next pointer of %S_PGID refers to page %S_PGID. Neither %S_PGID nor its parent were encountered. Possible bad chain linkage.

Error: 8982, Severity: 16, Table error: Cross object linkage. Page %S_PGID->next in object ID %d, index ID %d, partition ID %I64d, AU ID %I64d (type %.*ls) refers to page %S_PGID in object ID %d, index ID %d, partition ID %I64d, AU ID %I64d (type %.*ls) but is not in the same index
Error: 8983, Severity: 10, File %d. Extents %I64d, used pages %I64d, reserved pages %I64d, mixed extents %I64d, mixed pages %I64d.
Error: 8984, Severity: 16, Table error: object ID %d, index ID %d, partition ID %I64d. A row should be on partition number %d but was found in partition number %d. Possible extra or invalid keys for:
Error: 8985, Severity: 16, Could not locate file ‘%.*ls’ for database ‘%.*ls’ in sys.database_files. The file either does not exist, or was dropped.
Error: 8986, Severity: 16, Too many errors found (%d) for object ID %d. To see all error messages rerun the statement using “WITH ALL_ERRORMSGS”.
Error: 8987, Severity: 16, No help available for DBCC statement ‘%.*ls’.
Error: 8988, Severity: 16, Row (%d:%d:%d) identified by (%ls).
Error: 8989, Severity: 10, %.*ls found %d allocation errors and %d consistency errors in database ‘%ls’.
Error: 8990, Severity: 10, %.*ls found %d allocation errors and %d consistency errors in table ‘%ls’ (object ID %d).
Error: 8991, Severity: 16, 0x%p to 0x%p is not a valid address range.
Error: 8992, Severity: 16, Check Catalog Msg %d, State %d: %.*ls
Error: 8993, Severity: 16, Object ID %d, forwarding row page %S_PGID, slot %d points to page %S_PGID, slot %d. Did not encounter forwarded row. Possible allocation error.
Error: 8994, Severity: 16, Object ID %d, forwarded row page %S_PGID, slot %d should be pointed to by forwarding row page %S_PGID, slot %d. Did not encounter forwarding row. Possible allocation error.

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.

 

SQL Server Errors or Failures from Error: 8935 to Error: 8954

SQLServerF1

 

Error: 8935, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The previous link %S_PGID on page %S_PGID does not match the previous page %S_PGID that the parent %S_PGID, slot %d expects for this page.
Error: 8936, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). B-tree chain linkage mismatch. %S_PGID->next = %S_PGID, but %S_PGID->Prev = %S_PGID.
Error: 8937, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). B-tree page %S_PGID has two parent nodes %S_PGID, slot %d and %S_PGID, slot %d.

Error: 8938, Severity: 16, Table error: Page %S_PGID, Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Unexpected page type %d.
Error: 8939, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. Test (%.*ls) failed. Values are %ld and %ld.
Error: 8940, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. Test (%.*ls) failed. Address 0x%x is not aligned.
Error: 8941, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. Test (%.*ls) failed. Slot %d, offset 0x%x is invalid.
Error: 8942, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. Test (%.*ls) failed. Slot %d, offset 0x%x overlaps with the prior row.

Error: 8943, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. Test (%.*ls) failed. Slot %d, row extends into free space at 0x%x.
Error: 8944, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page (%d:%d), row %d. Test (%.*ls) failed. Values are %ld and %ld.
Error: 8945, Severity: 16, Table error: Object ID %d, index ID %d will be rebuilt.
Error: 8946, Severity: 16, Table error: Allocation page %S_PGID has invalid %ls page header values. Type is %d. Check type, alloc unit ID and page ID on the page.
Error: 8947, Severity: 16, Table error: Multiple IAM pages for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) contain allocations for the same interval. IAM pages %S_PGID and %S_PGID.
Error: 8948, Severity: 16, Database error: Page %S_PGID is marked with the wrong type in PFS page %S_PGID. PFS status 0x%x expected 0x%x.
Error: 8949, Severity: 10, %.*ls fixed %d allocation errors and %d consistency errors in table ‘%ls’ (object ID %d).
Error: 8950, Severity: 16, %.*ls fixed %d allocation errors and %d consistency errors not associated with any single object.
Error: 8951, Severity: 16, Table error: table ‘%ls’ (ID %d). Data row does not have a matching index row in the index ‘%ls’ (ID %d). Possible missing or invalid keys for the index row matching:
Error: 8952, Severity: 16, Table error: table ‘%ls’ (ID %d). Index row in index ‘%ls’ (ID %d) does not match any data row. Possible extra or invalid keys for:
Error: 8953, Severity: 10, Repair: Deleted off-row data column with ID %I64d, for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) on page %S_PGID, slot %d.
Error: 8954, Severity: 10, %.*ls found %d allocation errors and %d consistency errors not associated with any single object.
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.

 

SQL Server Errors or Failures from Error: 7948 to Error: 7969

SQLServerF1

 

Error: 7948, Severity: 10, – Avg. Pages per Extent……………………: %3.1f
Error: 7949, Severity: 10, – Scan Density [Best Count:Actual Count]…….: %4.2f%ls [%I64d:%I64d]
Error: 7950, Severity: 10, – Logical Scan Fragmentation ………………: %4.2f%ls
Error: 7951, Severity: 10, Warning: Could not complete filestream consistency checks due to an operating system error. Any consistency errors found in the filestream subsystem will be silenced. Please refer to other errors for more information. This condition is likely transien
Error: 7952, Severity: 10, – Extent Scan Fragmentation ……………….: %4.2f%ls

Error: 7953, Severity: 10, – Avg. Bytes Free per Page…………………: %3.1f
Error: 7954, Severity: 10, – Avg. Page Density (full)…………………: %4.2f%ls
Error: 7955, Severity: 16, Invalid SPID %d specified.
Error: 7956, Severity: 16, Table error: The FILESTREAM file “%.*ls” for column ID %d was found in column directory ID %.*ls of container ID %d but should be in container ID %d in object ID %d, index ID %d, partition ID %I64d, page ID %S_PGID, slot ID %d.
Error: 7957, Severity: 10, Cannot display the specified SPID’s buffer; in transition.
Error: 7958, Severity: 16, The specified SPID does not process input/output data streams.
Error: 7960, Severity: 16, An invalid server process identifier (SPID) %d or batch ID %d was specified.

Error: 7961, Severity: 16, Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) , page ID %S_PGID, row ID %d. Column ‘%.*ls’ is a var column with a NULL value and non-zero data length
Error: 7962, Severity: 16, Invalid BATCHID %d specified.
Error: 7963, Severity: 16, Database error: The file “%.*ls” is not a valid FILESTREAM LOG file in container ID %d.
Error: 7964, Severity: 10, Repair: Deleted FILESTREAM file “%.*ls” for column ID %d, for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) on page %S_PGID, slot %d.
Error: 7965, Severity: 16, Table error: Could not check object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) due to invalid allocation (IAM) page(s).
Error: 7966, Severity: 10, Warning: NO_INDEX option of %ls being used. Checks on non-system indexes will be skipped.
Error: 7968, Severity: 10, Transaction information for database ‘%.*ls’.
Error: 7969, Severity: 16, No active open transactions.

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.

 

SQL Server Errors or Failures from Error: 5255 to Error: 5274

SQLServerF1

 

Error: 5255, Severity: 10, %.*ls: Page %d:%d could not be moved because it is a sort page.
Error: 5256, Severity: 16, Table error: alloc unit ID %I64d, page %S_PGID contains an incorrect page ID in its page header. The PageId in the page header = %S_PGID.
Error: 5257, Severity: 10, %.*ls: File ID %d of database ID %d was skipped because the file size was changed in the middle of shrink operation.
Error: 5258, Severity: 10, %.*ls: Heap page %d:%d could not be moved because building computed column expression failed.
Error: 5259, Severity: 10, %.*ls: Heap page %d:%d could not be moved because populating computed column expression failed.

Error: 5260, Severity: 16, Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls): At least one record on page %S_PGID contains versioning information, but the VERSION_INFO bit in the page header is not set.
Error: 5261, Severity: 10, %.*ls: Page %d:%d could not be moved because it has not been formatted.
Error: 5262, Severity: 16, Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID, row %d: Row contains a NULL versioning timestamp, but its version chain pointer is not NULL. Version chain points to page %S_PGID, slot %d.
Error: 5263, Severity: 10, Found incorrect count(s) for table ‘%.*ls’, index ‘%.*ls’, partition %ld:
Error: 5264, Severity: 10, DATA pages %.*ls: From system table – %I64d pages; Actual – %I64d pages.

Error: 5265, Severity: 10, USED pages %.*ls: From system table – %I64d pages; Actual – %I64d pages.
Error: 5266, Severity: 10, RSVD pages %.*ls: From system table – %I64d pages; Actual – %I64d pages.
Error: 5267, Severity: 10, ROWS count: From system table – %I64d rows; Actual – %I64d rows.
Error: 5268, Severity: 10, DBCC %.*ls is performing an exhaustive search of %d indexes for possible inconsistencies. This is an informational message only. No user action is required.
Error: 5269, Severity: 16, Check terminated. The transient database snapshot for database ‘%.*ls’ (database ID %d) has been marked suspect due to an IO operation failure. Refer to the SQL Server error log for details.
Error: 5270, Severity: 10, %.*ls: Page %d:%d could not be moved because it is an unmovable page in a critical system table.
Error: 5271, Severity: 10, DBCC %ls could not output results for this command due to an internal failure. Review other errors for details.
Error: 5272, Severity: 10, %.*ls: Index Allocation Map (IAM) page %d:%d could not be moved because the underlying object could not be accessed exclusively.
Error: 5273, Severity: 10, %.*ls: Page %d:%d could not be moved because it belonged to an index/heap that was/is in build online.
Error: 5274, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID. %S_MSG is invalid for compressed page; the following internal test failed: %.*ls. Values are %ld and %ld.

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.

 

SQL Server Errors or Failures Error: 2567 to Error: 2590

SQLServerF1

 

Error: 2567, Severity: 14, DBCC INDEXDEFRAG cannot be used on system table indexes,
Error: 2568, Severity: 16, Page %S_PGID is out of range for this database or is in a log file.,
Error: 2570, Severity: 16, Page %S_PGID, slot %d in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type “%.*ls”). Column “%.*ls” value is out of range for data type “%.*ls”. Update column to a legal value.,
Error: 2571, Severity: 14, User ‘%.*ls’ does not have permission to run DBCC %.*ls.,

Error: 2572, Severity: 16, DBCC cannot free DLL ‘%.*ls’. The DLL is in use.,
Error: 2573, Severity: 16, Could not find table or object ID %.*ls. Check system catalog.,
Error: 2574, Severity: 16, Table error: Page %S_PGID is empty in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). This is not permitted at level %d of the B-tree.,
Error: 2575, Severity: 16, The Index Allocation Map (IAM) page %S_PGID is pointed to by the next pointer of IAM page %S_PGID in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), but it was not detected in the scan.,
Error: 2576, Severity: 16, The Index Allocation Map (IAM) page %S_PGID is pointed to by the previous pointer of IAM page %S_PGID in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), but it was not detected in the scan.,

Error: 2577, Severity: 16, Chain sequence numbers are out of order in the Index Allocation Map (IAM) chain for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Page %S_PGID with sequence number %d points to page %S_PGID with sequence number %d.,
Error: 2579, Severity: 16, Table error: Extent %S_PGID in object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) is beyond the range of this database.,
Error: 2580, Severity: 16, Table ‘%.*ls’ is either a system or temporary table. DBCC CLEANTABLE cannot be applied to a system or temporary table.,
Error: 2581, Severity: 10, DBCC cannot free the DLL “%.*ls”. The DLL is not loaded.,
Error: 2583, Severity: 16, An incorrect number of parameters was given to the DBCC statement.,
Error: 2585, Severity: 16, Cannot find partition number %ld for table “%.*ls”.,
Error: 2586, Severity: 16, Cannot find partition number %ld for index “%.*ls”, table “%.*ls”.,
Error: 2587, Severity: 16, The invalid partition number %ld was specified.,
Error: 2588, Severity: 16, Cannot find partition number %ld for index ID %d, object ID %d.,
Error: 2589, Severity: 16, Repair could not fix all errors on the first attempt.,
Error: 2590, Severity: 10, User “%.*ls” is modifying bytes %d to %d of page %S_PGID in 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.

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

 

SQL Server Errors or Failures Error: 2503 to Error: 2523

SQLServerF1

 

Error: 2503, Severity: 10, Successfully deleted the physical file ‘%ls’.,
Error: 2504, Severity: 16, Could not delete the physical file ‘%ls’. The DeleteFile system function returned error %ls.,
Error: 2505, Severity: 16, The device ‘%.*ls’ does not exist. Use sys.backup_devices to show available devices.,
Error: 2506, Severity: 16, Could not find a table or object name ‘%.*ls’ in database ‘%.*ls’.,
Error: 2507, Severity: 16, The CONCAT_NULL_YIELDS_NULL option must be set to ON to run DBCC CHECKCONSTRAINTS.,
Error: 2508, Severity: 16, The %.*ls count for object “%.*ls”, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) is incorrect. Run DBCC UPDATEUSAGE.,

Error: 2509, Severity: 16, DBCC CHECKCONSTRAINTS failed due to an internal query error. Please run DBCC CHECKDATABASE to ensure your data consistency.,
Error: 2510, Severity: 16, DBCC %ls error: %ls.,
Error: 2511, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Keys out of order on page %S_PGID, slots %d and %d.,
Error: 2512, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Duplicate keys on page %S_PGID slot %d and page %S_PGID slot %d.,
Error: 2514, Severity: 16, A DBCC PAGE error has occurred: %ls.,
Error: 2515, Severity: 16, The page %S_PGID, object ID %d, index ID %d, partition ID %I64d, allocation unit ID %I64d (type %.*ls) has been modified, but is not marked as modified in the differential backup bitmap.,

Error: 2516, Severity: 16, Repair has invalidated the differential bitmap for database %.*ls. The differential backup chain is broken. You must perform a full database backup before you can perform a differential backup.,
Error: 2517, Severity: 16, Bulk-logging has been turned on for database %.*ls. To ensure that all data has been secured, run backup log operations again.,
Error: 2518, Severity: 10, Object ID %ld (object “%.*ls”): Computed columns and CLR types cannot be checked for this object because the common language runtime (CLR) is disabled.,
Error: 2519, Severity: 10, Computed columns and CLR types cannot be checked for object ID %ld (object “%.*ls”) because the internal expression evaluator could not be initialized.,
Error: 2520, Severity: 16, Could not find database ‘%.*ls’. The database either does not exist, or was dropped before a statement tried to use it. Verify if the database exists by querying the sys.databases catalog view.,
Error: 2521, Severity: 16, Could not find database ID %d. The database ID either does not exist, or the database was dropped before a statement tried to use it. Verify if the database ID exists by querying the sys.databases catalog view.,
Error: 2522, Severity: 16, Unable to process index %.*ls of table %.*ls because filegroup %.*ls is invalid.,
Error: 2523, Severity: 16, Filegroup %.*ls is invalid.,

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.