May 2, 2011 at 4:08 am
Hello all,
sometimes scheduled stored procedures cancel without error message. Executing the script directly on the server in Management Studio sometimes result in the following error message:
Msg 121, Level 20, State 0, Line 0
A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.)
I have found the following the msdn article http://blogs.msdn.com/b/mssqlisv/archive/2008/05/27/sql-server-intermittent-connectivity-issue.aspx
in the post http://www.sqlservercentral.com/Forums/Topic569962-146-4.aspx.
After disabling synattck protect and tcp chumney offload the error still happens randomly.
Anyone an idea why this error can still occur?
May 3, 2011 at 6:55 am
How about this kb?
May 3, 2011 at 7:21 am
You'll get the same error if the server is restarted or if someone killed your SPID.
I've never hit a bug with this, but I'd certainly check the KB posted earlier.
Are you up to date in the SPs on your server?
May 3, 2011 at 11:28 pm
Ninja's_RGR'us (5/3/2011)
You'll get the same error if the server is restarted or if someone killed your SPID.
hello Ninja,
I always respect your words but the Error msg we recieve for the above situation is somewhat different. it is like this ..
Msg 233, Level 20, State 0, Line 0
A transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)
yes, it is also a trasport layer error because the connection with the server has got disconnected but it is somewhat different.
Hi david,
Can you look on this link, without knowing much about the N/W configuration i will not be able to comment much because it does not seems to me an sql server specific issue because as you said it got randomly disconnected so pls check the below link out...
Regards,
Sachin
May 4, 2011 at 5:41 am
sachnam (5/3/2011)
Ninja's_RGR'us (5/3/2011)
You'll get the same error if the server is restarted or if someone killed your SPID.hello Ninja,
I always respect your words but the Error msg we recieve for the above situation is somewhat different. it is like this ..
Msg 233, Level 20, State 0, Line 0
A transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)
yes, it is also a trasport layer error because the connection with the server has got disconnected but it is somewhat different.
Hi david,
Can you look on this link, without knowing much about the N/W configuration i will not be able to comment much because it does not seems to me an sql server specific issue because as you said it got randomly disconnected so pls check the below link out...
Regards,
Sachin
Thanks for the info. You're always welcome to interrupt me when I make a mistake :hehe:.
May 6, 2011 at 7:41 am
Thanks for the advice, our server administrar has chosen to insert a new network card, let's if it helps.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply