You are currently offline, waiting for your internet to reconnect

FIX: "General Network Error" when you use SqlClient with SSL encryption

This article has been archived. It is offered "as is" and will no longer be updated.
You use Secure Sockets Layer (SSL) encryption with Microsoft SQL Server 2000. If SQL Server finds a valid certificate on the local computer that is issued to the fully-qualified domain name of the computer, and you use the SQL Server .NET data provider (SqlClient), you may receive the following error message:
General Network Error. Check your network documentation.
This occurs with a SqlClient program when you try to bring back a large set of data (over 64k). The problem does not occur with a small set of data.

Typically, you see this problem when the following are true:
  • On the General tab of Server Network Utility, you click to select the Force Protocol Encryption check box.
  • On the General tab of Server Network Utility, you click to clear the Force Protocol Encryption check box. However, SQL Server finds a valid server certificate and tries to use it for encrypting login packets.
You see the following callstack when this problem occurs:
  exception in TraceLogProcess:General network error.  Check your network documentation.:   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, TdsParserState state)  at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, TdsParserState state)at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning()at System.Data.SqlClient.TdsParser.ReadNetlib(Int32 bytesExpected)at System.Data.SqlClient.TdsParser.ReadBuffer()at System.Data.SqlClient.TdsParser.ReadByteArray(Byte[] buff, Int32 offset, Int32 len)at System.Data.SqlClient.TdsParser.ReadSqlValue(_SqlMetaData md, Int32 length)at System.Data.SqlClient.TdsParser.ProcessRow(_SqlMetaData[] columns, Object[] buffer, Int32[] map, Boolean useSQLTypes)at System.Data.SqlClient.SqlDataReader.PrepareSQLRecord(Int32 i)at System.Data.SqlClient.SqlDataReader.GetSqlInt32(Int32 i)at System.Data.SqlClient.SqlDataReader.GetInt32(Int32 i)
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next .NET Framework service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Microsoft .NET Framework

   Date         Time   Version            Size    File name   --------------------------------------------------------------   11-Jun-2003  21:38         3,010,728  Ndp1.0sp2-kb821289-x86-enu.exe     10-Jun-2003  14:24  1.0.3705.432    1,179,648  				

Microsoft .NET Framework 1.1

   Date         Time   Version            Size    File name   --------------------------------------------------------------   23-Oct-2003          1.1.4322.962    1,294,336  System.Data.dll   24-Oct-2003         1,671,856  NDP1.1-KB821289-X86.exe  				

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
When you try to bring back a large set of data (over 64k), SqlClient internally sets the network packet size to 64k. When you enable SSL encryption, the client-side network library for SQL Server (DBNetlib) cannot handle a packet size that is more than 64k. Because of this problem, DBNetLib throws the error that is mentioned in the "Symptoms" section. With the current fix, SqlClient does not set the packet size to 64k. SqlClient sets the packet size to 32k.

Article ID: 821289 - Last Review: 12/08/2015 02:48:37 - Revision: 4.1

Microsoft .NET Framework 1.1, Microsoft .NET Framework 1.0

  • kbnosurvey kbarchive kbbug kbfix kbqfe kbnetframe100presp3fix kbhotfixserver KB821289