Many times I feel that I have so many blogs that I must have covered all common possible error related to usage of SQL Server. But there are few easy ones which I missed. And thanks to those who take time in sending them to me that it makes a great reminder to what I have missed till date. This blog is from one of such logon failure errors that came from a DBA from one of my consulting engagements. Since the error was simple enough, I thought to respond over mail to solve the problem.
After restarting my box, SQL Service didn’t start even though it was set to start automatically. As usual, I started looking around for error messages and fond below in the event log.
Log Name:Â Â Â Â Â System
Source:Â Â Â Â Â Â Â Service Control Manager
Date:Â Â Â Â Â Â Â Â Â 13-May-16 5:29:37 AM
Event ID:Â Â Â Â Â 7000
Task Category: None
Level:Â Â Â Â Â Â Â Â Error
Keywords:Â Â Â Â Â Classic
User:Â Â Â Â Â Â Â Â Â N/A
Computer:Â Â Â Â Â BIGPINAL
Description:
The SQL Server (SQL2014) service failed to start due to the following error:
The service did not start due to a logon failure.
I know how to fix the problem, but I found that I didn’t have a blog on this error. So here are the steps.
- Get the correct password of the account which is used to run the service. Take help from your domain administrators. If you decide to reset the password, keep in mind that this account might be used at other SQL Instance and other applications also.
- Use SQL Server Configuration Manager and choose the service which is not able to start.
- Right Click and go to Properties.
 
- Provide correct password on the Log On tab as shown below.
 
Once the correct password is provided, you should be able to start SQL Service without any problem. Have you ever encountered this error ever in your environments? Do let me know about what you did to solve the same.
Reference: Pinal Dave (https://blog.sqlauthority.com)
6 Comments. Leave new
Thank you Pinal. Yes, I have experienced this problem before in my home lab. I have built a cluster environment with one DC and other two nodes. One day I was promptly asked to change my password because the previous one was expired. I changed and when I logged in to the Nodes all the Sql services were stoped. Some of them were ON but I couldn’t log into the Sql server. It took me quite some times before I decided to go back to Configuration Manager and Change all Sql and Sql Server Agents passwords. From that time everything started to work agaian.
Hi Pinal, first of all thanks for this and all the rest of the answers I did only find here before. Just a comment, in my case, after the latest Microsoft Update, I had also to change the passwords(to the same ones) of the users I am running SQL Server and SQL Server Agent to make it work. But, again, your suggestion pointed me in the right direction (I was starting to freak out with the local policies, etc, etc)
@Ramon – I am sure this would help others.
Hi,
This happened to me but I didn’t change any passwords. I just restarted the Server.
Dear Mr.Pinal,
We have VM’s running and Sql server is installed on one of the VM’S .Everything running fine.We have backups running at night and a replication of VM’s on another server Using HYper-V from Arcserve backup tool is done successfully.What i noticed when i start that Hyper-V virtual standy server the sql server do not start .it’s showing Windows could not start the sql server (MSSQLSERVER) service on local computer.Error 2: They System cannot find the file specified.Can you please help to resolve this issue.
Thanks in Advance.
Looking to hear from you.
Hi @Pinal Dave, Thanks for sharing steps to resolve this event ID 7000 issue. But pleas let us know what is the cause of this issue, so it can be avoided. Thanks.