SQL Server service doesn't start anymore automatically if I make a Windows restart

Question

I have Windows 10 build 1511, where I have installed SQL Server 2014.

After installation everything is OK.

I\'ve made several times shutdown on Windows 10, a

Answer 1

I faced this issue today , as my server is dependent on SQL server connection , that was also not booting up. It was simple in my case. I saw in services screen its status is STOP. So I started there ans it started working. windows+R--> services.msc--> right click on the service and start it.

Answer 2

If you starts services.msc and serach for the SqlServer service, in properties, set the startup as automatic delay instead of automatic.

Answer 3

I'm dealing with the same issue on Win 2012. and it looks like the same issue described here:

Add your windows level user in following path:

Click on Start - Run - Secpol.msc Go to Local Policies - User right assignments

1. Act as a part of the Operating system
2. bypass Traverse checking
3. Lock pages in memory
4. Log on as a service
5. Log on a batch job
6. Replace process level token

If not, please add them and try restarting your system. Your SQL Server should be starting as a service. All the best.

Answer 4

I had this issue on Windows 10 and SQL Server 2014 Express.

The delayed start option didn't work for me, but here's what did work - granting higher DCOM permissions to the Network Service and Local Service accounts.

1. Click Start, type Component and then click the Component Services app
2. In Component Services, double-click Component Services, and then double- click Computers. Right-click My Computer, and then click Properties.
3. Click the COM Security tab.
4. In the Launch and Activation Permissions area, click Edit Default.
5. Click Add, type Network Service, and then click OK. While Network Service is selected, click to select the Allow check boxes for the following items:
   • Local Launch
   • Remote Launch
   • Local Activation
   • Remote Activation
6. Repeat step 4 for the Local Service account.
7. Reboot and SQL Server should not start automatically.

In my case, this is a development environment so I'm less concerned about the security implications of this change and more concerned about getting it to work. So be advised to check out potential security ramifications if that's important in your situation.

Answer 5

pay Attention in suffix too

example: if in your user Secedit.msc is as contoso\usersql, in the windows service needs to be the same, I was putting usersql@contoso.com and was having problems to start the service automatic, after change to contoso\usersql, working fine