An existing connection was forcibly closed by the remote host.

[salonen]

I've seen this message a lot in the groups but I haven't found a
solution for it yet.

Our setup is SQL Server 2000 on a Windows Server 2003 cluster. I
don't believe this issue happened as often when the OS was Server 2000
but that was before I started here.

We see this quite a bit from our wireless clients:
Errors=System.Data.SqlClient.SqlErrorCollection
Class=20 (0x14)
LineNumber=0 (0x0)
Number=10054 (0x2746)
Server=OurSQLServer
State=0 (0x0)
ErrorCode=-2146232060 (0x80131904)
Message=A transport-level error has occurred when sending the request
to the server. (provider: TCP Provider, error: 0 - An existing
connection was forcibly closed by the remote host.)
Data=System.Collections.ListDictionaryInternal

I initially thought it had something to do with them losing the
network connection but when I was trying to recreate (killing the
wireless connection during a long running process) that I always got
the following details:
Errors=System.Data.SqlClient.SqlErrorCollection
Class=20 (0x14)
LineNumber=0 (0x0)
Number=64 (0x40)
Server=OurSQLServer
State=0 (0x0)
ErrorCode=-2146232060 (0x80131904)
Message=A transport-level error has occurred when receiving results
from the server. (provider: TCP Provider, error: 0 - The specified
network name is no longer available.)
Data=System.Collections.ListDictionaryInternal

To recreate the original, all you have to do is run the KILL command
on the spids associated with your application from Query Analyzer.
Given this, I'm focusing on the server itself causing the errors and
not the client computers.

So now we have something to go on when we attempt to code around the
issue. I've been able to "soothe" the issue by executing
SqlConnection.ClearAllPools() when we see a SqlException with a
severity level of 20 or higher. However, I'd like to know if there's
a setup issue with my SQL Server box that I could change that would at
least lessen the frequency of these errors.

Thanks in advance for any advice,
Austin

 

[carol beaney]

hi, this is a long shot but do you have a fix for this? my setup is very
similar to yours. I'm running sql server 2000 and asp.net 2. my host has
recently changed servers and since then, I have been inondated with
A transport-level error has occurred when sending the request
to the server. (provider: TCP Provider, error: 0 - An existing
connection was forcibly closed by the remote host.)
and
A transport-level error has occurred when receiving results
from the server. (provider: TCP Provider, error: 0 - The specified
network name is no longer available.)
The hosting company aren't being very helpful though I'm convinced it's a
server issue rather than application issue. The call stack is always when it
is accessing the Profile object, too, according to my error log.

Any info would be greatly appreciated!

Thanks,

Carol.

url:http://www.ureader.com/msg/14165695.aspx

 

[William \(Bill\) Vaughn]

In the olden days we would see this when the server is configured for 50
connections and someone tried to connect for the 51st time. The connection
is initially made, but the server finds that its own limit was exceeded and
it closes it (from the server end). Make sense? Consider that DBAs do all
kinds of things that limit the impact on the server. This can also be
restricted by license.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)