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.

ODBC Provider Incorrectly Interprets SQL_DTC_DONE Flag in Distributed Transaction


View products that this article applies to.

This article was previously published under Q235508

↑ Back to the top


Symptoms

When participating in a distributed transaction, the Microsoft OLE DB Provider for ODBC (MSDASQL) interprets values, other than SQL_DTC_DONE, to mean that the current connection is already enlisted in a distributed transaction. However, the transaction has completed, the connection has been recycled and is being reused, and is involved in a completely different transaction.

This behavior occurs primarily when connecting to a DB2 server.

↑ Back to the top


Cause

When the Microsoft OLE DB Provider for ODBC calls ITransactionJoin::JoinTransaction, a call is being made to the SQLGetConnectAttr() function with the SQL_COPT_SS_ENLIST_IN_DTC attribute. In the DB2 driver, this returns a value other than SQL_DTC_DONE, and that is interpreted to mean the connection is still involved in a distributed transaction.

Since a connection can only be enlisted in one distributed transaction at a time, this generates a XACT_E_XTIONEXISTS return code and the following error message:
Only one transaction allowed

↑ Back to the top


Resolution

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft Data Access Components Service Pack 2 that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone 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 typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:
   Date      Time    Version      Size    File name     Platform
   -------------------------------------------------------------
   6/9/99            2.10.4209    583KB   msdasql.dll
   6/9/99            2.10.4209     10KB   msdasqlr.dll
   6/9/99            2.10.4209    152KB   msdatl2.dll
   6/9/99            2.10.4209     87KB   msdatt.dll

				

↑ Back to the top


Workaround

None.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

This problem no longer occurs in MDAC version 2.1 SP2 and MDAC version 2.5 or later.

↑ Back to the top


More information

Manual Installation

  1. Quit any applications or services that are using the ODBC provider (MSDASQL.dll). This may include Internet Information Server (IIS), Microsoft Transaction Server (MTS), Microsoft Distributed Transaction Coordinator (DTC), and any ADO or ODBC applications.
  2. Download the hotfix (WrongTrans.exe) into a temporary directory and run it to extract the following files:

    • Msdasql.dll
    • Msdasqlr.dll
    • Msdatl2.dll
    • Msdatt.dll
    • Readme.txt
  3. Locate and rename the current versions of the files listed in step two. These files should exist in the \Program files\Common files\System\ole db folder.
  4. Copy the hotfix files into the same location, and restart your services and applications.

Important Notice for Microsoft Windows 95/98 Users

If you are installing this fix on to a computer running Windows 95 or a computer with the original release of Windows 98, you may need to install the Windows 98 Migration DLL included with this fix. Please carefully read the Migrate_qfe.txt file that is included in the Migration.exe file that is in the download file.

↑ Back to the top


Keywords: kbqfe, kbbug, kbdatabase, kbfix, kbmdac210fix, kbprovider, kbqfe, kbhotfixserver, KB235508

↑ Back to the top

Article Info
Article ID : 235508
Revision : 7
Created on : 10/7/2005
Published on : 10/7/2005
Exists online : False
Views : 457