| 
                
Please start any new threads on our new 
    site at https://forums.sqlteam.com.  We've got lots of great SQL Server
    experts to answer whatever question you can come up with. 
    
        | 
                
                    | 
                            
                                | Author | Topic |  
                                    | sqlvijayStarting Member
 
 
                                        16 Posts | 
                                            
                                            |  Posted - 2009-03-25 : 07:00:37 
 |  
                                            | HI EVERYBODY,I got below error message in sql server 2000 production server application log yesterday.eventtype:error eventid:17052category (2)Error: 602, Severity: 21, State: 50Could not find row in sysindexes for database ID 24, object ID 1, index ID 1. Run DBCC CHECKTABLE on sysindexes.For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.please let me know how to solve this error.Thanks in Advance Vijay.Sedit: moved to correct forum |  |  
                                    | tosscrosbyAged Yak Warrior
 
 
                                    676 Posts | 
                                        
                                          |  Posted - 2009-03-25 : 10:00:55 
 |  
                                          | Just curious, is this a SQL 2005 database that you are trying to attach to SQL 2000? If so, that won't work. Did you run DBCC CHECKTABLE as suggested? If so, what were the results? You may also want to run DBCC CHECKDB dbname WITH ALL_ERRORMSGS, NO_INFOMSGS on the database in question and post the results here for Paul or Gail's reading pleasure (our resident corruption "gurus") and a possible quicker response.Terry-- Procrastinate now! |  
                                          |  |  |  
                                    | paulrandalYak with Vast SQL Skills
 
 
                                    899 Posts | 
                                        
                                          |  Posted - 2009-03-25 : 11:51:03 
 |  
                                          | That's exactly what that error state means. I just blogged about this - see [url]http://www.sqlskills.com/BLOGS/PAUL/post/Msg-602-Level-21-State-50-Line-1.aspx[/url]Paul S. Randal, Managing Director, SQLskills.com (www.SQLskills.com/blogs/paul)SQL Server MVP, Contributing Editor of TechNet MagazineAuthor of SQL 2005 DBCC CHECKDB/repair codeAuthor & Instructor of Microsoft Certified Master - Database course |  
                                          |  |  |  
                                |  |  |  |  |  |