GlennCameron
asked on
SQL Server: An existing connection was forcibly closed by the remote host
I am getting the following error when using our product that connects to SQL. It is pretty random and I have diffuculty reproducing it.
The error is:
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.
I have noticed that it is a generic TCP error and that people have replaced switch etc with no resolution. I have also tried the SynAttackProtect registry key also which did not resolve the issue.
Machines are all Windows 2003 SP2 and its Microsoft SQL Server Standard Edition (9.00.1399.06)
The error is:
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.
I have noticed that it is a generic TCP error and that people have replaced switch etc with no resolution. I have also tried the SynAttackProtect registry key also which did not resolve the issue.
Machines are all Windows 2003 SP2 and its Microsoft SQL Server Standard Edition (9.00.1399.06)
ASKER
OK, got SP2 installed and I am still recieving errors. My build number is now 9.0.3042. I can not find any other updates to bring the build number up to 3054
You need hotfix KB934458 to get to 9.0.3054:
http://support.microsoft.com/kb/934458/
Hope this helps ...
http://support.microsoft.com/kb/934458/
Hope this helps ...
ASKER
Thanks for that, I am now running 9.0.3054, however the error continues to happen.
From any specific machine or just any ?
Also from the server itself ?
Any messages in the eventviewer on hardware level ?
Also from the server itself ?
Any messages in the eventviewer on hardware level ?
ASKER
Nope no errors in the logs on either the SQL server or the application machine.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I am getting it on more the one SQL server and client with it now which points more at my Cisco Catalyst 2924-XL switches. Can you help me diagnose issues with the switches?
Sorry, I'm only a simple database guy ... switches are not my area of expertise ...
ASKER
Thanks for you reply. I think found my last issue. The port groupings were missing off the ports I had my crossovers cable on.
Glad I could be of any help and thanks for the grade !
Next to that, it might have something to do with the number of concurrent connections. Is that set to a maximum or 0 ? To check: right click on the server in the object explorer pane of SSMS, choose properties. Then select the connections page and see for the 'Maximum number of concurrent connections' ... should say 0 meaning unlimited. That is if you have that kind of license ...
Hope this helps ...