10:14:27.32 spid5s Setting database option COMPATIBILITY_LEVEL to 110 for database 'msdb'. upgrade script terminating.', 20, 127) WITH LOG RAISERROR('A problem was encountered accessing msdb.
10:14:27.30 spid5s Starting execution of PRE_SQLAGENT100.SQL PRINT 'Starting execution of PRE_SQLAGENT100.SQL' I solved my problema after starts with -T3601 and get in the log the Filestream trouble: PRINT '-' You can skip the scrip upgrade using trace flag -T902 and then you will be able to start SQL and connect to it to fix any kind of issues caused the script upgrade to failĪn another trouble like this occurs after I upgraded SQL Server 2012 with SP1, but is related with Filestream feacture. Just above this error, you will find the actual error causing the script upgrade to fail, so you need to fix that error so that the script upgrade can be completed next time without any issues. Of error the script upgrade fails and you will see his kind of error in the SQL logs and the SQL service will not start., Normally when you upgrade SQL or when you apply some patches, when the SQL instance restarts it runs few SQL scripts on the system databases. You don't have to rebuild or reinstall or repair SQL when you see these kind of errors. I don't have a master backup as this is a dev machine and there is no critical data involved. My dev machine also has SS2008 Dev on it as well - which is working. I tried a repair install, but that failed. For more information about how to rebuild the master database, see SQL Restore master from a full backup, repair it, or rebuild it.
Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the scriptĬannot recover the master database.
If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. This is a serious error condition which might interfere with regular operation and the database will be taken offline. Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 547, state 0, severity 16. I installed SS2012 Dev a couple of months ago on my dev machine(Win 7) - it worked for a while, but now it won't start and there are two errors in the Event log.