Windows could not start the sql server service on local computer

Unable to initialize SSL support

The error 0x2 when looked up with net helpmsg results in

The system cannot find the file specified.

This points to a missing file or a lack of permissions for the SQL Service Account. Try reapplying SQL Server 2005 Service Pack 3 (SP3) and 959195 Cumulative update package 1 (CU1) for SQL Server 2005 Service Pack 3 to the server. It could be that a DLL was changed by the update or removed that is required. Jonathan Kehayias
http://sqlblog.com/blogs/jonathan_kehayias/
http://www.twitter.com/SQLSarg
http://www.sqlclr.net/
Please click the Mark as Answer button if a post solves your problem!

My machine is Dell Vostro 1510, windows vista Enterprise 32 bit

I tried all options but no luck. Now I have uninstalled sql server 2005 and installing it again. but getting message as The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, «How to: View SQL Server 2005 Setup Log Files» and «Starting SQL Server Manually.

Log of my sql install is

Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Professional Service Pack 2 (Build 6002)
Time : Sat Aug 01 16:27:19 2009

Источник

Windows could not start the SQL Server (MSSQLSERVER) on Local Computer… (error code 3417)

For some reasons I moved this folder : ( Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL ) to another drive, then returned it to the same location, but sql server has stopped working, showing this error when trying to start it again:

Windows could not start the SQL Server (MSSQLSERVER) on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 3417.

I tried many solutions discussed in different forums, but none of them work for me.

The folder is not compressed or encrypted.

Thanks for your kind help in advance.

19 Answers 19

Very simple to solve this problem.

Just open RUN window(Window+R) and type services.msc :

Find the SQL within name column and right click on that.

right click on SQL as in screenshot

You will get properties option, click on properties.

One new window will be open and there you have to click on Log On tab. And select the Local System Account. then apply and okay.

Select Local system Account

After that come again in services.msc window. and right click on sql and click start.

And finally, SQL Server services started successfully. enjoy and keep learning.

If so, plesae goto the driver or folder, change the compress option by

After above things, you should be able to start the service again.

In my particular case, I fixed this error by looking in the Event Viewer to get a clue as to the source of the issue:

I then followed the steps outlined at Rebuilding Master Database in SQL Server.

In my particular case, the command to rebuild the master database was:

Run this command after opening cmd as administrator

This command is called trace flag 902. It is used to bypass script upgrade mode. Every time when you try to start your sql service it also looks for script upgrades. and when the script upgrade fail your service unable to start. So, Whenever we have such upgrade script failure issue and SQL is not getting started, we need to use trace flag 902 to start SQL.

I hope this will help you..

I have had the same error recently. I have checked the folder Log of my Server instance.

and I have found this errors in logs

So for me it was an easy fix. I just added proper access rights to this files to the sql server service account. I hope it will help

What is System Event Log saying?

I was getting this error today. And above answers didn’t help me. I was getting this error when I try to start the SQL Server(SQLEXPRESS) service in Services(services.msc).

When I checked the error log at the location C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS\MSSQL\Log, there was an entry related TCP/IP port.

2018-06-19 20:41:52.20 spid12s TDSSNIClient initialization failed with error 0x271d, status code 0xa. Reason: Unable to initialize the TCP/IP listener. An attempt was made to access a socket in a way forbidden by its access permissions.

Recently I was running a MSSQLEXPRESS image in my docker container, which was using the same TCP/IP port, that caused this issue.

So, what I did is, I just reset my TCP/IP by doing the below command.

netsh int ip reset resetlog.txt

Once the resetting is done, I had to restart the machine and when I try to start the SQLEXPRESS service again, it started successfully. Hope it helps.

In My case I had to Upgrade the SQL Server since evaluation licence had been expired.

Database rebuild fixed it for me as well. Also had to restore the old database from backup as it got corrupted during power outage. The copy master.mdf procedure did not work for me.

i had the same problem before

the error code 3417 : the SQL SERVER cannot start the master database, without master db SQL SERVER can’t start MSSQLSERVER_3417

The master database records all the system-level information for a SQL Server system. This includes instance-wide metadata such as logon accounts, endpoints, linked servers, and system configuration settings. In SQL Server, system objects are no longer stored in the master database; instead, they are stored in the Resource database. Also, master is the database that records the existence of all other databases and the location of those database files and records the initialization information for SQL Server. Therefore, SQL Server cannot start if the master database is unavailable MSDN Master DB so you need to reconfigure all settings after restoring master db

solutions

Источник

• ← Windows could not start the service on local computer error 1053
• Windows could not verify the digital signature of netlimiter 4 driver →