August 6, 2007 at 1:38 pm
Dear subscribers,
Background: A previously working and unchanged SSIS package loading a moderate amount of data to a remote instance of SS2005 is now failing shortly after invocation with a message about the connection being "forcibly closed".
Hoping someone can confirm a similar experience and resolution or perhaps debunk the following cause/resolution which was suggested by another resource...
4.1.2 Connections May Be Forcibly Closed When Running on Windows Server 2003 SP1
<script type=text/javascript>loadTOCNode(2, 'moreinformation');</script>Client connections to an instance of the SQL Server Database Engine running on Windows Server 2003 Service Pack 1 might fail with the following error: "ProviderNum: 7, Error: 10054, ErrorMessage: "TCP Provider: An existing connection was forcibly closed by the remote host"." This can occur when you are testing scalability with a large number of client connection attempts. To resolve this issue, use the regedit.exe utility to add a new DWORD value named SynAttackProtect to the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\with value data of 00000000.
Note Setting this registry key can expose the server to a SYN flood denial-of-service attack. Remove this registry value when testing is complete.
Any and all responses are greatly appreciated.
TIA. Chris.
August 7, 2007 at 1:31 am
Interesting. I cannot see how the error is actually related to your SSIS package though. When SSIS runs, it does not hold many connections open. Only as many as there are connection managers. The above seems to do with DoS attacks which would be rather high.
Are there any clues in event log for SQL?
Cheers,CrispinI can't die, there are too many people who still have to meet me!It's not a bug, SQL just misunderstood me!
August 8, 2007 at 9:59 am
Perhaps another process is making the connections?
RandyHelpdesk: Perhaps Im not the only one that does not know what you are doing. 😉
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply