FIX: Error message when an ADO.NET-connected application tries to reuse a connection from the connection pool in SQL Server 2005: "The request failed to run because the batch is aborted" (915112)
The information in this article applies to:
- Microsoft SQL Server 2005 Standard Edition
- Microsoft SQL Server 2005 Standard X64 Edition
- SQL Server 2005 Standard Edition for Itanium-based Systems
- Microsoft SQL Server 2005 Enterprise Edition
- Microsoft SQL Server 2005 Enterprise X64 Edition
- Microsoft SQL Server 2005 Enterprise Edition for Itanium Based Systems
- Microsoft SQL Server 2005 Developer Edition
Bug #: 242 (SQL Hotfix) Bug #: 345 (SQL Hotfix) Bug # 386 (SQL Hotfix) Bug #: 603 (SQL Hotfix) Bug #: 428308 (SQLBUDT)
Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. SUMMARYThis article describes the following about this hotfix
release:
- The issues that are fixed by this hotfix package
- The prerequisites for installing the hotfix
package
- Information about whether you must restart the computer after you install the
hotfix package
- Information about whether the hotfix package is replaced by any other hotfix
package
- Information about whether you must make any registry changes
- The files that are contained in the hotfix
package
SYMPTOMSIn SQL Server 2005, when a Microsoft ADO.NET-connected application tries to reuse a connection from the connection pool, you receive an error message that resembles the following: Error 3980 Severity 16
State 1 The request failed to run because the batch is aborted, this can be
caused by abort signal sent from client, or another request is running in the
same session, which makes the session busy. This problem occurs
when the following conditions are true:
- Connection pooling is enabled in the ADO.NET-connected
application.
- The ADO.NET-connected application uses distributed
transactions.
CAUSEThis problem occurs when SQL Server 2005 must handle a connection reset and a Microsoft Distributed Transaction Coordinator (DTC) abort request for a distributed transaction on the same connection at the same time.RESOLUTIONService pack information
To resolve this problem, obtain the latest service pack for SQL Server
2005. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
913089 How to
obtain the latest service pack for SQL Server 2005
Hotfix informationA 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 SQL Server 2005 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. PrerequisitesThere are no prerequisites for this hotfix. Restart information You do not have to restart the computer after you apply this
hotfix. Registry information You do not have to change the registry. Hotfix file informationThis hotfix contains only those files that are required to correct
the issues that this article lists. This hotfix may not contain of all the
files that you must have to fully update a product to the latest
build.
The English 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.SQL Server 2005, 32-bit version |
Osql.exe | 2005.90.1528.0 | 51,416 | 18-Feb-2006 | 00:18 | Not
Applicable | Replrec.dll | 2005.90.1528.0 | 781,016 | 18-Feb-2006 | 00:18 | Not
Applicable | Sbmsmdlocal.dll | 9.0.1528.0 | 15,588,568 | 18-Feb-2006 | 00:19 | Not
Applicable | Sbmsmdredir.dll | 9.0.1528.0 | 3,927,256 | 18-Feb-2006 | 00:19 | Not
Applicable | Sqlaccess.dll | 2005.90.1528.0 | 349,400 | 18-Feb-2006 | 00:18 | Not
Applicable | Sqldiag.exe | 2005.90.1528.0 | 960,216 | 18-Feb-2006 | 00:18 | Not
Applicable | Sqlservr.exe | 2005.90.1528.0 | 28,778,256 | 18-Feb-2006 | 00:19 | Not
Applicable |
SQL Server 2005, 64-bit version |
Osql.exe | 2005.90.1528.0 | 83,672 | 18-Feb-2006 | 02:48 | Not
Applicable | Replrec.dll | 2005.90.1528.0 | 1,007,320 | 18-Feb-2006 | 02:48 | Not
Applicable | Sbmsmdlocal.dll | 9.0.1528.0 | 15,588,568 | 18-Feb-2006 | 00:19 | Not
Applicable | Sbmsmdredir.dll | 9.0.1528.0 | 3,927,256 | 18-Feb-2006 | 00:19 | Not
Applicable | Sqlaccess.dll | 2005.90.1528.0 | 356,568 | 18-Feb-2006 | 02:48 | Not
Applicable | Sqldiag.exe | 2005.90.1528.0 | 1,127,640 | 18-Feb-2006 | 02:48 | Not
Applicable | Sqlservr.exe | 2005.90.1528.0 | 39,402,712 | 18-Feb-2006 | 02:49 | Not
Applicable |
SQL Server 2005, 64-bit version for Itanium processors |
Osql.exe | 2005.90.1528.0 | 123,096 | 18-Feb-2006 | 03:01 | Not
Applicable | Replrec.dll | 2005.90.1528.0 | 2,137,816 | 18-Feb-2006 | 03:01 | Not
Applicable | Sbmsmdlocal.dll | 9.0.1528.0 | 48,429,784 | 18-Feb-2006 | 03:02 | Not
Applicable | Sbmsmdredir.dll | 9.0.1528.0 | 6,073,560 | 18-Feb-2006 | 03:01 | Not
Applicable | Sqlaccess.dll | 2005.90.1528.0 | 351,448 | 18-Feb-2006 | 03:01 | Not
Applicable | Sqldiag.exe | 2005.90.1528.0 | 1,637,080 | 18-Feb-2006 | 03:01 | Not
Applicable | Sqlservr.exe | 2005.90.1528.0 | 72,227,032 | 18-Feb-2006 | 03:02 | Not
Applicable |
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in SQL Server 2005 Service Pack 1.
Modification Type: | Minor | Last Reviewed: | 7/26/2006 |
---|
Keywords: | kbsql2005sp1fix KBsql2005connect kbBug kbfix kbtshoot kbQFE kbhotfixserver kbpubtypekc KB915112 kbAudITPRO kbAudDeveloper |
---|
|