DOCUMENT:Q168161 22-AUG-1997 [vbwin] TITLE :FIX: Distributed Transaction Fails on Subsequent Runs PRODUCT :Microsoft Visual Basic for Windows PROD/VER:5.0 97 OPER/SYS:NT WINDOWS KEYWORDS:vb5all VB5FixlistSP1 VBKBRDO VS97FixlistSP2 VS97FixlistSP1 VB5FixlistSP2 ====================================================================== --------------------------------------------------------------------- The information in this article applies to: - Microsoft Visual Basic Enterprise Edition for Windows, version 5.0 - Microsoft Visual Studio 97 - Microsoft Visual C++, 32-bit Editions, version 5.0 --------------------------------------------------------------------- SYMPTOMS ======== Using distributed transactions from RDO 2.0 may generating an error stating that the connection is invalid. CAUSE ===== The problem may occur when RDO loads the Distributed Transaction Coordinator (DTC) components after having previously unloaded them. RDO no longer unloads the DTC components when it is unloaded from memory. The DTC components are then unloaded when the process ends. STATUS ====== Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug has been corrected in version 5.00.3817 of the file msrdo20.dll, which is included in Visual Studio 97 Service Pack 1. For additional information about the Visual Studio 97 Service Pack 1, please see the following article in the Microsoft Knowledge Base: ARTICLE-ID: Q170365 TITLE : INFO: Visual Studio 97 Service Pack 1 - What, Where, and Why ====================================================================== Keywords : vb5all VB5FixlistSP1 VBKBRDO VS97FixlistSP2 VS97FixlistSP1 VB5FixlistSP2 Version : 5.0 97 Platform : NT WINDOWS Issue type : kbbug Solution Type : kbfix ============================================================================= THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY. Copyright Microsoft Corporation 1997.