September 28, 2014 at 8:12 am
Hi
Has anyone run into this problem while trying to install the service pack 2 on SQL Server 2012?
Error: 912, Severity: 21, State: 2.
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 errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
Error: 3417, Severity: 21, State: 3.
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.
SQL Server shutdown has been initiated
Thanks
Kathy
September 28, 2014 at 8:55 am
plamannkathy (9/28/2014)
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
What did you find when you did the investigation the message said you needed to do?
The message you posted is a generic 'something went wrong'. Can't help you with just that.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 28, 2014 at 9:40 am
The corrective action stated to restore or rebuild the master database. We tried to restore and that didn't work. We're working on a rebuild--tried to rebuild the master using the setup/Q/ACTION=REBUILDDATABASE /INSTANCENAME=MSSQLSERVER and added the account still no luck.
September 28, 2014 at 10:41 am
The message posted said to check the latest errorlog for the last messages and fix whatever those messages said was wrong. So, I'm asking what were those messages and what exactly did they say to do?
I can't see your screen, I can't read your files, unless you post exact messages there is no way I can help you.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 29, 2014 at 6:53 am
The corrective action was to restore the master database. I know longer have the error log. What we decided to do after a lot of trial and error was to uninstall the Service Pack 2. That ran successfully. Out of 4 servers that I installed sp2 this was the only server that was stuck in upgrade mode. We never did get to the root cause.
Thanks again Gail.
Kathy
October 8, 2014 at 4:41 pm
After i installed service pack 2 for SQL server 2012 SP1, x64 on windows server 2012 and have always on enabled with isolated disks. I was unable to restart the SQL server failed with below 2 errors and Uninstalled the service pack 2 and the server started back , is there a bug in SQL server 2012 sp2 ?
Error 1 :
"Script level upgrade for database 'master' failed because upgrade step 'SSIS_hotfix_install.sql' encountered error 922, state 1, 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. "
Error 2:
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.
October 9, 2014 at 9:31 am
I was never able to find out if there is a bug in SP2 or not. I have installed SP2 SQL Server successfully on other servers, because of these successful installs I think there was another issue of why my install of SP2 was unsuccessful. I will be trying the install again later this month.
Kathy
October 10, 2014 at 3:36 pm
Issue is when service pack has some script like this needs to be executed but the database is in restoring mode because it is involved in Always On secondary.
Resolution is to uninstall the service pack that installed with errors then remove the SSISDB from Always On and then re install should work smooth.
February 23, 2015 at 6:15 am
@SQLFRNDZ
Nice one help me out, The SP2 failure was bugging the CR@P out of me.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply