Article ID: 2006769 - View products that this article applies to.
Consider the following scenario for either SQL Server 2005 or SQL Server 2008 environments:
In this scenario, you will notice the following:
Note: The problem could happen with any operation that uses either LoadFromSqlServer or SaveToSqlServer methods when both the conditions (encryption and large packet size) discussed in this section are true.
Secure Socket Layer (SSL) and its replacement, Transport Layer Security(TLS), limit data fragments to 16k in size. This is documented in the public RFC 2246 (section 6.2.2) and the current implementation of SQL Network Interface (SNI) layer adheres to this specification. So when using a network packet size that is greater than 16388 (16K) in environments where encryption is enabled on SQL Server, you will run into errors discussed in the Symptoms section. For further information refer to the following KB article:
To resolve this problem, specify a network packet size that is smaller than 16384 (16K) bytes. You may use the following code to set the network packet size configuration option of the sp_configure system stored procedure:
EXEC sp_configure 'network packet size', 16383
RECONFIGURE WITH OVERRIDE
The network packet size can also be altered via the Server Properties page in Object Explorer. Select the Advanced option and type in the new value for Network Packet Size and click OK.
Note: You do not need to restart SQL Server for the change to be effective. After this setting is changed, all new connections receive the new value.
Steps to reproduce:
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.
Article ID: 2006769 - Last Review: January 14, 2010 - Revision: 5.0
Contact us for more help
Connect with Answer Desk for expert help.