Answered by:
"Protocol error in TDS stream"

Question
-
Was running Windows 2003 SP1 on the server having this issue. The package will run fine from my workstation, but when I execute it on the database server itself I'm getting:
Started: 3:20:22 AM
Error: 2010-08-27 03:26:49.49
Code: 0xC0202009
Source: Build Perform import files PortiaPerformHoldings [1]
Description: An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Protocol error in TDS stream".
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure".
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "TCP Provider: An existing connection was forcibly closed by the remote host.
".
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure".
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "TCP Provider: An existing connection was forcibly closed by the remote host.
".
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure".
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "TCP Provider: An existing connection was forcibly closed by the remote host.
".
End Error
Error: 2010-08-27 03:26:49.49
Code: 0xC0202009
Source: Build Perform import files PortiaPerformSecurity [112]
Description: An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Protocol error in TDS stream".
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure".
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "TCP Provider: An existing connection was forcibly closed by the remote host.
".
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure".
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "TCP Provider: An existing connection was forcibly closed by the remote host.
".
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure".
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "TCP Provider: An existing connection was forcibly closed by the remote host.
".
End Error
I've disabled the TCP chimney feature and I'm still getting this error. Like I said, running the data flow task on my machine works just fine. The one thing I did change was adding the /PAE switch on the windows 2003 server but did not add the /3GB switch which some say could be the issue. Any suggestions folks might have would be much appreciated.
Friday, August 27, 2010 12:02 PM
Answers
-
this is not a SSIS error.
this is network issue. Please check your firewall setting or ntk load.
Let us TRY this |
http://quest4gen.blogspot.com/- Marked as answer by Jinchun ChenMicrosoft employee Tuesday, September 7, 2010 4:00 AM
Friday, August 27, 2010 12:09 PM -
Hi duhaas,
Another possible reason for this issue is SNP features(TCP Offload, RSS) is enabled on the NIC.
Please try following the following articles to disable TCP Offload and RSS to check if the issue is solved:
http://support.microsoft.com/kb/951037
http://support.microsoft.com/kb/948496If you have any more questions, please feel free to ask.
Thanks,
Jin Chen
Jin Chen - MSFT- Marked as answer by Jinchun ChenMicrosoft employee Tuesday, September 7, 2010 4:00 AM
Monday, August 30, 2010 6:41 AM
All replies
-
this is not a SSIS error.
this is network issue. Please check your firewall setting or ntk load.
Let us TRY this |
http://quest4gen.blogspot.com/- Marked as answer by Jinchun ChenMicrosoft employee Tuesday, September 7, 2010 4:00 AM
Friday, August 27, 2010 12:09 PM -
Hi duhaas,
Another possible reason for this issue is SNP features(TCP Offload, RSS) is enabled on the NIC.
Please try following the following articles to disable TCP Offload and RSS to check if the issue is solved:
http://support.microsoft.com/kb/951037
http://support.microsoft.com/kb/948496If you have any more questions, please feel free to ask.
Thanks,
Jin Chen
Jin Chen - MSFT- Marked as answer by Jinchun ChenMicrosoft employee Tuesday, September 7, 2010 4:00 AM
Monday, August 30, 2010 6:41 AM