June 18, 2007 at 10:29 pm
June 18, 2007 at 10:40 pm
I hope connection pooling is enabled. Can you try disabling that and see if the error occurs. Connection pooling might have been enabled for reasons so check before you disable the same.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
June 19, 2007 at 11:44 am
Sugesh,
Client configuration hasn't changed. It was working fine for quite a while. i have found article suggesting that SQL Server might generate this error while having many concurrent connections:
http://support.microsoft.com/kb/937745
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply