FIX: Truncated result is returned without any error message if a connection that contains a pending transaction is disconnected by SQL Server
Consider the following scenario:
- You have a Microsoft .NET Framework 4-based client application that starts a transaction on a Microsoft SQL Server database. The application starts the transation by using one of the following methods:
- Executing the Begin Transaction command
- Calling the SqlConnection.BeginTransaction method
- Using the System.Transaction.TransactionScope class
- A SqlDataReader objectinside the transaction reads the database rows, but the object is blocked by a lock on a row.
- While the SqlDataReader objectis blocked, the connection between the application and the database is disconnected. This behavior may occur if one of the following conditions is true:
- The database administrator uses the KILL command.
- The server is restarted, or the server fails over to an alternative server.
In this scenario, the SQLDataReader object returns a result that is truncated without reporting an error message to the client.
After you apply this hotfix, an error message that resembles the following is sent to the client in the scenario that is described in the “Symptoms” section:
A severe error occurred on the current command. The results, if any, should be discarded.
Hotfix informationA supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft website: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.
PrerequisitesTo apply this hotfix, you must have the .NET Framework 4 installed.
Restart requirementYou do not have to restart the computer after you apply this hotfix if the affected files are not being used. We recommend that you close all .NET Framework applications before you apply this hotfix.
File informationThe global version of this hotfix has the file attributes (or later file attributes) 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 item in Control Panel.
|File name||File version||File size||Date||Time||Platform|
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 2645084 - Last Review: 01/12/2012 08:52:00 - Revision: 2.0
Microsoft .NET Framework 4
- kbqfe kbhotfixserver kbfix kbexpertiseadvanced kbsurveynew KB2645084