So my guess then is that there's system table corruption in master - possibly in a table holding login info. Make sure she run's DBCC on the system databases too.

Thanks

But he also says he can't even connect to the database now - that's why I think there's some corruption in there too. That error can also crop up (when...

Ah - ok you've definitely still got a corrupt database then. Do you have any output from the maintenance job(s)? One of them should be failing every night...

Do you get this error whenever you try to do anything with the database?

What's the output from running 'DBCC CHECKDB (yourdbname) WITH ALL_ERRORMSGS, NO_INFOMSGS' from a connection to the database?

Should be somewhere in there - can you post the error log? (Or just email it to me - paul@sqlskills.com).

It's entirely possible (and likely) that the error came from one...

This error and state indicates that you've got missing information in one of the system tables in a database (i.e. metadata corruption). In the SQL Server error log (buried down...

c0000005 is the code for an AV (access violation - commonly occurs when something is corrupt and causes a reference to an invalid piece of memory). Is this happening in...

Duplicate thread - Steve - please remove.

No need - if your master is corrupt and you don't have a backup, you're going to have to create a new master database, and then reattach the user databases....

ok - that screams 'bug' at me - it wouldn't work on 2005 if the backup was corrupt.

Yup - I realize that. The only things I can suggest in this case are that it's either a bug or a corruption in your backup.

Unfortunately, on SQL 2000, its...

Interesting - I'll dig around with the SQL and MOSS dev teams and see what I can find out.

Cheers

Cool (well, kind of). Do you know if there was a failed CHECKDB beforehand?

There have been some bugs that would cause this - see http://support.microsoft.com/kb/329487 and http://support.microsoft.com/kb/831950.

PS I found these doing a Google search on the error message - always try that first...

Cool. That error is benign and you can safely repair it without any data loss (although you need to use that option to repair it).

Shoot me an email with devlink...