Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. FIX: Error message when you commit a distributed transaction that contains a query that retrieves data from a linked server in SQL Server 2005: "Transaction manager has cancelled the distributed transaction"

FIX: Error message when you commit a distributed transaction that contains a query that retrieves data from a linked server in SQL Server 2005: "Transaction manager has cancelled the distributed transaction"

View products that this article applies to.

Bug #: 50001297 (SQL Hotfix)

↑ Back to the top

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.

↑ Back to the top

Summary

This article describes the following about this hotfix release:
  • The issues that are fixed by the 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

↑ Back to the top

Symptoms

Consider the following scenario. You use the SQL Native Client OLE DB provider (SQLNCLI) in SQL Server 2005 to create a linked server. You create a distributed transaction. The distributed transaction contains a query that uses the linked server to retrieve data from a table. When you commit the distributed transaction, you may receive the following error message:
Msg 1206, Level 18, State 167, Line 3

The Microsoft Distributed Transaction Coordinator (MS DTC) has cancelled the distributed transaction.

Additionally, you may receive the following error message when you run a query after this behavior occurs:
Msg 8525, Level 16, State 1, Line 1

Distributed transaction completed. Either enlist this session in a new transaction or the NULL transaction.
This problem occurs if the following conditions are true:
  • You use the SQLNCLI provider to create a linked server between two instances of SQL Server 2005.
  • The XACT_ABORT option is set to ON.
  • In the distributed transaction, you try to release a rowset before all rows in the rowset are processed.
Note This problem may also occur if you call the ReleaseRows method in a distributed transaction to release a rowset before you commit a distributed transaction in an application.

↑ Back to the top

Cause

This problem occurs because the SQLNCLI provider incorrectly sends an attention signal to the linked server to roll back the distributed transaction.

↑ Back to the top

Resolution

Hotfix information

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

Prerequisites

You must have SQL Server 2005 Service Pack 2 (SP2) installed to apply this hotfix.

For more information about how to obtain SQL Server 2005 Service Pack 2, 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

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 information

This 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
File nameFile versionFile sizeDateTimePlatform
Sqlncli.dll2005.90.3172.02,234,22425-May-200712:32x86
Sqlnclir.rll2005.90.1399.0205,52813-Oct-200519:48Not Applicable
SQL Server 2005 x64-based version
File nameFile versionFile sizeDateTimePlatform
Sqlncli.dll2005.90.3172.02,234,22425-May-200712:32x86
Sqlnclir.rll2005.90.1399.0205,52813-Oct-200519:48Not Applicable
Msvcm80.dll8.0.50727.42516,09622-Sep-200515:27x64
Msvcp80.dll8.0.50727.421,097,72822-Sep-200515:28x64
Msvcr80.dll8.0.50727.42822,78422-Sep-200515:26x64
SQL Server 2005 Itanium architecture version
File nameFile versionFile sizeDateTimePlatform
Sqlncli.dll2005.90.3172.02,234,22425-May-200712:32x86
Sqlnclir.rll2005.90.1399.0205,52813-Oct-200519:48Not Applicable
Msvcm80.dll8.0.50727.42572,41622-Sep-200515:29IA-64
Msvcp80.dll8.0.50727.421,385,47222-Sep-200515:31IA-64
Msvcr80.dll8.0.50727.421,484,80022-Sep-200515:28IA-64

↑ Back to the top

Workaround

To prevent the SQLNCLI provider from sending an attention signal to the server, use the SQLNCLI provider to consume fully any rowsets that the OLE DB consumer creates.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More Information

For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:

822499 New naming schema for Microsoft SQL Server software update packages

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top

Keywords: kb, kbautohotfix, kbexpertiseadvanced, kbfix, kbsql2005connect, kbpubtypekc, kbqfe, kbhotfixserver

↑ Back to the top

Article Info
Article ID : 937517
Revision : 1
Created on : 1/7/2017
Published on : 10/8/2011
Exists online : False
Views : 839