This error can occur when the error log file does not match the database file or when the .mdb file is detected as being corrupt.
There are multiple ways to fix the problem and the solution depends on whether or not your database has data that is critical for you to keep. For me, I only get this error on my local box where I’m conducting allot of experiments and tests so that there is no need for me to worry about critical data. This makes the restoration task much more simple.
First, I try the following canned stored procedure : sp_resetstatus. If this fails then the following always works:
- Stop the SQL Server database & services
- Rename or move the “msdblog.ldf” & “msdbdata.mdf” files
- Copy “msdblog.ldf & msdbdata.mdf” files from any other working database installation to the same path
- Start the SQL Server database