|Message:||During undoing of a logged operation in database ‘%.*ls’, an error occurred at log record ID %S_LSN. Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.|
This is the rollup error for undo recovery. There should be a previous error logged in the Windows event log indicating the specific failure.
Restore database, file or page from backup or repair database.
|Message:||Error while undoing logged operation in database ‘%.*ls’. Error at log record ID %S_LSN.|
|The recovery process could not undo (roll back) one or more transactions in the specified database. This error will be accompanied by a more specific error in the SQL Server error log and/or the event log.|
Run hardware diagnostics and correct any problems. Also examine the Microsoft Windows NT system and application logs and the SQL Server error log to see if the error occurred as the result of hardware failure. Fix any hardware related problems.
If you have persistent data inconsistency problems, try to swap out different hardware components to isolate the problem. Check that your system does not have write caching enabled on the disk controller. If you suspect this to be the case, contact your hardware vendor.
Finally, you might find it beneficial to switch to a completely new hardware system, including reformatting the disk drives and reinstalling the operating system.
RESTORE FROM BACKUP
If the problem is not hardware related and a known clean backup is available, restore the database from the backup.
If no clean backup is available, execute DBCC CHECKDB without a repair clause to determine the extent of the corruption. DBCC CHECKDB will recommend a repair clause to use. Then, execute DBCC CHECKDB with the appropriate repair clause to repair the corruption.
CAUTION: If you are unsure what effect DBCC CHECKDB with a repair clause has on your data, contact your primary support provider before executing this statement.
If running DBCC CHECKDB with one of the repair clauses does not correct the problem, contact your primary support provider.