FIX: Error message when you run a transaction from a remote server by using a linked server in SQL Server 2005: "This operation conflicts with another pending operation on this transaction"

Article translations Article translations
Article ID: 949687 - View products that this article applies to.
Bug #: 50002514 (SQL Hotfix)
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.
Expand all | Collapse all

On This Page

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
  • Whether you must restart the computer after you install the hotfix package
  • Whether the hotfix package is replaced by any other hotfix package
  • Whether you must make any registry changes
  • The files that are contained in the hotfix package

SYMPTOMS

Consider the following scenario. In Microsoft SQL Server 2005, you run a transaction from a remote server by using a linked server. The transaction contains a DML statement that is followed by a data definition language (DDL) statement. For example, the transaction contains an INSERT statement that is followed by a DROP TABLE statement. In this scenario, you receive the following error message when you run the transaction:
Server: Msg 3970, Level 16, State 2, Line 1
This operation conflicts with another pending operation on this transaction. The operation failed.
Note This problem does not occur in Microsoft SQL Server 2000.

RESOLUTION

Cumulative update information

The fix for this issue was first released in Cumulative Update 7. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
949095 Cumulative update package 7 for SQL Server 2005 Service Pack 2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

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

To apply this hotfix, you must have SQL Server 2005 Service Pack 2 installed. 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

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.
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Bcp.exe2005.90.3231.068,63224-Feb-200823:36x86
Chsbrkr.dll12.0.7822.01,684,84022-Jun-200709:22x86
Chtbrkr.dll12.0.7822.06,112,61622-Jun-200709:22x86
Databasemailprotocols.dll9.0.3231.046,10424-Feb-200823:36x86
Distmdl.ldfNot applicable2,883,58424-Feb-200821:31Not applicable
Distmdl.mdfNot applicable5,242,88024-Feb-200821:31Not applicable
Distrib.exe2005.90.3231.070,68024-Feb-200823:36x86
Dts.dll2005.90.3231.01,102,36024-Feb-200823:36x86
Dtsconn.dll2005.90.3231.0250,39224-Feb-200823:36x86
Dtspipeline.dll2005.90.3231.0605,20824-Feb-200823:36x86
Fteref.dll12.0.7822.0446,46422-Jun-200709:22x86
Infosoft.dll12.0.7822.0468,32822-Jun-200709:22x86
Instdist.sqlNot applicable149,16324-Feb-200819:03Not applicable
Instorcl.sqlNot applicable153,77924-Feb-200819:03Not applicable
Korwbrkr.dll12.0.7822.071,01622-Jun-200709:22x86
Langwrbk.dll12.0.7822.0136,55222-Jun-200709:22x86
Mergetxt.dll2005.90.3231.032,28024-Feb-200823:36x86
Microsoft.analysisservices.dll9.0.3231.01,217,56024-Feb-200823:36x86
Microsoft.sqlserver.connectioninfo.dll9.0.3231.0156,69624-Feb-200823:36x86
Microsoft.sqlserver.dtstransferprovider.dll9.0.3231.0115,73624-Feb-200823:36x86
Microsoft.sqlserver.maintenanceplantasks.dll9.0.3231.0295,96024-Feb-200823:36x86
Microsoft.sqlserver.replication.dll2005.90.3231.01,628,18424-Feb-200823:36x86
Microsoft.sqlserver.servicebrokerenum.dll9.0.3231.042,00824-Feb-200823:36x86
Microsoft.sqlserver.smo.dll9.0.3231.01,606,68024-Feb-200823:36x86
Microsoft.sqlserver.smoenum.dll9.0.3231.0222,23224-Feb-200823:36x86
Microsoft.sqlserver.sqlenum.dll9.0.3231.0898,07224-Feb-200823:36x86
Msfte.dll12.0.7822.02,430,31222-Jun-200709:22x86
Msftefd.exe12.0.7822.066,92022-Jun-200709:22x86
Msftepxy.dll12.0.7822.095,59222-Jun-200709:22x86
Msftesql.exe12.0.7822.095,59222-Jun-200709:22x86
Msgprox.dll2005.90.3231.0200,21624-Feb-200823:36x86
Msir5jp.dll5.0.2130.03,159,91222-Jun-200709:22x86
Mssqlsystemresource.ldfNot applicable524,28824-Feb-200821:21Not applicable
Mssqlsystemresource.mdfNot applicable40,239,10424-Feb-200821:21Not applicable
Nlhtml.dll12.0.7822.0124,26422-Jun-200709:22x86
Nls400.dll5.0.4217.012,240,74422-Jun-200709:22x86
Odsole70.dll2005.90.3231.058,90424-Feb-200823:36x86
Osql.exe2005.90.3231.053,27224-Feb-200823:36x86
Query9x.dll12.0.7822.048,48822-Jun-200709:22x86
Rdistcom.dll2005.90.3231.0644,63224-Feb-200823:36x86
Replerrx.dll2005.90.3231.0114,71224-Feb-200823:36x86
Replisapi.dll2005.90.3231.0272,92024-Feb-200823:36x86
Replmerg.exe2005.90.3231.0320,53624-Feb-200823:36x86
Replprov.dll2005.90.3231.0552,98424-Feb-200823:36x86
Replrec.dll2005.90.3231.0785,43224-Feb-200823:36x86
Replsub.dll2005.90.3231.0408,08824-Feb-200823:36x86
Replsync.dll2005.90.3231.0101,40024-Feb-200823:36x86
Sac.exe9.0.3231.082,96824-Feb-200823:36x86
Sbmsmdlocal.dll9.0.3231.015,969,30424-Feb-200823:36x86
Sbmsmdredir.dll9.0.3231.04,022,80824-Feb-200823:36x86
Sqlaccess.dll2005.90.3231.0350,23224-Feb-200823:36x86
Sqladhlp.exe2005.90.3231.047,12824-Feb-200823:36x86
Sqlagent90.exe2005.90.3231.0349,72024-Feb-200823:36x86
Sqlbrowser.exe2005.90.3231.0242,71224-Feb-200823:36x86
Sqlcmd.exe2005.90.3231.0143,38424-Feb-200823:36x86
Sqlctr90.dll2005.90.3231.067,60824-Feb-200823:36x86
Sqldiag.exe2005.90.3231.01,074,20024-Feb-200823:36x86
Sqldumper.exe2005.90.3231.068,63224-Feb-200823:36x86
Sqlmaint.exe2005.90.3231.077,84824-Feb-200823:36x86
Sqlmergx.dll2005.90.3231.0194,07224-Feb-200823:36x86
Sqlmgmprovider.dll2005.90.3231.0236,56824-Feb-200823:36x86
Sqlsac.exe2005.90.3231.01,246,23224-Feb-200823:36x86
Sqlservr.exe2005.90.3231.029,216,28024-Feb-200823:36x86
Sqlsqm.exe9.0.3231.0128,02424-Feb-200823:36x86
Sqlwep.dll2005.90.3231.090,64824-Feb-200823:36x86
Sqlwtsn.exe9.0.3231.099,35224-Feb-200823:36x86
Sqsrvres.dll2005.90.3231.070,16824-Feb-200823:36x86
Ssradd.dll2005.90.3231.042,52024-Feb-200823:36x86
Ssravg.dll2005.90.3231.043,03224-Feb-200823:36x86
Ssrmax.dll2005.90.3231.040,98424-Feb-200823:36x86
Ssrmin.dll2005.90.3231.040,98424-Feb-200823:36x86
Ssrpub.dll2005.90.3231.030,23224-Feb-200823:36x86
Svrenumapi.dll2005.90.3231.0615,44824-Feb-200823:36x86
Sysdbupg.sqlNot applicable510,62224-Feb-200819:02Not applicable
Tablediff.exe9.0.3231.087,06424-Feb-200823:36x86
Thawbrkr.dll12.0.7822.0206,18422-Jun-200709:22x86
Xmlfilt.dll12.0.7822.0197,99222-Jun-200709:22x86
Xmlsub.dll2005.90.3231.0194,58424-Feb-200823:36x86
Xpadsi90.exe2005.90.3231.050,71224-Feb-200823:36x86
Xpqueue.dll2005.90.3231.056,85624-Feb-200823:36x86
Xprepl.dll2005.90.3231.073,24024-Feb-200823:36x86
Xpstar90.dll2005.90.3231.0298,52024-Feb-200823:36x86

STATUS

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

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

Important information for SQL Server 2005 Analysis Services

A known issue exists in Cumulative Update 7 for SQL Server 2005 Analysis Services. Consider the following scenario. You install Cumulative Update 7 for SQL Server 2005 SP2. In SQL Server Profiler, you start a trace or stop a trace. Then, you run a query. The execution time of the query exceeds the value of the ForceCommitTimeout server setting. In this scenario, all the queries that are running on the server are canceled. To work around this issue, do not run MDX queries before you start a trace or stop a trace.

Properties

Article ID: 949687 - Last Review: May 6, 2008 - Revision: 2.1
APPLIES TO
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Standard X64 Edition
  • Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Enterprise X64 Edition
  • Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
Keywords: 
kbautohotfix kbsql2005engine kbhotfixrollup kbfix kbpubtypekc kbqfe kbexpertiseadvanced kbhotfixserver KB949687

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com