SQL Server Errors or Failures from Error: 8955 to Error: 8974

SQLServerF1

 

Error: 8955, Severity: 16, Data row (%d:%d:%d) identified by (%ls) with index values ‘%ls’.
Error: 8956, Severity: 16, Index row (%d:%d:%d) with values (%ls) pointing to the data row identified by (%ls).
Error: 8957, Severity: 10, %lsDBCC %ls (%ls%ls%ls)%ls executed by %ls found %d errors and repaired %d errors. Elapsed time: %d hours %d minutes %d seconds. %.*ls
Error: 8958, Severity: 10, %ls is the minimum repair level for the errors found by DBCC %ls (%ls%ls%ls).
Error: 8959, Severity: 16, Table error: IAM page %S_PGID for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) is linked in the IAM chain for object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) by page %S_PGID.

Error: 8960, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). Page %S_PGID, slot %d, column %d is not a valid complex column.
Error: 8961, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d does not match its reference from page %S_PGID, slot %d.
Error: 8962, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d has incorrect node type %d.
Error: 8963, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d has type %d. It cannot be placed on a page of type %d.

Error: 8964, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d is not referenced.
Error: 8965, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d is referenced by page %S_PGID, slot %d, but was not seen in the scan.
Error: 8966, Severity: 22, Unable to read and latch page %S_PGID with latch type %ls. %ls failed.
Error: 8967, Severity: 16, An internal error occurred in DBCC that prevented further processing. Contact Customer Support Services.
Error: 8968, Severity: 16, Table error: %ls page %S_PGID (object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls)) is out of the range of this database.
Error: 8969, Severity: 16, Table error: IAM chain linkage error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The next page for IAM page %S_PGID is %S_PGID, but the previous link for page %S_PGID is %S_PGID.
Error: 8970, Severity: 16, Row error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page ID %S_PGID, row ID %d. Column ‘%.*ls’ was created NOT NULL, but is NULL in the row.
Error: 8971, Severity: 16, Forwarded row mismatch: Object ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) page %S_PGID, slot %d points to forwarded row page %S_PGID, slot %d; the forwarded row points back to page %S_PGID, slot %d
Error: 8972, Severity: 16, Forwarded row referenced by more than one row. Object ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID, slot %d incorrectly points to the forwarded row page %S_PGID, slot %d, which correctly refers back to page %S_PGID, slot %d.
Error: 8973, Severity: 16, CHECKTABLE object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) processing encountered page %S_PGID, slot %d twice.
Error: 8974, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls). The off-row data node at page %S_PGID, slot %d, text ID %I64d is pointed to by page %S_PGID, slot %d and by page %S_PGID, slot %d.

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: 7001 to Error: 7119

SQLServerF1

 

Error: 7001, Severity: 16, OPENXML flags parameter must be of data type int.
Error: 7002, Severity: 16, OPENXML XPath must be of a string data type, such as nvarchar.
Error: 7003, Severity: 16, Only one OPENXML column can be of type %ls.
Error: 7004, Severity: 16, OPENXML does not support retrieving schema from remote tables, as in ‘%.*ls’.
Error: 7005, Severity: 16, OPENXML requires a metaproperty namespace to be declared if ‘mp’ is used for another namespace in sp_xml_preparedocument.
Error: 7006, Severity: 16, OPENXML encountered a problem identifying the metaproperty namespace prefix. Consider removing the namespace parameter from the corresponding sp_xml_preparedocument statement.

Error: 7007, Severity: 16, OPENXML encountered unknown metaproperty ‘%.*ls’.
Error: 7008, Severity: 16, The OPENXML EDGETABLE is incompatible with the XMLTEXT OVERFLOW flag.
Error: 7009, Severity: 16, OPENXML allows only one metaproperty namespace prefix declaration in sp_xml_preparedocument.
Error: 7101, Severity: 16, You need an active user transaction in order to use text pointers for a table with the option “text in row” set to ON.
Error: 7102, Severity: 20, Internal Error: Text manager cannot continue with current statement. Run DBCC CHECKTABLE.
Error: 7104, Severity: 16, Offset or size of data type is not valid. Data type must be of type int or smallint.
Error: 7105, Severity: 22, The Database ID %d, Page %S_PGID, slot %d for LOB data type node does not exist. This is usually caused by transactions that can read uncommitted data on a data page. Run DBCC CHECKTABLE.

Error: 7106, Severity: 16, Internal error: An attempt was made to update a LOB data type using a read-only text pointer.
Error: 7107, Severity: 16, You can have only 1,024 in-row text pointers in one transaction
Error: 7108, Severity: 22, Database ID %d, page %S_PGID, slot %d, link number %d is invalid. Run DBCC CHECKTABLE.
Error: 7116, Severity: 16, Offset %d is not in the range of available LOB data.
Error: 7117, Severity: 16, Error reading large object (LOB) data from the tabular data stream (TDS).
Error: 7118, Severity: 16, Only complete replacement is supported when assigning a large object (LOB) to itself.
Error: 7119, Severity: 16, Attempting to grow LOB beyond maximum allowed size of %I64d bytes.

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 from Error: 5215 to Error: 5234

SQLServerF1

 

Error: 5215, Severity: 10, %.*ls: Page %d:%d could not be moved because the partition to which it belonged was dropped.
Error: 5216, Severity: 10, %.*ls: Heap page %d:%d could not be moved because the table to which it belonged was dropped.
Error: 5217, Severity: 10, %.*ls: Page %d:%d could not be moved because it is an empty non-leaf level index page.
Error: 5218, Severity: 10, %.*ls: Heap page %d:%d could not be moved because the table name could not be found.
Error: 5219, Severity: 10, %.*ls: Heap page %d:%d could not be moved.

Error: 5220, Severity: 10, %.*ls: Index Allocation Map (IAM) page %d:%d could not be moved.
Error: 5221, Severity: 10, %.*ls: Index Allocation Map (IAM) page %d:%d from a dropped allocation unit could not be moved.
Error: 5222, Severity: 10, %.*ls: Page %d:%d from a dropped allocation unit could not be deallocated.
Error: 5223, Severity: 10, %.*ls: Empty page %d:%d could not be deallocated.
Error: 5224, Severity: 10, %.*ls: Empty large object page %d:%d could not be deallocated.
Error: 5225, Severity: 10, %.*ls: Not all ghost records on the large object page %d:%d could be removed. If there are active queries on readable secondary replicas check the current ghost cleanup boundary.
Error: 5226, Severity: 10, %.*ls: Page %d:%d (type UNLINKED_REORG_PAGE) could not be deallocated.

Error: 5227, Severity: 10, %.*ls: Page %d:%d (type BULK_OPERATION_PAGE) could not be deallocated.
Error: 5228, Severity: 16, Table error: object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID, row %d. DBCC detected incomplete cleanup from an online index build operation. (The anti-matter column value is %d.)
Error: 5229, Severity: 16, Table error: Object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) contains an anti-matter column, but is not a nonclustered index.
Error: 5230, Severity: 10, The check statement was aborted. DBCC CHECKCATALOG cannot be run on TEMPDB.
Error: 5231, Severity: 10, Object ID %ld (object ‘%.*ls’): A deadlock occurred while trying to lock this object for checking. This object has been skipped and will not be processed.
Error: 5232, Severity: 10, DBCC CHECKDB will not check SQL Server catalog or Service Broker consistency because a database snapshot could not be created or because WITH TABLOCK was specified.
Error: 5233, Severity: 16, Table error: alloc unit ID %I64d, page %S_PGID. The test (%.*ls) failed. The values are %ld and %ld.
Error: 5234, Severity: 10, DBCC SHRINKDATABASE: File ID %d of database ID %d was skipped because trying to adjust the space allocation for the file was failed.

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: 2524 to Error: 2544

SQLServerF1

 

Error: 2524, Severity: 16, Cannot process object ID %ld (object “%.*ls”) because it is a Service Broker queue. Try the operation again with the object ID of the corresponding internal table for the queue, found in sys.internal_tables.,
Error: 2525, Severity: 16, Database file %.*ls is offline.,
Error: 2526, Severity: 16, Incorrect DBCC statement. Check the documentation for the correct DBCC syntax and options.,
Error: 2527, Severity: 16, Unable to process index %.*ls of table %.*ls because filegroup %.*ls is offline.,

Error: 2528, Severity: 10, DBCC execution completed. If DBCC printed error messages, contact your system administrator.,
Error: 2529, Severity: 16, Filegroup %.*ls is offline.,
Error: 2530, Severity: 16, The index “%.*ls” on table “%.*ls” is disabled.,
Error: 2531, Severity: 16, Table error: object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) B-tree level mismatch, page %S_PGID. Level %d does not match level %d from the previous %S_PGID.,
Error: 2532, Severity: 16, One or more WITH options specified are not valid for this command.,
Error: 2533, Severity: 16, Table error: page %S_PGID allocated to object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls) was not seen. The page may be invalid or may have an incorrect alloc unit ID in its header.,

Error: 2534, Severity: 16, Table error: page %S_PGID, whose header indicates that it is allocated to object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), is allocated by another object.,
Error: 2536, Severity: 10, DBCC results for ‘%.*ls’.,
Error: 2537, Severity: 16, Table error: object ID %d, index ID %d, partition ID %I64d, alloc unit ID %I64d (type %.*ls), page %S_PGID, row %d. The record check (%.*ls) failed. The values are %I64d and %I64d.,
Error: 2538, Severity: 10, File %d. The number of extents = %I64d, used pages = %I64d, and reserved pages = %I64d.,
Error: 2539, Severity: 10, The total number of extents = %I64d, used pages = %I64d, and reserved pages = %I64d in this database.,
Error: 2540, Severity: 10, The system cannot self repair this error.,
Error: 2541, Severity: 10, DBCC UPDATEUSAGE: Usage counts updated for table ‘%.*ls’ (index ‘%.*ls’, partition %ld):,
Error: 2542, Severity: 10, DATA pages %.*ls: changed from (%I64d) to (%I64d) pages.,
Error: 2543, Severity: 10, USED pages %.*ls: changed from (%I64d) to (%I64d) pages.,
Error: 2544, Severity: 10, RSVD pages %.*ls: changed from (%I64d) to (%I64d) pages.,

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.