Select the product you need help with
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"Article ID: 915112 - View products that this article applies to. 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. On This PageSummaryThis article describes the following about this hotfix
release:
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.
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 informationTo 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
(http://support.microsoft.com/kb/913089/
)
How to
obtain the latest service pack for SQL Server 2005
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
(http://support.microsoft.com/contactus/?ws=support)
PrerequisitesThere are no prerequisites for this hotfix.Restart informationYou do not have to restart the computer after you apply this hotfix.Registry informationYou 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 versionCollapse this table
SQL Server 2005, 64-bit versionCollapse this table
SQL Server 2005, 64-bit version for Itanium processorsCollapse this table
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. More information
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe
Microsoft software updates
PropertiesArticle ID: 915112 - Last Review: December 25, 2012 - Revision: 3.0 Applies to
| Article Translations
|



Back to the top








