BUG: MTS Connection Pooling Problem with Visual Basic 5.0

Last reviewed: February 9, 1998
Article ID: Q180221
The information in this article applies to:
  • Microsoft Transaction Server 1.0
  • Microsoft Visual Basic Professional and Enterprise Editions for Windows, version 5.0

SYMPTOMS

Microsoft Transaction Server (MTS) does not correctly pool database connections when using RDO 2.0 after installing Visual Basic 5.0 Service Pack 2. A new connection is created with each call to the database instead of using the already existing connections.

RESOLUTION

The two resolutions are listed below:

  • Install ODBC version 3.5.

    -or-

  • Edit your Data Source through the ODBC administrator. Find the check box 'Create temporary stored procedures for prepared SQL statements' and clear it. Use this Data Source Name (DSN) to connect to the database. Do not use a DSN-less connection.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

If you are using SQL Server you can use the SQL Performance Monitor (Perfmon.exe) to check your active connections. If connection pooling is not working, you will see the User Connections counter increase by one each time you activate a method that uses RDO from your MTS server application.

Keywords          : TSrvConnect
Version           : WINDOWS:5.0; WINNT:1.0
Platform          : WINDOWS winnt
Issue type        : kbbug
Solution Type     : kbpending


================================================================================


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.

Last reviewed: February 9, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.