• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1698
  • Last Modified:

SBSMONITORING event id 824 SBS 2008 SQL 2005 Express

Running SBS 2008, receiving a ton of error messages in the event log.


SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:120763; actual 0:332280272). It occurred during a read of page (1:120763) in database ID 5 at offset 0x0000003af76000 in file 'C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\SBSMonitoring.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.

So, ran DBCC CHECKDB, got message below:

Msg 8939, Level 16, State 98, Line 2
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID -2676586395008892928 (type Unknown), page (56026:-623191302). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 96471049 and -4.
Msg 8921, Level 16, State 1, Line 2
Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
Msg 8998, Level 16, State 2, Line 2
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:16176) to (1:24263). See other errors for cause.
Msg 8998, Level 16, State 2, Line 2
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:32352) to (1:40439). See other errors for cause.
Msg 8998, Level 16, State 2, Line 2
Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 5 pages from (1:80880) to (1:88967). See other errors for cause.
Msg 8909, Level 16, State 1, Line 2
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 293270838050816 (type Unknown), page ID (1:32352) contains an incorrect page ID in its page header. The PageId in the page header = (0:13).
Msg 8909, Level 16, State 1, Line 2
Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 3472386858932109312 (type Unknown), page ID (1:80880) contains an incorrect page ID in its page header. The PageId in the page header = (15717:1970037110).
CHECKDB found 6 allocation errors and 0 consistency errors not associated with any single object.
CHECKDB found 6 allocation errors and 0 consistency errors in database 'SBSMonitoring'.
Msg 824, Level 24, State 2, Line 2
SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0xb752374b; actual: 0x27aa063e). It occurred during a read of page (1:130728) in database ID 5 at offset 0x0000003fd50000 in file 'C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\SBSMonitoring.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.

As a matter of fact, everything I try, results in the error message above:  
DBCC CheckDB ('SBSMONITORING' , REPAIR_ALLOW_ DATA_LOSS)
or
alter database sbsmonitoring set SINGLE_USER
 DBCC CHECKDB (sbsmonitoring, repair_rebuild)
 alter database sbsmonitoring set MULTI_USER
or a variety of other troubleshooting steps that I have taken.

I am not a DBA, but I am at a total loss on what to do now.

Any help?

What we believe happened is we had a consultant working over the weekend and all of a sudden the whole network kind of went down.  Exchange stopped working correctly, Sharepoint stopped working, it was just a mess.  Somehow, the IP address of the server had been changed.  So, we changed it back and everything started working again.  It was right around there that we started receiveing the 824 messages.  
0
steele2007
Asked:
steele2007
1 Solution
 
Aaron ShiloChief Database ArchitectCommented:
hi
 It looks like You have corruption on PFS tables and that cannot be repaired.
 
CHECKDB cannot be used to repair this problem.
 
You can confirm that with Microsoft Support.
 
do you have a backup available, because restoring from backup is the only solution on this case.
 
Hope this helps.  

this help my coligue once : http://www.mssqldatabaserepair.org/
 
 
0

Featured Post

Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now