SharePoint 2007 Std SP2 - 32 bit
SQL 2005 SP3 - 32 bit
Issue found on the 28th November.
Navigated to a document library and found the error message:
<!-- #RENDER FAILED -->
Windows Error shows 5586
Tried the following:
- Modified existing Views (Failed)
- Create new Views (Failed)
- Created same webpart on same page (Failed - Render Failed)
- Created a new page with added library web part (Failed - Render Failed)
Had a reboot of all servers on the following weekend and when SharePoint booted up. It showed the following error on the home page:
Teh "CalendarListView" Web Part appears to be causing a problem. Warning: Fatal error 824 occurred at Dec 5 2011 8:12AM. Note the error and time, and contact your system administrator.
Removed the web part, which allowed users to access the homepage. If we re-add the webpart, it showed the Rendered Failed and accessing the Calendar list directly shows the same error message.
In the content database, the results from dbcc checktable (alluserdata) shows the following:
Results from dbcc checktable (alluserdata)
The results are:
DBCC results for 'AllUserData'.
Msg 8928, Level 16, State 1, Line 1
Object ID 1365579903, index ID 1, partition ID 72057597721772032, alloc unit ID 72057597818306560 (type In-row data): Page (1:113913) could not be processed. See other errors for details.
Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1365579903, index ID 1, partition ID 72057597721772032, alloc unit ID 72057597818306560 (type In-row data), page (1:113913). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -4.
Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1365579903, index ID 1, partition ID 72057597721772032, alloc unit ID 72057597818306560 (type In-row data). Page (1:113913) was not seen in the scan although its parent (1:623388) and previous (1:113912) refer to it. Check any previous errors.
Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1365579903, index ID 1, partition ID 72057597721772032, alloc unit ID 72057597818306560 (type In-row data). Page (1:113914) is missing a reference from previous page (1:113913). Possible chain linkage problem.
There are 18869 rows in 2153 pages for object "AllUserData".
CHECKTABLE found 0 allocation errors and 4 consistency errors in table 'AllUserData' (object ID 1365579903
Ran a checkdisk:
Event Type: Error
Event Source: MSSQL$EIDE
Event Category: (2)
Event ID: 824
Time: 12:26:16 AM
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0xe8f1950b; actual: 0xb7c2b1c9). It occurred during a read of page (1:106841) in database ID 31 at offset 0x000000342b2000 in file 'E:\SQLServer\Data\WSS_Content_SharePoint.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.
Can you please let me know what we should do for this scenario? I know that repairing the database directly is not supported.