views:

741

answers:

2

The error happens trying to do an insert from a stored proc. I tried running DBCC CHECKDB as suggested by the kb article that Jonathan Holland suggested and it returned with the all clear.

+3  A: 

Bummer dude.

http://support.microsoft.com/kb/828337

FlySwat
+1  A: 

Ran a dbcc dbreindex ('tablename') against the tables that were being affected by the stored procedure that was being called. This forced all of the pages to be moved, which appears to have corrected the problem. This would indicate it was a page corruption that the DBCC CHECKDB didn't catch.