Cannot recover the master database. Exiting.

Details
Product: SQL Server
Event ID: 3417
Source: MSSQLServer
Version: 10.0
Component: SQLEngine
Symbolic Name: REC_BADMASTER
Message: Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
   
Explanation

SQL Server cannot start the
master
database. If the
master
or
tempdb
cannot be brought online, SQL Server cannot run. This error is usually preceded by other errors. Review error logs to find the root cause.

   
User Action

Restore backup of the database or repair the database.

   
   
Version: 9.00.1281.60
Symbolic Name: REC_BADMASTER
Message: Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
   
Explanation

SQL Server cannot start the master database. If the master or tempdb cannot be brought online, SQL Server cannot run. This error is usually preceded by other errors. Review error logs to find the root cause.

   
User Action

Restore backup of the database or repair the database.

   
   
Version: 9.0
Component: SQLEngine
Symbolic Name: REC_BADMASTER
Message: Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
   
Explanation

SQL Server cannot start the
master
database. If the
master
or
tempdb
cannot be brought online, SQL Server cannot run. This error is usually preceded by other errors. Review error logs to find the root cause.

   
User Action

Restore backup of the database or repair the database.

   
   
Version: 8.0
Component: SQL Engine
Message: Cannot recover the master database. Exiting.
   
Explanation
The master database is not in a recoverable state.
   
User Action
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.

Related:

Leave a Reply