On Tuesday our Monitoring Tool sent out this notification about a SQL Server 2005 instance.
Error: 26050, Severity: 17, State: 1. Server local connection provider has stopped listening on [ \\.\pipe\SQLLocal\MSSQLSERVER ] due to a failure. Error: 0xe8, state: 4. The server will automatically attempt to re-establish listening.
The instance was running fine but this error message was logged in the SQL Server Error log. Even Named Pipes protocol was enabled since I was able to connect to the instance using Named Pipes. Like SQL Server mentioned in the above error message, it automatically re-established and was listening on Named Pipes within a few seconds.
Server local connection provider has successfully re-established listening on [ \\.\pipe\SQLLocal\MSSQLSERVER ]
Why did this error occur?
When a connection is attempted using Named Pipes a pipe is created by SQL Server and it is then enabled to accept the client connections. The error code 0xe8 means The pipe is being closed. In this case the client attempted to connect using the Named Pipes. Hence a Pipe was created. But the client closed the connection before the pipe was ready for accepting new client connections. Hence SQL Server stopped listening on Named Pipes.
This error was a one time occurrence in this case. If this message appears in the SQL Server Error Log often, then a SQL Server Trace can be used to find out which application is causing these errors.