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

I cannot start the SQL Server 2012 service. The event log says the service-specific error code is 3417.

In the Event Viewer:

The SQL Server (MSSQLSERVER) service terminated with the following service-specific error:
WARNING: You have until SQL Server (MSSQLSERVER) to logoff. If you have not logged off at this time, your session will be disconnected, and any open files or devices you have open may lose data.

I've changed the service logon account in the service properties but this error happened again.

I think the problem is in the master database, but I do not know what to do.


I've try Rebuild the Resource database but this error happened again!

share|improve this question
Do you have working backups of the system databases? If you do, then I suggest you rebuild your system databases on the instance, and then restore the backups. – RoKa May 21 '13 at 11:37
No! So how i can restore when i can't connect to sql server? – mehdi May 21 '13 at 11:41
When you rebuild the system databases, you will be able to connect. – RoKa May 21 '13 at 11:53
No, you can rebuild using the original media set. See this link here: – RoKa May 21 '13 at 12:54
@RoKa: ...huh? I've never seen this particular error before, so no, it's not obvious (at least not to me). Since you seem very clear on what the problem is, consider posting an answer with an explanation of the issue, and the necessary steps to resolve it. – Jon Seigel May 21 '13 at 15:40

That error is usually associated with the Master database, so you are on the right track. Does the service account have access to the directory where the Master database resides?

There should be some additional errors in either the SQL Server error log or the Windows event log that may narrow down the issue. Look for access denied messages or cannot find file messages associated with the master database and other system databases.

One other thing I have found on other sites is folder compression being a problem. Make sure SQL Server does not reside on a compressed folder or drive.

If that doesn't work, then rebuild as suggested.

share|improve this answer

protected by Jack Douglas Feb 4 '14 at 11:03

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.