BTW sysobjects view exists in 2005+ versions also.
The view does, but it's a view and not a table and since a view does not store data, sysobjects cannot become corrupt. Its underlying tables can, but not the view.
So if somebody is trying to select data from sysobjects in later 2005+ then he can get the same error that is listed here.
No he can't.
He cannot get this exact error for a number of reasons, not least because the errors were rewritten in SQL 2005 and no longer have the form that was posted here. Also because sysobjects is not a table in SQL 2005+, it's a view, and any corruption that affects the underlying tables will be reported as being in the underlying tables, not sysobjects.
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter
We stand on the bridge and no one may pass