2

We have started seeing the following errors appearing intermittently (between 1 and 5 a day on average) in the error logs on one of our SQL 2016 servers:

Error: 26050, Severity: 17, State: 1. Server local connection provider has stopped listening on [ \.\pipe\SQLLocal\SQL16 ] due to a failure. Error: 0xe8, state: 4. The server will automatically attempt to re-establish listening.

These are followed a few seconds later by:

Server local connection provider has successfully re-established listening on [ \.\pipe\SQLLocal\SQL16 ].

(SQL16 is the instance name of this server).

We do not appear to be getting any errors from the applications that use this server at the same time and as far as I am aware "\.\pipe\SQLLocal\SQL16" is used by the Shared Memory protocol, which would indicate this was something that would only affect connections coming from the local server.

This server is part of an Availability Group and is the primary replica. The databases are also log-shipped to a third server. I have tried to look at any errors from Agent jobs etc. but cannot see anything obvious that ties in with the times we see these errors logged.

I am just curious as to what might cause these messages, as I have never seen them on any other servers.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.