Fix: Multiple Fixes for SQL Server .NET Data Provider

View products that this article applies to.

Expand all | Collapse all

SYMPTOMS

The following bugs have been fixed in the current release of Microsoft SQL Server .NET Data Provider (SqlClient):

When processing a batch of results or a stored procedure, SQL Server can return result sets, errors messages, and informational messages. For example, the DBCC stored procedure returns a mix of result sets, error messages, and informational messages. This is additionally complicated by the fact that SQL Server may return error messages during the call to SQLCommand.ExecuteReader (or other SQLCommand.Executexxx methods), or during the processing of results SQLDataReader.Read and SQLDataReader.NextResult.

With this fix, if the error occurs first in the stream (during the call to SQLCommand.ExecuteReader), it throws a single exception that contains all the error messages, and you do not receive any results.

Note If the error occurs after the first result set, you may see an exception from SQLDataReader that contains all the error messages. This is not a change from the behavior in version 1.1 or in version 1.0.
Version 1.1 of SqlClient introduced a regression in the handling of connection strings that contain apostrophes (') or double quotation marks (""). This causes connection strings with correctly escaped apostrophes or double quotation marks to fail, and you receive the following error message:
Format of the initialization string does not conform to specification starting at index {0}.
This fix removes this regression.
When the SQLCommand.CommandTimeout is set to zero, you expect an infinite timeout. However, versions 1.1 and 1.0 of the SqlClient provider incorrectly timeout when a response from SQL Server is broken into two packets. Immediately upon receipt of the second packet, versions 1.1 and 1.0 of the provider incorrectly timeout. The fix that is included in this article fixes this issue so that the command will have an infinite timeout.
When you use a COMPUTE BY clause in a SQL statement, versions 1.1 and 1.0 of SqlClient fail, and you receive the following error message:
"COMPUTE BY statements not supported"
With this fix, SqlClient correctly handles a COMPUTE BY clause in SQL statements.

Note All these problems have been fixed in the latest build of SQL Server .NET Data Provider (System.Data.dll). This fix only exists for the Microsoft .NET Framework 1.1, and does not fix the problem in the .NET Framework 1.0.

Back to the top

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem described in this article. Only apply it to systems that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next .NET Framework 1.1 service pack that contains this fix.

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:

http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)

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 fix 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.

   Date         Time   Version            Size    File name
   -------------------------------------------------------------------------------------
   27-Jun-2003  15:01  1.1.4322.918    1,294,336  System.data.dll  
   30-Jun-2003  22:27  1.0.0.0         1,629,352  Ndp1.1-kb823679-x86.exe  
   03-Jul-2003  03:20  5.3.17.17         709,920  Windowsserver2003-kb821415-x86-enu.exe

Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Back to the top

MORE INFORMATION

To install the fix in a computer that is running Microsoft Windows Server 2003, install Windowsserver2003-kb821415-x86-enu.exe.

To install the fix on a computer that is running Microsoft Windows NT or Microsoft Windows 2000 Server, install Ndp1.1-kb823679-x86.exe.

Back to the top