Hello, We currently have two SSIS packages that experience the same type of errors. Both packages pull from SQL Server and write to another database on SQL Server. The SQL Version is SQL 2008 SP2 pulling from SQL 2005 SP4. Here is the summary of the error message: Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Protocol error in TDS stream". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Protocol error in TDS stream". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Communication link failure". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "TCP Provider: An existing connection was forcibly closed by the remote host. ". End Error Error: 2011-07-25 02:16:35.72 Code: 0xC0047038 Source: Load Visit Tx SSIS.Pipeline Description: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on component "ResidentVistTx Source" (1) returned error code 0xC0202009. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 2:00:01 AM Finished: 2:16:35 AM Elapsed: 994.756 seconds. The package execution failed. The step failed. Looking at the first line "Protocol Error in TDS Stream" seems to point to some issue with the network. We are pulling the data over WAN. I was wondering if anyone has had the same issue and are there any white papers or such on network latency/configuration for SSIS over WAN. Thank you in advance for your help. Oliver

This might give you some guide lines http://social.msdn.microsoft.com/Forums/en/sqlintegrationservices/thread/315f0ba7-cfa5-48d8-978a-b7ec00c85388http://uk.linkedin.com/in/ramjaddu

Hi SQLPrivateer, Based on the error message you have provided, the issue might occur if TCP Offloading feature is enabled on Windows Server 2003 SQL server with SP2 applied. Please try following steps to disabled TCP Offloading on the server. To do this, a. Logon the SQL servers, click Start, click Run, type regedit, and then click OK. b. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters c. If the EnableRSS registry entry does not exist, create it. To do this, follow these steps: - On the Edit menu, point to New, and then click DWORD Value. - In the New Value #1 box, type EnableRSS , and then press ENTER. d. Right-click EnableRSS, and then click Modify. e. In the Value data box, type 0 (zero), and then click OK. Please take the above steps and disable the following registry key as well: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters EnableTCPA REG_DWORD 0x0 EnableTCPChimney REG_DWORD 0x0 Note: The new configuration does not take effect until you restart the server. For more information, please refer to the following article, Some problems occur after installing Windows Server 2003 SP2: http://support.microsoft.com/kb/945977 SSIS package fails with Protocol error in TDS stream: http://blogs.msdn.com/b/ramoji/archive/2009/12/30/protocol-error-in-tds-stream.aspx If you have any question, please feel free to ask. Thanks, Eileen