Microsoft KB Archive/810967

= XA_END May Return an Exception Error in Microsoft Distributed Transaction Coordinator =

Article ID: 810967

Article Last Modified on 11/8/2004

-

APPLIES TO


 * Microsoft COM+ 1.0, when used with:
 * Microsoft Windows 2000 Standard Edition
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Service Pack 3
 * Microsoft Windows 2000 Service Pack 2
 * Microsoft Windows 2000 Service Pack 1
 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Service Pack 3
 * Microsoft Windows 2000 Service Pack 2
 * Microsoft Windows 2000 Service Pack 1
 * Microsoft Windows 2000 Professional Edition

-





SYMPTOMS
This problem occurs when you create two XA connections in a test application:
 * 1) The test application points both connection objects to the same database, and both connection objects use the same user ID and password.
 * 2) The test application creates two XA connections, gets the XAResource object from each connection, and creates an XID.
 * 3) One of the XAResource objects becomes associated with a transaction branch. The object does some work, and then the object is suspended.
 * 4) If the other XAResource object does more work on the same transaction branch and calls the XA_END function, an XA exception error occurs and the XA_END call returns -3 in Microsoft Distributed Transaction Coordinator (MSDTC).



CAUSE
This problem occurs because an internal transaction manager join flag (TMJOIN) is handled incorrectly in the XA_START function. If you specify this flag, a new transaction is always created for the XAResource object to join, regardless of whether an existing transaction is found for the object to join.



How to Obtain the Hotfix
This issue is fixed in the Windows 2000 Server COM+ 1.0 Hotfix Package 24. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

810578 INFO: Availability of Windows 2000 Post-Service Pack 3 COM+ Hotfix Rollup Package 24



STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the &quot;Applies to&quot; section of this article.

