An existing connection was forcibly closed by the remote host.

Question

An existing connection was forcibly closed by the remote host.

Viewing 12 posts - 16 through 26 (of 26 total)

You must be logged in to reply to this topic. Login to reply

Carl Federl One Orange Chip Points: 25384 More actions · Answer 1

MS has added some "Denial of service attacks" protection (SynAttackProtect setting), which can cause this message. See "Troubleshooting: Connection Forcibly Closed" at http://msdn.microsoft.com/en-us/library/ms187005.aspx

Also see "Avoiding TCP/IP Port Exhaustion" at http://msdn.microsoft.com/en-us/library/aa560610(BTS.20).aspx

SQL = Scarcely Qualifies as a Language

Jack Corbett SSC Guru Points: 184394 More actions · Answer 2

Lynn Pettis (3/11/2010)
Jack Corbett (3/11/2010)
Do you have your network and sever admins involved as well? It doesn't seem to me to be a SQL Server issue.
I'm not sure that you'd get anything from the trace since it is a connection being closed and you don't really get any events when that happens. You'd want the queries happening so RPC:Starting & Completed, T-SQL:BatchStarting & Completed - I say starting and completed in case it's happening mid-query. I'd also do Errors and Warnings:Exception because made you are getting one and it isn't getting back to the client.
That's all I've got to offer. I'll be interested to hear more.
If you knew our network people you'd understand why I am looking at the SQL side first. I'll have to prove it isn't SQL before we get any real support.

Been there, done that!

Good information shared by Carl though.

Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question

GTR SSCrazy Eights Points: 8007 More actions · Answer 3

I may missed here something in previous postings, Is TCP\IP, Named Pipes Enabled in SQL server network configuration (Not on SQL server native service configuration)

EnjoY!

GTR SSCrazy Eights Points: 8007 More actions · Answer 4

Carl Federl (3/11/2010)
MS has added some "Denial of service attacks" protection (SynAttackProtect setting), which can cause this message. See "Troubleshooting: Connection Forcibly Closed" at http://msdn.microsoft.com/en-us/library/ms187005.aspx
Also see "Avoiding TCP/IP Port Exhaustion" at http://msdn.microsoft.com/en-us/library/aa560610(BTS.20).aspx

If that is the case, i would get with Microsoft support first before i make any registry changes.

EnjoY!

Lynn Pettis SSC Guru Points: 442467 More actions · Answer 5

GTR (3/11/2010)
I may missed here something in previous postings, Is TCP\IP, Named Pipes Enabled in SQL server network configuration (Not on SQL server native service configuration)

We are using TCP for the connectivity to connect to the database servers from the application servers.

Lynn Pettis SSC Guru Points: 442467 More actions · Answer 6

GTR (3/11/2010)
Carl Federl (3/11/2010)
MS has added some "Denial of service attacks" protection (SynAttackProtect setting), which can cause this message. See "Troubleshooting: Connection Forcibly Closed" at http://msdn.microsoft.com/en-us/library/ms187005.aspx
Also see "Avoiding TCP/IP Port Exhaustion" at http://msdn.microsoft.com/en-us/library/aa560610(BTS.20).aspx
If that is the case, i would get with Microsoft support first before i make any registry changes.

If any changes need to be made regarding DoS, tha will be done by Network Services, they are responsible for the OS and network conectivity. I am only responsible for SQL Server.

smile_netz Ten Centuries Points: 1018 More actions · Answer 7

Hi Lynne,

We are also encountering the exact same error you have posted. Can you please tell me what you did in order to solve this problem?

We will be implementing the TCP Offloading but from what I understand, this didn't solve your problem?

Thanks.

Minaz Amin SSChampion Points: 11052 More actions · Answer 8

Hi Lynne,

Any update, did it solve the issue?

"More Green More Oxygen !! Plant a tree today"

Lynn Pettis SSC Guru Points: 442467 More actions · Answer 9

The problem was resolved, but I never got an answer to as to what was done. No longer with this employer so not sure if they would even remember that long ago.

mssqlsrv SSCrazy Points: 2375 More actions · Answer 10

:crazy:

Getting same error since last 2 days.

OS: windows server 2008 R2

SQL : Sql server 2008 R2.

Tried TCP IP Chimney option but still getting the same error.

any Solution Guys ????

david.vandiver Valued Member Points: 59 More actions · Answer 11

We have recently moved to new hardware and have a similar message. Did you have a solution that worked when this happened in 2010?

Our message is:

File: E:\pt85012b-retail\peopletools\SRC\pssys\gensql.cppSQL error. Stmt #: 900 Error Position: 0 Return: 8200 - [Microsoft][SQL Server Native Client 10.0]TCP Provider: An existing connection was forcibly closed by the remote host.

Thanks

David Vandiver

Lynn Pettis SSC Guru Points: 442467 More actions · Answer 12

david.vandiver (7/9/2014)
We have recently moved to new hardware and have a similar message. Did you have a solution that worked when this happened in 2010?
Our message is:
File: E:\pt85012b-retail\peopletools\SRC\pssys\gensql.cppSQL error. Stmt #: 900 Error Position: 0 Return: 8200 - [Microsoft][SQL Server Native Client 10.0]TCP Provider: An existing connection was forcibly closed by the remote host.
Thanks
David Vandiver

As I mentioned a couple of years ago, the Network Services group never supplied me with an explanation regarding what was done to correct the issue so I was never able to provide any real follow-up here. I haven't been with that organization now for nearly 4 years and I doubt if they remember what they did.