Details
Product:SQL Server
ID:9003
Source:MSSQLServer
Version:10.0
Component:SQLEngine
Symbolic Name:LOG_INVALID_LSN
Message:The log scan number %S_LSN passed to log scan in database '%.*ls' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup.
   
Explanation

A component passed an invalid log sequence number to the log manager for the database. This could be replication, corruption, or an inconsistency between the primary data file and the log.

   
User Action

If this occurred during replication, recreate the publication. Otherwise, restore from backup.

   
   
Version:8.0
Component:SQL Engine
Message:The LSN %S_LSN passed to log scan in database '%.*ls' is invalid.
   
Explanation
If you see this message during startup when the SQL Server process tries to recover the database or as a result of an ATTACH statement, the log file for the database is corrupted. If you see the message during a restore process, the backup file is corrupted. If you see this message during a replication process, the replication metadata may be incorrect.
   
User Action
If you see the error during a restore process, check the integrity of the backup file. If possible, create a new backup in a new location and retry the restore with the new backup file.

If you see this error during startup or when you try to attach a database:

HARDWARE FAILURE

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.

DBCC CHECKDB

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.