After receiving the following event log message (see below) a DBCC was run on the DB listed however the Query return (see below) states that the ‘tempdb out of space or a system table is inconsistent.’ Event Log message: Application Log Event: 16 Dec 2010 02:12:29 AM Computer: [ESM-APP] Monitor: [Event Log Monitor] Description: * Event Time: 16 Dec 2010 02:06:34 AM * Source: MSSQL$MICROSOFT##SSEE * Event Log: Application * Type: Error Event * Event ID: 824 * SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x44a75f1c; actual: 0x2411382a). It occurred during a read of page (1:28776) in database ID 21 at offset 0x0000000e0d0000 in file 'C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\WSS_Content_118e5acc9f9d487cafcd24a9780049ba.mdf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online. * Event Time: 16 Dec 2010 02:06:34 AM * Source: Windows SharePoint Services 3 * Event Log: Application * Type: Error Event * Event ID: 6398 * The Execute method of job definition Microsoft.SharePoint.Administration.SPRecycleBinCleanupJobDefinition (ID 37583bce-2258-42a6-87f4-718952fe2337) threw an exception. More information is included below. Cannot complete this action. Please try again. Query return message: Msg 8967, Level 16, State 216, Line 1 An internal error occurred in DBCC that prevented further processing. Contact Customer Support Services. DBCC results for 'WSS_Content_118e5acc9f9d487cafcd24a9780049ba'. Msg 8921, Level 16, State 1, Line 1 Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors. CHECKDB found 0 allocation errors and 0 consistency errors in database 'WSS_Content_118e5acc9f9d487cafcd24a9780049ba'. File WSS_Content_118e5acc9f9d487cafcd24a9780049ba.mdf is 1.29GB. The server has plenty of disk space. C: has 7GB free and D: has 13GB free. What does this mean? Could it mean the SharePoint Services DB is limited in growth space and that the limit of DB space has been reached? How can one remove old data from this kind of database? If data needs to be removed what data is it in the SharePoint site? -DM Small Biz IT Manager

Hi, The 824 error indicates that a logical consistency error was detected during a read. A logical consistency error is a clear indication of actual damage and frequently indicates data corruption caused by a faulty I/O subsystem component. If the problem is not hardware-related and a known clean backup is available, restore the database from the backup. For more information, please refer to: http://technet.microsoft.com/en-us/library/aa337274(SQL.90).aspx For Event ID 6398 error, it is likely to occur for the SharePoint Timer service, the issue has fixed by KB946517: http://support.microsoft.com/?id=946517 Hope the information can help. Xue-Mei Chang TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com Xue-Mei Chang

You have DB corruption going on. Hopefully you have a backup before this corruption happend. This is your DB file with inconsistencies: \WSS_Content_118e5acc9f9d487cafcd24a9780049ba.mdf' Given that you are running a SharePoint Standalone installation with Windows Internal Database (SSEE), you need to open it with \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query in Management Studio to run DBCC CheckDB. Living the SharePoint dream...

You have DB corruption going on. Hopefully you have a backup before this corruption happend. This is your DB file with inconsistencies: \WSS_Content_118e5acc9f9d487cafcd24a9780049ba.mdf' Given that you are running a SharePoint Standalone installation with Windows Internal Database (SSEE), you need to open it with \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query in Management Studio to run DBCC CheckDB. Living the SharePoint dream...