Select the product you need help with
FIX: You receive error messages when you use the Failover Partner connection string attribute to connect to a mirror server in a transaction in SQL Server 2005Article ID: 971654 - View products that this article applies to. On This PageSYMPTOMSConsider the following scenario in Microsoft
SQL Server 2005:
Exception: System.Transactions.TransactionAbortedException
ErrorMessage: The transaction has aborted. Inner Exception: System.InvalidOperationException ErrorMessage: The requested operation cannot be completed because the connection has been broken. RESOLUTION A 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. 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, submit a request to 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)
PrerequisitesYou must have the .NET Framework 2.0 Service Pack 2 (SP2) installed to apply this hotfix.Restart requirementYou do not have to restart the computer after you apply this hotfix if no instance of the .NET Framework is being used.Hotfix replacement informationThis hotfix does not replace other hotfixes.File informationThe 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.For all supported x86-based versions of Windows XP, of Windows Server 2000, and of Windows Server 2003Collapse this table
For all supported x64-based versions of Windows XP, of Windows Server 2000, and of Windows Server 2003Collapse this table
For all supported Itanium-based versions of Windows XP, of Windows Server 2000, and of Windows Server 2003Collapse this table
For all supported x86-based versions of Windows VistaCollapse this table
For all supported x64-based versions of Windows VistaCollapse this table
For all supported Itanium-based versions of Windows VistaCollapse this table
WORKAROUNDTo
work around this problem, use one of the following procedures. Workaround 1Keep the connection in the transaction closed until the TransactionScope class is fully committed.Workaround 2Manage the transaction manually. Do not use the methods in the TransactionScope class to manage the transaction.STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section. PropertiesArticle ID: 971654 - Last Review: August 4, 2010 - Revision: 4.0
|


Back to the top








