Service Not Starting after upgrade of Sql Server 2012 to SP1

• asdfasdf-440613

  SSC Journeyman

  Points: 89

  More actions

  November 18, 2013 at 5:50 pm

  #286431

  We recently upgraded out Sql Server 2012 RTM instance to SP1 base configuration. After the upgrade, the Sql Server Service fails to start up clean.

  I checked the log, the failure is when Sql Server runs the final upgrade script. I added the trace flag -T902 to the startup parameters to prevent it from running the scripts and the service started. The Sql Server is now showing version Sp1 but it does not start if I remove the trace floa -T902. I also added trace flag -T3601 to print out the batch details in the log and noticed that the error "The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction." is created when running the below statement. If I run the below query seperately it runs fine. No sure how to get this fixed and service restarted without using the -T902 flag.

  EXEC sp_dbcmptlevel @dbname = 'msdb', @new_cmptlevel = '100'

  Below is the last entries on the Error Log.

  ----------------------------------

  2013-11-19 10:42:17.74 spid5s Starting execution of PRE_MSDB.SQL

  2013-11-19 10:42:17.74 spid5s ----------------------------------

  2013-11-19 10:42:17.84 spid5s Error: 3930, Severity: 16, State: 1.

  2013-11-19 10:42:17.84 spid5s The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction.

  2013-11-19 10:42:17.84 spid5s Error: 912, Severity: 21, State: 2.

  2013-11-19 10:42:17.84 spid5s Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 3930, state 1, severity 16. 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.

  2013-11-19 10:42:17.84 spid5s Error: 3417, Severity: 21, State: 3.

  2013-11-19 10:42:17.84 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.

  2013-11-19 10:42:17.84 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.