After installing SP3 for SQL Server 2008, I cannot connect to the database anymore.
Trying to connect to the server with Management Studio results in an error about the network. Starting the server manually in SQL Server Configuration Manager, the trying to connect results in an error about the server being in "scripting mode."
I do not have a backup of the master database, though I do have a backup of the database I was working on. The databases themselves are still in the DATA folder.
I have tried running a repair, to no avail.
What do I need to do to get it running again?
The last lines of the log file are:
pid7s Error: 15174, Severity: 16, State: 1.2013-02-18 16:01:53.22 spid7s Login '##MS_PolicyEventProcessingLogin##' owns one or more database(s). Change the owner of the database(s) before dropping the login.
2013-02-18 16:01:53.22 spid7s Error: 912, Severity: 21, State: 2.
2013-02-18 16:01:53.22 spid7s Script level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_upgrade.sql' encountered error 15174, 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-02-18 16:01:53.22 spid7s Error: 3417, Severity: 21, State: 3.
2013-02-18 16:01:53.22 spid7s 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-02-18 16:01:53.22 spid7s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.