Jeff,
I agree with your comments, But as before trying with the dbcc commands, i requested to do the basic analysis on the row size so that if it didnt solve this i thought to recommend the dbcc commands.
These 12301 errors are, actually, transitient and no permanent database corruption exists.
This can be verified by running :
dbcc checktable(<table_name>)
They are caused when one process (spid) is performing an isolation level 0 scan of a table while another process is simultaneously updating a row.
Regards
Kiran Kumar A
SAP