February 15, 2010 at 2:36 am
Hi,
We have SQL server 2008 and using clustering environment with 2 nodes. One .net application connects to this server. But sometimes we get the below error from the application log.
System.Data.SqlClient.SqlException: 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 checked the windows and system event logs and sql server error logs, but I didnt find any logs during that time.
Do you have any idea how to check and troubleshoot this issue.
Ryan
//All our dreams can come true, if we have the courage to pursue them//
March 3, 2010 at 12:29 am
Sumanta-1056020 (2/15/2010)
Hi,We have SQL server 2008 and using clustering environment with 2 nodes. One .net application connects to this server. But sometimes we get the below error from the application log.
System.Data.SqlClient.SqlException: 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 checked the windows and system event logs and sql server error logs, but I didnt find any logs during that time.
Do you have any idea how to check and troubleshoot this issue.
there may be n number of reasons for the same, but first thing comes in mind is:
try changing the timeout limit for remote connections to 0 which is unlimited and then test, this should resolve the issue.
otherwise, if this is a named instance start the browser service, check TCP IP \ Named pipe Protocol, PORT on which SQL running.
Regards,
Sarabpreet Singh 😎
Sarabpreet.com
SQLChamp.com
Twitter: @Sarab_SQLGeek
March 19, 2010 at 11:19 am
Sounds like a memory pressure issue to me.
Have a look at the amount of free VAS (Virtual Address Space).
http://www.eraofdata.com/blog/tag/vas/
Also look at dbcc memorystatus complicated you will need the link below.
http://support.microsoft.com/kb/907877
Thanks
Chris
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply