Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

After updating, whenever I start the service of the server in configuration manager, it always stops then.

And I found the error in the log

2013-04-13 19:08:19.63 spid7s Error: 15174, Severity: 16, State: 1.

2013-04-13 19:08:19.63 spid7s Login '##MS_PolicyEventProcessingLogin##' owns one or more database(s). Change the owner of the database(s) before dropping the login.

2013-04-13 19:08:19.63 spid7s Error: 912, Severity: 21, State: 2.

2013-04-13 19:08:19.63 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-04-13 19:08:19.63 spid7s Error: 3417, Severity: 21, State: 3.

2013-04-13 19:08:19.63 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-04-13 19:08:19.63 spid7s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

Can anyone pinpoint why this is happening?

As I cannot start the server of SQL server, I cannot connect via management studio and edit anything. How can I edit, for example, the owner of the database?


migration rejected from Jun 3 '15 at 10:14

This question came from our site for professional and enthusiast programmers. Votes, comments, and answers are locked due to the question being closed here, but it may be eligible for editing and reopening on the site where it originated.

closed as off-topic by Max Vernon, Paul White, dezso, Colin 't Hart, RolandoMySQLDBA Jun 3 '15 at 10:14

This question appears to be off-topic. The users who voted to close gave these specific reasons:

  • "Too localized - this could be because your code has a typo, basic error, or is not relevant to most of our audience. Consider revising your question so that it appeals to a broader audience. As it stands, the question is unlikely to help other users (regarding typo questions, see this meta question for background)." – Max Vernon, Paul White, RolandoMySQLDBA
  • "Tip of the iceberg - the question or comments reveal an underlying issue that would need extensive investigation by a consultant or database vendor support team: issues like this do not fit the SE Q&A model well. For more information see this meta post." – dezso, Colin 't Hart
If this question can be reworded to fit the rules in the help center, please edit the question.

It is a problem to tackle with the help of Microsoft Support. Their upgrade script appears to be at fault. Best case is you can manually change the ownership of database ('master'?) away from '##MS_PolicyEventProcessingLogin##', and then proceed. – hardmath Apr 13 '13 at 13:59
Did you try starting it up in single user mode (sqlservr.exe -m)? – Aaron Bertrand Apr 13 '13 at 18:53
Have you seen this? Connecting using trace flag 902 and making sure to run the update as an admin were the big takeaways. – Jason Quinones Apr 15 '13 at 16:43