Master DB Recovery Failure After Upgrading to SQL Server 10.50.6220

Master DB Recovery Failure After Upgrading to SQL Server 10.50.6220

April 14, 2017

I recently tried to upgrade a SQL Server 2008 R2 instance to build 10.50.6220. In fact I worked on two servers simultaneously. Both succeeded but one instance failed to startup after the installation. The errors in Event Viewer were as follows:

 


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.

Script level upgrade for database ‘master’ failed because upgrade step ‘sqlagent100_msdb_upgrade.sql’ encountered error 200, state 7, severity 25. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the ‘master’ database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.


 

This was scary and I began preparing to repair the instance. A repair using command line options might involve revert the instance to the RTM level. I had the option of a restore so I started up the instance in single-user mode and saw the actual error below:


2017-04-14 15:23:09.20 spid6s Dropping procedure [dbo].[sp_syscollector_enable_collector]…
2017-04-14 15:23:09.20 spid6s Creating procedure [dbo].[sp_syscollector_enable_collector]…
2017-04-14 15:23:09.21 spid6s Dropping procedure [dbo].[sp_syscollector_disable_collector]…
2017-04-14 15:23:09.21 spid6s Creating procedure [dbo].[sp_syscollector_disable_collector]…
2017-04-14 15:23:09.21 spid6s Dropping procedure [dbo].[sp_syscollector_get_trace_info]

2017-04-14 15:23:09.32 spid6s Uploading data collector package from disk: f:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Install\SqlTra
ceCollect.dtsx
2017-04-14 15:23:09.33 spid6s Error: 4860, Severity: 16, State: 1.
2017-04-14 15:23:09.33 spid6s Cannot bulk load. The file “f:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Install\SqlTraceCollect.dtsx”
does not exist.
2017-04-14 15:23:09.33 spid6s Error: 912, Severity: 21, State: 2.

.

.

.
2017-04-14 15:23:09.33 spid6s Script level upgrade for database ‘master’ failed because upgrade step ‘sqlagent100_msdb_upgrade.sql’ encountered error 200,
state 7, severity 25. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happen
ed during upgrade of the ‘master’ database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take
the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
2017-04-14 15:23:09.33 spid6s Error: 3417, Severity: 21, State: 3.
2017-04-14 15:23:09.33 spid6s 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.


 

I simply copied the contents of the path f:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Install\ from its equivalent on the working server and I was able to start the instance. I still am not sure where things went wrong. Comment if you can hazard a guess.

 

Igiri Books © Copyright 2016. All Rights Reserved. Site Credits: AppWorld