Welcome, Guest to: Public MPWiki ▼
Welcome to Management Pack Wiki! Your documentation pro for SCOM Management Packs
0 comment(s) Post a comment
  • Management Pack:  SQL Server
  • MP Version: for SQL Server 2008
  • Released:  10/15/2015
  • Publisher:  Microsoft

Cannot retrieve row from page by RID because the slotid is not valid : DEPRECATED Rule

  • ID:  Microsoft.SQLServer.2008.Cannot_retrieve_row_from_page_by_RID_because_the_slotid_is_not_valid_1_5_Rule
  • Description:   
  • Target:  SQL Server 2008 DB Engine
  • Enabled:  No

Overridable Parameters

Parameter Name Default Value Description Override
Priority 1  
Severity 2  

Run As Profiles

SQL Server Default Action Account

Alert Details

Message Priority Severity
Cannot retrieve row from page by RID because the slotid is not valid Medium Critical

Rule Knowledgebase


This error occurs when an object to which this row belongs is in error. The problem was detected during the reading of a specific row from that logical page. This error can occur as a result of:

Hardware problems, especially problems with the hard drive, controller or hardware write caching.

Other errors in the database.

This rule does not contain any causes.

Execute DBCC CHECKDB to determine the full extent of the error. Also check the error log for other errors such as 25xx messages, which often accompany this error.

If DBCC CHECKDB issues other error messages, resolving those messages first may take care of this error. Execute DBCC CHECKDB with the REPAIR_REBUILD clause to repair the damage.

Important: If executing DBCC CHECKDB with the REPAIR_REBUILD clause does not correct the index problem or if you are unsure what effect DBCC CHECKDB with the REPAIR_REBUILD clause has on your data, contact your primary support provider.

If executing DBCC CHECKDB with the REPAIR_REBUILD clause does not resolve all table error problems, determine which table is affected by examining the page in the error message. If the page is associated with an index, you may be able to resolve the problem by dropping and then re-creating the index. If the page is a data page and a clean current backup is available, restore the database from the backup.

If no backup is available, select the table into another table or bulk copy data out of the table, drop the table, re-create it, and then select data back into the table.

If you suspect a hardware problem, run hardware diagnostics and correct any problems. You might find it beneficial to perform a completely new setup, including reformatting the disk drives and reinstalling the operating system. Also examine the Microsoft® Windows NT® application log to see if the error occurred as the result of hardware failure.

Finally, be sure that your system does not have write caching enabled on the disk controller. If you suspect this to be the problem, contact your hardware vendor.

External References
This rule does not contain any external references.

See Also for SQL Server Management Pack

Downloads for SQL Server Management Pack

Post a comment
Comments to other elements of this Management Pack:
Article Message Posted By
We are providing a platform for those who want to join this profession.
writing jobs
shahid.afraid111@gmail.com at 10/29/2014 11:48:42 AM
Is Management Pack inventory available for SQL Server 2012 MP version
milmanfm@gmail.com at 9/23/2014 11:36:42 AM
Database cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQ
Due to over storage of SQL database files the memory allocation refuses and creates some errors which are responsible for SQL database inaccessibility. You must go through this to learn more about resolving solutions:- http://www.sqlrecoverysoftware.net/blog/sql-error-926-and-945.html
enriquemallon@gmail.com at 6/28/2014 10:10:17 AM
Database consistency errors found
I recommend you to read this article which serve you how get rid of this consistency error:- http://www.sqlrecoverysoftware.net/blog/fix-database-consistency-errors.html
elliswhite43@gmail.com at 5/10/2014 11:06:07 AM
Overview shantal@list.ru at 7/2/2013 11:57:28 AM
Where can i get the Management pack Inventory for SQL 2008
vivakhangloo@gmail.com at 4/4/2013 8:32:16 AM
According to the Pinpoint catalog, the SQL MP was updated to include SQL 2012 monitoring as of 4/2/2012. Do you have an ETA for when this MPwiki entry will be updated? Keep up the great work; thanks!
bdady@denaliai.com at 5/30/2012 2:47:22 PM
DB File Space
You should keep in mind that file-level monitoring works rather good now but in case of extremely loaded server (e.g. which works all the time about 99% of CPU) or you have really huge number of DBs and files (e.g. 500 databases consist of 1000-2000 files) - you should think about Database-level space monitoring.
legolasishe@mail.ru at 3/21/2012 1:39:09 PM
Overview shantal@list.ru at 11/4/2011 3:29:24 PM
Overview igrudina@viacode.com at 10/26/2011 4:12:53 PM