Lynn Pettis (8/29/2012)
Looks like a problem with a nonclustered index, id = 22. Try dropping and recreating this index.
Just as an FYI, I would have done this before using REPAIR_ALLOW_DATA_LOSS. It does indeed look like an index that can be dropped and re-created and considering the severity of REPAIR_ALLOW_DATA_LOSS trying that first makes more sense. If that didn't work, I still would have gone to backups. Maybe you'll get lucky and they're not all corrupted.
EDIT: You also posted this to the wrong forum ( SQL Server 7,2000 but you said it's 2005). Could have caused confusion for some.