Protocol Error in TDS Stream

"Protocol error in TDS stream"
SQL Server
>
SQL Server Integration Services
Question
0
Sign in to vote
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".
"Communication link failure".
"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.
"Protocol error in TDS stream".
".
".
".
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

Reply
|
Quote
duhaas
10 Points
Answers
0
Sign in to vote
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, Moderator Tuesday, September 07,
2010 4:00 AM
Reply
|
Quote
ETL vs ELTL
(Partner)
10,660 Points
0
Sign in to vote
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
If you have any more questions, please feel free to ask.
Thanks,
Jin Chen
Jin Chen - MSFT

2010 4:00 AM
Monday, August 30, 2010 6:41 AM
Reply
|
Quote
Jinchun Chen
Microsoft
(MSFT)
28,433 Points
Moderator
All replies
0
Sign in to vote
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/
2010 4:00 AM
Reply
|
Quote
ETL vs ELTL
(Partner)
10,660 Points
0
Sign in to vote
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:
If you have any more questions, please feel free to ask.
Thanks,
Jin Chen
Jin Chen - MSFT

o

2010 4:00 AM
Monday, August 30, 2010 6:41 AM

Reply
|
Quote
Manage my account
Ask the community
Contact Answer Desk
Find downloads
Information about the TCP Chimney Offload, Receive Side Scaling, and Network Direct Memory
Access features in Windows Server 2008
Email
Print
Not sure if this is the right fix? We've added this issue to our memory dump
diagnostic which can confirm.
INTRODUCTION
This article describes the TCP Chimney Offload, Receive Side Scaling (RSS), and Network
Direct Memory Access (NetDMA) features that are available for the TCP/IP protocol in
Windows Server 2008.
More information
TCP Chimney Offload overview
TCP Chimney Offload is a networking technology that helps transfer the workload from the
CPU to a network adapter during network data transfer. In Windows Server 2008, TCP
Chimney Offload enables the Windows networking subsystem to offload the processing of
a TCP/IP connection to a network adapter that includes special support for TCP/IP offload
processing.
TCP Chimney Offload is available in all versions of Windows Server 2008 and Windows
Vista. Both TCP/IPv4 connections and TCP/IPv6 connections can be offloaded if the
network adapter supports this feature.
How to enable and disable TCP Chimney Offload in Windows Server 2008
TCP Chimney Offload can be enabled or disabled in the following two locations:
The operating system
The advanced properties page of the network adapter

TCP Chimney Offload will work only if it is enabled in both locations. By default, TCP
Chimney Offload is disabled in both these locations. However, OEM installations may
enable TCP Chimney Offload in the operating system, in the network adapter, or in both
the operating system and the network adapter.
How to configure TCP Chimney Offload in the operating system
To enable TCP Chimney Offload, follow these steps:
a.
Use administrative credentials to open a command prompt.
b.
At the command prompt, type the following command, and then press
ENTER:
netsh int tcp set global chimney=enabled
To disable TCP Chimney Offload, follow these steps:
a.
b.
ENTER:
netsh int tcp set global chimney=disabled
To determine the current status of TCP Chimney Offload, follow these steps:
a.
b.
ENTER:
netsh int tcp show global
How to configure TCP Chimney Offload on the network adapter
To enable or disable TCP Chimney Offload, follow these steps:
a.
Open Device Manager.
b.
Under Network Adapters, double-click the network adapter that you want.
c.
On the Advanced tab, click Enabled or Disabled in the box next to the TCP
offload entry.
Note Different manufacturers may use different terms to describe TCP Chimney Offload
on the Advancedproperties page of the network adapter.
How TCP Chimney Offload coexists with other programs and services
When the TCP Chimney Offload technology offloads TCP/IP processing for a given TCP
connection to a dedicated network adapter, it must coexist with other programs or
services that rely on lower layer services in the networking subsystem. The following table
shows how TCP Chimney Offload coexists with other programs and services.
Program or service
Works
together with
TCP Chimney
Offload
Expected behavior when both the servic

and TCP Chimney Offload are enabled
Windows Firewall
Yes
If the firewall is configured to allow for a give

TCP connection, the TCP/IP stack will offload t
TCP connection to the network adapter.
Third-party firewall
Implementationspecific
Some firewall vendors have decided to

implement their product in such a way that T
Chimney Offload can be used while the firewa
service is running. Refer to the firewall
documentation to find out whether the produ
you are using supports TCP Chimney Offload.
Internet Protocol security

(IPsec) policy
No
If the system has an IPsec policy applied, the

TCP/IP stack will not try to offload any TCP
connections. This lets the IPsec layer inspect
every packet to provide the desired security.
Network Adapter teaming

service (This service is also
known as the Load
Balancing and Failover
service. It is usually
provided by an OEM.)
Some OEMs have decided to implement their

network adapter teaming solutions so that th
coexist with TCP Chimney Offload. See the
network adapter teaming service
documentation to determine whether you can
use TCP Chimney offload together with this
service.
Windows Virtualization
(Hyper-V technology)
No
If you are using the Microsoft Hyper-V

technology to run virtual machines, no
operating system will take advantage of TCP
Chimney offload.
Network monitoring tools,

such as Network Monitor
and Wireshark
Some network monitoring tools may coexist w

TCP Chimney but may not monitor offloaded
connections.
Network Load Balancing

(NLB) service
No
If you configure the NLB service on a server,

TCP/IP stack does not offload TCP connection
Cluster service
Yes
However, note that TCP connections using th

Network Fault Tolerant driver (NetFT.sys) will
be offloaded. NetFT is used for fault-tolerant
inter-node cluster communication.
Network Address
Translation (NAT) service
(also known as the Internet
Connection Sharing service)
No
If this service is installed and running, the TC

stack does not offload connections.
How to determine whether TCP Chimney Offload is working
When TCP Chimney Offload is enabled in the operating system and in the network
adapter, the TCP/IP stack tries to offload suitable TCP connections to the network adapter.
To find out which of the currently established TCP connections on the system are
offloaded, follow these steps:
1.
2.
Type the following command, and then press ENTER:

netstat t
You receive output that resembles the following:
Active Connections
Proto Local Address
Foreign Address
TCP
127.0.0.1:52613
TCP
192.168.1.103:52614
State
computer_name:52614
Offload State
ESTABLISHED
computer_name:52613
InHost
ESTABLISHED
Offloaded
In this output, the second connection is offloaded.

For more information about TCP Chimney offload in Windows Server 2003, click the
following article number to view the article in the Microsoft Knowledge Base:
912222 The Microsoft Windows Server 2003 Scalable Networking Pack release
How to enable and disable RSS in Windows Server 2008
To enable RSS, follow these steps:

1.
2.
At the command prompt, type the following command, and then press ENTER:
netsh int tcp set global rss=enabled
To disable RSS, follow these steps:
1.
2.
netsh int tcp set global rss=disabled
To determine the current status of RSS, follow these steps:
1.
2.
netsh int tcp show global
When you use a command to enable RSS, you receive the following message:
TCP Global Parameters

---------------------------------------------Receive-Side Scaling State : enabled
Note By default, RSS is enabled.

How to enable and disable NetDMA in Windows Server 2008
To have us enable or disable NetDMA for you, go to the "Fix it for me" section. If you
prefer to enable or disable NetDMA yourself, go to the "Let me fix it myself" section.
Fix it for me
To fix this problem automatically, click the Fix it button or link. In the File
Download dialog box, click Run, and then follow the steps in the Fix it Wizard.
Microsoft Fix it
Microsoft Fix it
Notes
To make sure the Enable NetDMA package work, you must enable the NetDMA
functionality. For more information about using NetDMA, click the following link:
http://technet.microsoft.com/en-us/library/gg162716(WS.10).aspx
This wizard may be in English only. However, the automatic fix also works for other
language versions of Windows.
If you are not on the computer that has the problem, save the Fix it solution to a
flash drive or a CD, and then run it on the computer that has the problem.
Then, go to the "Did this fix the problem?" section.
Let me fix it myself
To enable or disable NetDMA, follow these steps:

1.
Click Start, click Run, type regedit, and then click OK.
2.
Locate the following registry subkey, and then click it:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
3.
Double-click the EnableTCPA registry entry.

Note If this registry entry does not exist, right-click Parameters, point to New,
click DWORD Value, typeEnableTCPA, and then press ENTER.
4.
To enable NetDMA, type 1 in the Value data box, and then click OK.
5.
To disable NetDMA, type 0 in the Value data box, and then click OK.
6.
If the EnableTCPA registry entry does not exist, enable the NetDMA functionality.
Did this fix the problem?
Check whether the problem is fixed. If the problem is fixed, you are finished with
this section. If the problem is not fixed, you can contact support.
We would appreciate your feedback. To provide feedback or to report any issues

with this solution, please leave a comment on the "Fix it for me" blog or send us
an email message.
The third-party products that this article discusses are manufactured by companies that
are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about
the performance or reliability of these products.
Properties
Article ID: 951037 - Last Review: 10/09/2014 13:13:00 - Revision: 9.0
Applies to
Windows Web Server 2008
Windows Server 2008 Standard
Windows Server 2008 Enterprise
Windows Server 2008 Datacenter
Windows Server 2008 Standard without Hyper-V
Windows Server 2008 for Itanium-Based Systems
Windows Server 2008 Enterprise without Hyper-V
Windows Server 2008 Datacenter without Hyper-V

Keywords:
kbmdd kbenable kbnetworkmon kbnlb kbnetworkcard kbnetworkconnectivity

kbexpertiseadvanced kbinfo kbhowto kbfixme kbmsifixme KB951037
Update to turn off SNP features for Windows Server 2003 and Windows SBS 2003
Email
Print
Support for Office 2003 has ended

Microsoft ended support for Office 2003 on April 8, 2014. This change has affected your
software updates and security options. Learn what this means for you and how to stay
protected.
Support for Windows Server 2003 will end

on July 14, 2015
Microsoft will end support for Windows Server 2003 on July 14, 2015. This change will
affect your software updates and security options. Learn what this means for you and how
to stay protected.
Not sure if this is the right fix? We've added this issue to our memory dump
diagnostic which can confirm.
Symptoms
After you install Windows Server 2003 Service Pack 2 (SP2) or Windows Server 2003
Scalable Networking Pack (SNP) on a computer that has a TCP/IP Offload-enabled network
adapter, you may experience many network-related problems.
The following issues may occur when Windows Server 2003 SNP is turned on:
When you try to connect to the server by using a VPN connection, you receive the
following error message:
Error 800: Unable to establish connection.
You cannot create a Remote Desktop Protocol (RDP) connection to the server.
You cannot connect to shares on the server from a computer on the local area
network.
You cannot join a client computer to the domain.
You cannot connect to the Exchange server from a computer that is running
Microsoft Outlook.
Inactive Outlook connections to the Exchange server may not be cleaned up.
You experience slow network performance.

You may experience slow network performance when you communicate with a
Windows Vista-based computer.
You cannot create an outgoing FTP connection from the server.
The Dynamic Host Configuration Protocol (DHCP) server service crashes.
You experience slow performance when you log on to the domain.
Network Address Translation (NAT) clients that are located behind Windows Small
Business Server 2003 or Internet Security and Acceleration (ISA) Server experience
intermittent connection failures.
You experience intermittent RPC communications failures.
The server crashes.
The server runs low on nonpaged pool memory

Note SNP features are currently not supported on Itanium-based systems.
Resolution
Update information
This update turns off default SNP features. After you install this hotfix, you can manually
re-enable these features by changing registry values. The following files are available for
download from the Microsoft Download Center:
Download the update for Windows Server 2003, x86-based versions (KB948496)
package now.
Download the update for Windows Server 2003, x64-based versions (KB948496)
package now.
Download the update for Windows Server 2003, Itanium-based versions (KB948496)
package now.
For more information about how to download Microsoft support files, click the following
article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection
software that was available on the date that the file was posted. The file is stored on
security-enhanced servers that help prevent any unauthorized changes to the file.
Prerequisites
You must have Windows Server 2003 Service Pack 2 installed.

Restart requirement
You must restart the computer after you apply this update.
Hotfix replacement information
This update does not replace any other previously released updates.
File information
This update does not replace any files.
Workaround
To work around this problem, use any of the following three methods. You must restart the
computer after you try any of these methods.
Method 1: Manually disable Receive Side Scaling and TCP Offload in the network adapter
driver
To manually disable RSS and TCP Offload in the network adapter driver, follow these
steps:
1.
Click Start, and then click Run.
2.
Type the following command, and then click OK:

ncpa.cpl
3.
Right-click a network adapter object, and then click Properties.
4.
Click Configure, and then click the Advanced tab.
5.
In the Property list, click Receive Side Scaling, click Disable in the Value list,
and then click OK.
6.
In the Property list, click TCP/IP Offload, click Disable in the Value list, and then
click OK.
7.
Repeat steps 2 through 5 for each network adapter object.

Method 2: Update the network adapter drivers
To see whether an updated network adapter driver is available, contact the network
adapter manufacturer or the original equipment manager (OEM) for the computer. The
driver must meet Network Driver Interface Specification (NDIS) 5.2 or a later version of
this specification.
For information about how to contact computer program manufacturers, go to the
following Microsoft website:
http://support.microsoft.com/gp/vendors
Method 3: Manually disable RSS and TCP Offload in the registry
To have us do this for you, go to the "Fix it for me" section. If you would rather do this
yourself, go to the "Let me fix it myself" section.
Fix it for me
To disable RSS and TCP Offload in the registry automatically, click the Fix this
problem link. Then click Run in the File Download dialog box, and follow the steps in
this wizard.
Microsoft Fix it
Note this wizard may be in English only. However, the automatic fix also works for other
language versions of Windows.
Note If you are not on the computer that has the problem, you can save the automatic fix
to a flash drive or to a CD. Then you can run the automatic fix on the computer that has
the problem.
Now go to the "Did this fix the problem?" section.
Let me fix it myself
Important This section, method, or task contains steps that tell you how to modify the
registry. However, serious problems might occur if you modify the registry incorrectly.
Therefore, make sure that you follow these steps carefully. For added protection, back up
the registry before you modify it. Then, you can restore the registry if a problem occurs.
For more information about how to back up and restore the registry, click the following
article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
To manually disable RSS and TCP Offload, follow these steps:

1.
Click Start, click Run.
2.
Type the following command in the Open, and then click OK:
regedit
3.
Locate the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
4.
Right-click EnableTCPChimney, and then click Modify.
5.
In the Value data box, type 0, and then click OK.
6.
Right-click EnableRSS, and then click Modify.
7.
8.
Right-click EnableTCPA, and then click Modify.
9.
10.
Exit Registry Editor, and then restart the computer.
If you set the value of the EnableTCPChimney registry entry to 1, the TCP Chimney
functionality is enabled. Similarly, if you set the values of the EnableRSS and EnableTCPA
registry entries to 1, the RSS functionality and the TCPA functionality are enabled.
Did this fix the problem?

Check whether the problem is fixed. If it is fixed, you are finished with this article. If it is
not fixed, you can contact support. To do this, go to the Microsoft Support for small
business website.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in
the "Applies to" section.
Advanced information
These issues occur because of several problems with the Windows Server 2003 SNP
features that are enabled in Windows Server 2003 Service Pack 2. These features include
Receive Side Scaling (RSS) and TCP/IP Offloading. Specifically, these problems include the
following:
RSS is incompatible with NAT or with Network Load Balancing (NLB).
TCP/IP Offload has a problem with the Window Scaling feature. This problem
typically occurs when you communicate with a Windows Vista-based computer. Windows
Vista uses the Window Scaling feature.
Some TCP/IP Offload-enabled network adapters do not send TCP keep-alive

messages but Exchange servers use TCP keep-alive messages to clean up inactive client
sessions.
The TCP/IP Offload-enabled network adapter may consume lots of nonpaged pool
memory. This may cause other problems in the operating system.
In some cases, the TCP/IP Offload-enabled network adapter may request large
blocks of contiguous memory. This makes the computer crash when it tries to free the
memory.
For more information about software update terminology, click the following article
number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft
software updates
For more information about SNP, click the following article number to view the article in
the Microsoft Knowledge Base:
912222 The Microsoft Windows Server 2003 Scalable Networking Pack release
In rare cases, this hotfix does not work. For example, when you use network adapter
teaming software on the computer, the changes to TCP Chimney and RSS settings are not
picked up by the network adapter teaming software. This causes a loss of network
connectivity. After you apply this hotfix, you must verify the properties of the network
adapter team to make sure that the TCP Chimney or TOE and RSS settings have also been
disabled. If the hotfix cannot disable the TCP Chimney or TOE and RSS feature, you can
manually disable RSS and TCP Chimney Offload by using one of the methods that is
mentioned in the Workaround section.
The third-party products that this article discusses are manufactured by companies that
are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about
the performance or reliability of these products.
Microsoft provides third-party contact information to help you find technical support. This
contact information may change without notice. Microsoft does not guarantee the
accuracy of this third-party contact information.
Properties
Article ID: 948496 - Last Review: 10/09/2014 16:19:00 - Revision: 13.0
Applies to
Microsoft Windows Server 2003 Service Pack 2
Microsoft Office SharePoint Portal Server 2003
Microsoft Office SharePoint Server 2007
Microsoft Windows SharePoint Services 3.0
Microsoft Windows SharePoint Services 2.0
Microsoft Exchange Server 2007 Enterprise Edition
Microsoft Exchange Server 2007 Standard Edition
Microsoft Exchange Server 2003 Standard Edition
Microsoft Exchange Server 2003 Enterprise Edition

Keywords:
kbmdd kbmsifixme kbfixme atdownload kbfix kbexpertiseadvanced kbqfe

kbsmbportal KB948496

Protocol Error in TDS Stream

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Protocol Error in TDS Stream

Uploaded by

Copyright:

Available Formats

"Protocol error in TDS stream"

Friday, August 27, 2010 12:02 PM

this is not a SSIS error.

Let us TRY this |

Jin Chen - MSFT

this is not a SSIS error.

Let us TRY this |

Jin Chen - MSFT

Marked as answer by Jinchun ChenMicrosoft employee, Moderator Tuesday, September 07,

Monday, August 30, 2010 6:41 AM

The operating system

The advanced properties page of the network adapter

To enable TCP Chimney Offload, follow these steps:

Use administrative credentials to open a command prompt.

To disable TCP Chimney Offload, follow these steps:

Use administrative credentials to open a command prompt.

Use administrative credentials to open a command prompt.

To enable or disable TCP Chimney Offload, follow these steps:

Open Device Manager.

Expected behavior when both the servic

If the firewall is configured to allow for a give

Some firewall vendors have decided to

Internet Protocol security

If the system has an IPsec policy applied, the

Network Adapter teaming

Some OEMs have decided to implement their

If you are using the Microsoft Hyper-V

Network monitoring tools,

Some network monitoring tools may coexist w

Network Load Balancing

If you configure the NLB service on a server,

However, note that TCP connections using th

If this service is installed and running, the TC

How to determine whether TCP Chimney Offload is working

Use administrative credentials to open a command prompt.

Type the following command, and then press ENTER:

Proto Local Address

In this output, the second connection is offloaded.

To enable RSS, follow these steps:

Use administrative credentials to open a command prompt.

Use administrative credentials to open a command prompt.

Use administrative credentials to open a command prompt.

TCP Global Parameters

Note By default, RSS is enabled.

Then, go to the "Did this fix the problem?" section.

Let me fix it myself

To enable or disable NetDMA, follow these steps:

Locate the following registry subkey, and then click it:

Double-click the EnableTCPA registry entry.

Did this fix the problem?

We would appreciate your feedback. To provide feedback or to report any issues

Windows Web Server 2008

Windows Server 2008 Standard

Windows Server 2008 Enterprise

Windows Server 2008 Datacenter

Windows Server 2008 Standard without Hyper-V

Windows Server 2008 for Itanium-Based Systems

Windows Server 2008 Enterprise without Hyper-V

Windows Server 2008 Datacenter without Hyper-V

kbmdd kbenable kbnetworkmon kbnlb kbnetworkcard kbnetworkconnectivity

Support for Office 2003 has ended

Support for Windows Server 2003 will end

You experience slow network performance.