Skip to content

Archive for

Msg 8992, Level 16, State 1, Line 1

Error Message

DBCC checkdb is failing on user database and throwing errors like:-

Msg 8992, Level 16, State 1, Line 1

Check Catalog Msg 3851, State 1: An invalid row

(class=12,depid=0,depsubid=0) was found in the system table sys.syssingleobjrefs (class=12).

Msg 8992, Level 16, State 1, Line 1

Check Catalog Msg 3851, State 1: An invalid row

(class=13,depid=1,depsubid=0) was found in the system table sys.syssingleobjrefs (class=13).

Msg 8992, Level 16, State 1, Line 1

Check Catalog Msg 3851, State 1: An invalid row

(class=60,depid=1,depsubid=0) was found in the system table sys.syssingleobjrefs (class=60).

Msg 8992, Level 16, State 1, Line 1

Check Catalog Msg 3851, State 1: An invalid row

(class=26,depid=1,depsubid=0,indepid=3,indepsubid=0) was found in the system table sys.sysmultiobjrefs (class=26).

Msg 8992, Level 16, State 1, Line 1

Check Catalog Msg 3851, State 1: An invalid row

(class=13,depid=2,depsubid=0) was found in the system table sys.syssingleobjrefs (class=13).

Msg 8992, Level 16, State 1, Line 1

Check Catalog Msg 3851, State 1: An invalid row

(class=60,depid=2,depsubid=0) was found in the system table sys.syssingleobjrefs (class=60).

Msg 8992, Level 16, State 1, Line 1

Check Catalog Msg 3851, State 1: An invalid row

(class=60,depid=3,depsubid=0) was found in the system table sys.syssingleobjrefs (class=60).

Msg 8992, Level 16, State 1, Line 1

Check Catalog Msg 3851, State 1: An invalid row

(class=60,depid=4,depsubid=0) was found in the system table sys.syssingleobjrefs (class=60).

Msg 8992, Level 16, State 1, Line 1

Check Catalog Msg 3851, State 1: An invalid row

(class=60,depid=5,depsubid=0) was found in the system table sys.syssingleobjrefs (class=60).

Msg 8992, Level 16, State 1, Line 1

Check Catalog Msg 3851, State 1: An invalid row

(class=26,depid=260,depsubid=0,indepid=3,indepsubid=0) was found in the system table sys.sysmultiobjrefs (class=26).

Msg 8992, Level 16, State 1, Line 1

Check Catalog Msg 3851, State 1: An invalid row

(class=26,depid=261,depsubid=0,indepid=3,indepsubid=0) was found in the system table sys.sysmultiobjrefs (class=26).

Msg 8992, Level 16, State 1, Line 1

Check Catalog Msg 3851, State 1: An invalid row

(class=26,depid=266,depsubid=0,indepid=3,indepsubid=0) was found in the system table sys.sysmultiobjrefs (class=26).

Msg 8992, Level 16, State 1, Line 1

Check Catalog Msg 3851, State 1: An invalid row

(class=26,depid=299,depsubid=0,indepid=9,indepsubid=0) was found in the system table sys.sysmultiobjrefs (class=26).

Msg 8992, Level 16, State 1, Line 1

Check Catalog Msg 3851, State 1: An invalid row

(class=26,depid=337,depsubid=0,indepid=3,indepsubid=0) was found in the system table sys.sysmultiobjrefs (class=26).

Msg 8992, Level 16, State 1, Line 1

Check Catalog Msg 3851, State 1: An invalid row

(class=76,depid=65536,depsubid=100) was found in the system table sys.syssingleobjrefs (class=76).

Msg 8992, Level 16, State 1, Line 1

Check Catalog Msg 3851, State 1: An invalid row

(class=76,depid=65536,depsubid=101) was found in the system table sys.syssingleobjrefs (class=76).

Msg 8992, Level 16, State 1, Line 1

Check Catalog Msg 3851, State 1: An invalid row

(class=76,depid=65536,depsubid=102) was found in the system table sys.syssingleobjrefs (class=76).

CHECKDB found 0 allocation errors and 17 consistency errors not associated with any single object.

Analysis

Here check DB found consistency errors on multiple system tables in user database. Unlike the report, which we generally see after running DBCC checkdb, this report didn’t show like

‘repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB’

or

‘repair_fast is the minimum repair level for the errors found by DBCC CHECKDB’

or

‘repair_rebuild is the minimum repair level for the errors found by DBCC CHECKDB’

Solution

You can try running DBCC repair options but none will fix the issue. Please note, repair_allow_data_loss is not recommended, as we will not know which all data blocks are removed by this command.

Only solution that will work here is, to create a blank database and then export all the database objects and data to the newly created database. There is no other solution possible for these errors.

Configuring firewall settings for SQL Server Reporting Services (SSRS) on Windows 2008 R2

This is the last of the series of articles that we have published on how to configure firewall settings for SQL Server components installed on Windows 2008 R2 server. So, now we will be talking about opening port for SOL Server Reporting services on Windows 2008 R2.

1) Go to Start –> Administrative tools–> Windows Firewall with Advanced security tool.

2) Here go to Inbound Rule tab and open a new rule window. We will be creating a new rule in order to open a port for SSRS.

3) Since we have to open port for SSRS, select the option Port in Rule type and move to the next step.

4) Select TCP and mention the port number as 80. Then move to next step.

5) Select allow the connection so that connections are allowed to SSRS using port 80. Then move next.

6) In the profile tab, select the appropriate option as per your requirement.

7) In this final step, provide appropriate name to this rule like ReportServer (TCP on 80) and click Finish.

8) Rules are enabled by default but you can verify that by going to Inbound rules and look for the newly created rule.