January 12, 2009 at 11:42 am
We have one server that keeps displaying this error message in the errorlog:
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 error is immediately followed by this message:
2009-01-08 19:31:04.41 spid13s Server local connection provider has successfully re-established listening on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
Anyone know why this might be occuring? It's happening on a regular basis.
It's SQL Server Standard Edition v9.00.3152 with full text indexing enabled on some of the databases.
Thanks,
John
January 12, 2009 at 2:58 pm
Any error in Windows event viewer logs?
MJ
January 12, 2009 at 10:22 pm
John (1/12/2009)
We have one server that keeps displaying this error message in the errorlog: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 error is immediately followed by this message:
2009-01-08 19:31:04.41 spid13s Server local connection provider has successfully re-established listening on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
Anyone know why this might be occuring? It's happening on a regular basis.
It's SQL Server Standard Edition v9.00.3152 with full text indexing enabled on some of the databases.
Thanks,
John
Please enable namedpipe protocol from configuration.
January 13, 2009 at 7:08 am
When I go to Surface Area Config and look at Services and Connections -> Remote Connections I see that Local and Remote Connections for both TCP/IP and Named Pipes is selected.
When I go to cliconfg under General, I see that all protocols are under the "disabled" box, but I checked our other servers and they're all like that and this is the only server giving me the issue.
The protocol isn't permanantly disabled, it seems as though it stops working for like a second then re-connects and stays like that for a while.
I looked in the event log for that time period and saw nothing but I did see an entry a little later (next day) in the Application Log which looks like it was for the same error:
1/10/09 @ 7:30:34 AM
EventID: 26050
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.
This was followed by a bunch of Sharepoint errors saying that it can't connect to the database.
John
January 15, 2009 at 11:16 pm
John (1/13/2009)
When I go to Surface Area Config and look at Services and Connections -> Remote Connections I see that Local and Remote Connections for both TCP/IP and Named Pipes is selected.When I go to cliconfg under General, I see that all protocols are under the "disabled" box, but I checked our other servers and they're all like that and this is the only server giving me the issue.
The protocol isn't permanantly disabled, it seems as though it stops working for like a second then re-connects and stays like that for a while.
I looked in the event log for that time period and saw nothing but I did see an entry a little later (next day) in the Application Log which looks like it was for the same error:
1/10/09 @ 7:30:34 AM
EventID: 26050
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.
This was followed by a bunch of Sharepoint errors saying that it can't connect to the database.
John
Please enable it from SQL server configuration manager, it will not disable again..
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply