Problem

After a Sql Server restart, the service failed to start giving the following error messages:

 

Error: 26049, Severity: 16, State: 1.

Server local connection provider failed to listen on [ \\.\pipe\SQLLocal\MSSQLSERVER ]. Error: 0x5

Error: 17182, Severity: 16, State: 1.

TDSSNIClient initialization failed with error 0x5, status code 0x40. Reason: Unable to initialize the Shared Memory listener. Access is denied.

Error: 17182, Severity: 16, State: 1.

TDSSNIClient initialization failed with error 0x5, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Access is denied.

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.

 

Solution

When the SQL Server starts it tries to open listening named-pipes to accept client share memory or named-pipe connections. If the listening named-pipes are not closed properly during the last shutdown of SQL Server (maybe after a forced kill of the SQL Server process), there will be orphan named-pipe handles in the windows kernel file system.

To solve this issue, a quick solution will be to reboot the machine hosting the SQL Server.

 


No feedback yet

Leave a comment


Your email address will not be revealed on this site.
(Line breaks become <br />)
(For my next comment on this site)
(Allow users to contact me through a message form -- Your email will not be revealed!)