October 9, 2008 at 4:04 pm
I am occasionally seeing the following error on two of our SQL 2005 64bit servers. (build 9.0.3239)
[font="Courier New"]"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."[/font]
The "automatic re-establish" works within a minute and the servers seem to continue to function correctly, but I'm still interested in knowing what's causing the error.
There isn't anything in the server Event logs and there is minimal load on the server at the time.
Anyone seen anything like this before? I've had a look on the web but can't see much about it.
Cheers
November 16, 2008 at 8:48 pm
I'm seeing the same issues. Anyone know what might cause this?
SQL Ver 9.0.3186
December 29, 2008 at 2:44 pm
I am having the same problem. Please let me know, why it is happening.
December 29, 2008 at 10:03 pm
Spicoli (10/9/2008)
I am occasionally seeing the following error on two of our SQL 2005 64bit servers. (build 9.0.3239)[font="Courier New"]"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."[/font]
The "automatic re-establish" works within a minute and the servers seem to continue to function correctly, but I'm still interested in knowing what's causing the error.
There isn't anything in the server Event logs and there is minimal load on the server at the time.
Anyone seen anything like this before? I've had a look on the web but can't see much about it.
Cheers
Please enable named piped protcol in sql server.
April 2, 2009 at 12:50 pm
Paresh,
I am recieving the same erroe as stated above. The solution you've suggested is to enable 'named pipes' in the config manager. I have crosschecked that the 'named pipes' is already enabled on the server that keeps sending out the error, ie., "Error: 0xe8, state: 4". Any suggestions ?
Thanks,
SP
April 2, 2009 at 1:17 pm
Do you see any issue with this behavior? It looks like a client made a NP connection to the server after the Pipe is created, but before it's ready to accept connection. When we try to setup things to accept connection, we could re-active the existing client connection and thing would be OK. However, looks like in your case, client closed the connection before everything is ready and we logged this error. The server is robust to create another pipe to accept new connections after this. You can verify if this is the case by using Netmon to see how the NP connection is opened/closed.
The above is the correct answer it is related to Named Pipe being used before it is ready to accept connection. Check the link below for details.
http://blogs.msdn.com/sql_protocols/archive/2005/12/22/506607.aspx
Kind regards,
Gift Peddie
April 2, 2009 at 1:47 pm
Thanks for the prompt reply.
Is there anyway this problem can be avoided / fixed ?
April 2, 2009 at 2:00 pm
You could enable Named Pipes and TCP/IP which is what I do but you also have the option to use NetMon to see how your Named Pipes are opened and closed per that text I posted.
http://blogs.technet.com/netmon/
Kind regards,
Gift Peddie
March 21, 2013 at 9:19 am
Can you tell me where to find this entry in SMS ?
"Please enable named piped protcol in sql server."
Thanks
Jim
March 21, 2013 at 9:39 am
JC-3113 (3/21/2013)
Can you tell me where to find this entry in SMS ?"Please enable named piped protcol in sql server."
Thanks
Jim
The protocols are not in SMS but in Configuration manager under Network Configuration then Protocols. I am only running SQL Server 2012 so I am assuming it is the same in 2005.
Kind regards,
Gift Peddie
March 21, 2013 at 10:12 am
Thanks Gift Peddie
Mine are enabled, so must be another issue
Jim
March 22, 2013 at 12:46 pm
JC-3113 (3/21/2013)
Thanks Gift PeddieMine are enabled, so must be another issue
Jim
But 2005 also comes with surface area configuration tool check for remote connection and both Named Pipes and TCP/IP are enabled in the surface area configuration tool. If the problem continues then go to the links I posted and read up on the many known issues and other ways to fix it.
Kind regards,
Gift Peddie
March 22, 2013 at 1:01 pm
Hi Gift Peddie
parameters are all okay
This databases are on a Virtual server and the admin made some changes last Thu
Have been having issues ever since so I am not sure just what he did
also seeing these types of msgs:
[382] Logon to server '(local)' failed (ConnUpdateStartExecutionDate)
[165] ODBC Error: 0, Unable to complete login process due to delay in opening server connection [SQLSTATE 08001]
[298] SQLServer Error: 258, Shared Memory Provider: Timeout error [258]. [SQLSTATE 08001]
so I am not sure just what he did at this time
will have to do some more investigating
appreciate your time and expertise
Jim
March 22, 2013 at 1:40 pm
JC-3113 (3/22/2013)
Hi Gift Peddieparameters are all okay
This databases are on a Virtual server and the admin made some changes last Thu
Have been having issues ever since so I am not sure just what he did
also seeing these types of msgs:
[382] Logon to server '(local)' failed (ConnUpdateStartExecutionDate)
[165] ODBC Error: 0, Unable to complete login process due to delay in opening server connection [SQLSTATE 08001]
[298] SQLServer Error: 258, Shared Memory Provider: Timeout error [258]. [SQLSTATE 08001]
so I am not sure just what he did at this time
will have to do some more investigating
appreciate your time and expertise
Jim
Then the changes could be the reasons for your problem, if the server is not busy see if you can stop and restart both the server and SQL Server.
Kind regards,
Gift Peddie
March 25, 2013 at 9:40 am
Hi Gift Peddie
unable to do until Thursday night as that is when maint is.
Jim
Viewing 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply