Issue:-
015-06-12 21:37:54.32 spid5s Script level upgrade for database 'master' failed because upgrade step 'msdb110_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.
2015-06-12 21:37:54.32 spid5s Error: 3417, Severity: 21, State: 3.
2015-06-12 21:37:54.32 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.
2015-06-12 21:37:54.33 spid5s SQL Server shutdown has been initiated
2015-06-12 21:37:54.33 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
Cannot close event log because there are still event handle users active.
The issue in previous Errorlog file.
2015-06-12 18:34:49.17 spid7s Uploading data collector package from disk: D:\MSSQL11.MSSQLSERVER\MSSQL\Install\SqlTraceCollect.dtsx
2015-06-12 18:34:49.17 spid7s Uploading data collector package from disk: D:\MSSQL11.MSSQLSERVER\MSSQL\Install\SqlTraceCollect.dtsx
2015-06-12 18:34:49.17 spid7s Error: 4860, Severity: 16, State: 1.
2015-06-12 18:34:49.17 spid7s Cannot bulk load. The file "D:\MSSQL11.MSSQLSERVER\MSSQL\Install\SqlTraceCollect.dtsx" does not exist.
2015-06-12 18:34:49.17 spid7s Error: 912, Severity: 21, State: 2.
The Problem is SQL Server generate more genereic error, and we have tendency to focus on generic error only, and we ignore actual error.
Here in this case the actual error was
2015-06-12 18:34:49.17 spid7s Uploading data collector package from disk: D:\MSSQL11.MSSQLSERVER\MSSQL\Install\SqlTraceCollect.dtsx
where as DBA concentrate more one error highlighted in green.
The Problem is SQL Server generate more genereic error, and we have tendency to focus on generic error only, and we ignore actual error.
Here in this case the actual error was
2015-06-12 18:34:49.17 spid7s Uploading data collector package from disk: D:\MSSQL11.MSSQLSERVER\MSSQL\Install\SqlTraceCollect.dtsx
where as DBA concentrate more one error highlighted in green.
Resolution:-
Actually, The error highlighted in green is a generic & Misguided error.
The Actual error is highlighted in Red*
Actually, "X:\MSSQL11.MSSQLSERVER\MSSQL\Install \" should contain a list of dtsx files besides *.sql and *.cer
PerfCountersCollect.dtsx -- Missing file from the upgrade logs
PerfCountersUpload.dtsx -- Missing file from the upgrade logs
QueryActivityCollect.dtsx -- Missing file from the upgrade logs
QueryActivityUpload.dtsx -- Missing file from the upgrade logs
SqlTraceCollect.dtsx -- Missing file from the upgrade logs
SqlTraceUpload.dtsx --- Missing file from the upgrade logs
TSQLQueryCollect.dtsx -- Missing file from the upgrade logs
TSQLQueryUpload.dtsx -- Missing file from the upgrade logs
Resolution:-
In order to fix this issue, you have to copy all these files from same version of another SQL Server and then paste in the location X:\MSSQL11.MSSQLSERVER\MSSQL\Install.
then restarted the services, the SQl Server service will came up.
Thanks for Reading and hope this will help someone who have facec this issue.
Do not forget to comment, irrespective of Issue gets resolve or not.
then restarted the services, the SQl Server service will came up.
Thanks for Reading and hope this will help someone who have facec this issue.
Do not forget to comment, irrespective of Issue gets resolve or not.