SQL Server Service Startup Failure Common Errors

As a DBA we encounter issues where SQL Server fail to start after reboot of server or after making some configuration changes. It is very critical to bring the SQL Server online immediately as it impacts applications leading to escalations.

First, we need to understand on where to check if SQL Server fails to start.
– Try to start SQL Server from Configuration manager on standalone servers and on cluster servers, bring the SQL Server resources ONLINE.
– Check if the SQL Serve errorlog is created. You can find the location of the SQL Server errorlog file from Start -> All Programs -> Microsoft SQL Server 2008 or latest version installed -> Configuration Tools -> SQL Server Configuration Manager -> Select SQL Server Services on the left side -> On the right side right click on SQL Server (MSSQLSEVER or instance name) and select Properties -> Click on Advanced Tab(in SQL 2012 or higher there will be separate tab called startup parameters) -> you can see the location of SQL Server ErrorLog file as mentioned next to the “-e” startup parameter .
– Check and see if new errorlog file is getting created when you start the SQL Service, if it is not getting created then check the Event viewer Application and System logs which should have some errors related to the cause of the failure.
– If Errorlog file is created, then look into the file and look for any errors.

Although there could be variety of reasons for the failure, here we try to document most common ones and add more to the list going forward.

Error 1069: The service did not start due to a logon failure.
– This error occurs if the SQL Server service account password in incorrect. Change the password to the correct one from SQL Server configuration manager and then restart the SQL Server service.

The SQL Server (MSSQLSERVER) service failed to start due to the following error: The service did not start due to a logon failure.
– This error occurs when the password provided for the SQL Server service account is incorrect. Open SQL Server Configuration Manager and then provide the correct password.
– If this issue is happening after every reboot of Server, then server might not be able to immediately communicate with Active Directory (AD) or some policy in DC leading to the failure. In this case, you may choose to start the SQL Server service with “(Automatic) Delayed Start” option, which can be configured from registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ and then create a new DWORD DelayedAutoStart and set it to 1 and also ensure Start value key is set to 2. You
can also set this from services console(services.msc), open SQL Server service properties and change the startup type to (Automatic) Delayed Start.

Server local connection provider failed to listen on [ \\.\pipe\SQLLocal\MSSQLSERVER ]. Error: 0x50Error: 17182, Severity: 16, State: 1.
TDSSNIClient initialization failed with error 0x50, status code 0x50.
Error: 17182, Severity: 16, State: 1.
TDSSNIClient initialization failed with error 0x50, status code 0x1.
Error: 17826, Severity: 18, State: 3.
Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
Error: 17120, Severity: 16, State: 1.
SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

– This error occurs, when incorrect values are provided to the Named Pipes in the SQL Server Configuration Manager. For default instance of SQL Server, change the Named Pipe name Protocols for MSSQLSERVER in configuration manager to \\.\pipe\MSSQLSERVER\sql\query and for named instance use the named pipe as \\.\pipe\MSSQL$\query
– Restart the SQL Server instance or better Reboot the server.

Unable to load user-specified certificate. The server will not accept a connection. You should verify that the certificate is correctly installed. See “Configuring Certificate for Use by SSL” in Books Online.
TDSSNIClient initialization failed with error 0x80092004, status code 0x80.
TDSSNIClient initialization failed with error 0x80092004, status code 0x1.

– The error occurs, when SQL Server is unable to use the SSL certificate provided in the SQL Server configuration manager. To fix the issue make sure SSL certificate meets all the requirements to be used for SQL Server.

Error: 26023, Severity: 16, State: 1.
Server TCP provider failed to listen on [ ‘any’ 3136]. Tcp port is already in use.
Error: 17182, Severity: 16, State: 1.
TDSSNIClient initialization failed with error 0x2740, status code 0xa.
Error: 17182, Severity: 16, State: 1.
TDSSNIClient initialization failed with error 0x2740, status code 0x1.
Error: 17826, Severity: 18, State: 3.

– This error occurs, if the TCP port which SQL is listening is on is already being used by some other process. You need to find the process which is using this port or change SQL Server TCP port to some thing else which is available to use.

The request failed or the service didn’t respond in a timely fashion.Consult the event log or other applicable error logs for details.
Could not open error log file ‘C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG’. Operating system error = 5(failed to retrieve text for this error. Reason: 1815)

– Operating system error = 5 means access denied. Grant full control to the SQL Server service account Microsoft SQL Server folder where you have your SQL Server binaries, database files and Errorlog files and all sub-folders.

Error: 17113, Severity: 16, State: 1.
Error 2(The system cannot find the file specified.) occurred while opening file ‘C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf’ to obtain configuration information at startup. An invalid startup option might have caused the error. Verify your startup options, and correct or remove them if necessary.

– Above error occurs if master.mdf file is not found in the location mentioned or if SQL Server does not have permission to access this file, so make sure the master.mdf file exists in that path and Full permissions are granted to SQL Server service account.

Error: 17204, Severity: 16, State: 1.
FCB::Open failed: Could not open file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf for file number 2. OS error: 32(error not found).

– This error occurs if the mastlog.ldf file is not accessible by the SQL Server process, possibly because this file is used by some other process.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.


Leave a Reply

Your email address will not be published. Required fields are marked *