data-konzept

'In this post we would like to explain one of the interesting issues that we encountered while upgrading a SQL Server Instance.

Symptoms

SQL Server Service fails to start after applying SQL patch due to misconfiguration in MSDB.

Error:

2016-06-28 19:23:41.22 spid5s    Script level upgrade for database ‘master’ failed because upgrade step ‘msdb110_upgrade.sql’encountered error 2714, state 6, severity 25. Severity: 16, State: 0.
2016-06-28 19:23:41.22 spid5s    CREATE SCHEMA failed due to previous errors.
2016-06-28 19:23:41.22 spid5s    Error: 912, Severity: 21, State: 2.
2016-06-28 19:23:41.22 spid5s    Script level upgrade for database ‘master’ failed because upgrade step ‘msdb110_upgrade.sql’ encountered error 2714, state 6, 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 error log entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
2016-06-28 19:23:41.22 spid5s    Error: 3417, Severity: 21, State: 3.
2016-06-28 19:23:41.22 spid5s    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.
2016-06-28 19:23:41.22 spid5s    SQL Server shutdown has been initiated'...

https://blogs.msdn.microsoft.com/ujpat/2017/01/22/sql-server-service-fails-to-start-after-applying-patch-error-create-schema-failed-due-to-previous-errors/