FIX: ODBC Connection from COM+ Component May Connect to Wrong Database

Article translations Article translations
Article ID: 306414 - View products that this article applies to.
This article was previously published under Q306414
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

SYMPTOMS

If a COM+ component establishes two database connections within the context of the same transaction, the first connection string is used to make the second connection. This problem only occurs if you use ODBC to make both connections.

If you use the OLE DB Provider for ODBC to make the ODBC connection, the problem only occurs if OLE DB resource pooling has been disabled for the connections.

CAUSE

This problem occurs because of a bug in COM+. This bug only occurs if you have applied Microsoft Windows 2000 Service Pack 2 or COM+ Rollup Hotfix 3 or later.

If you are unsure which service pack or COM+ hotfix is installed, check the version number of the Comsvcs.dll file that is located in the System32 folder (this file is hidden by default). The last four digits of the version number represent the build number. If the build number is greater than or equal to 3464 and less than 3485, your system may encounter this problem.

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
322389 How to Obtain the Latest Windows XP Service Pack
To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack

To resolve this problem, obtain Microsoft COM+ Rollup Hotfix 15. For additional information, please see the following article in the Microsoft Knowledge Base:
306417 INFO: Availability of Windows 2000 Post-Service Pack 2 COM+ Hotfix Rollup Package 15

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Windows 2000 Service Pack 3 (SP3) and Microsoft Windows XP Service Pack 1 (SP1).

MORE INFORMATION

For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:
265173 The Datacenter Program and Windows 2000 Datacenter Server Product
For additional information about how to install multiple hotfixes with only one reboot, click the article number below to view the article in the Microsoft Knowledge Base:
296861 Use QChain.exe to Install Multiple Hotfixes with One Reboot
For additional information about how to install Windows 2000 and Windows 2000 hotfixes at the same time, click the article number below to view the article in the Microsoft Knowledge Base:
249149 Installing Microsoft Windows 2000 and Windows 2000 Hotfixes

Properties

Article ID: 306414 - Last Review: February 27, 2014 - Revision: 2.2
APPLIES TO
  • Microsoft COM+ 1.0, when used with:
    • the operating system: Microsoft Windows 2000
    • the operating system: Microsoft Windows XP
  • Microsoft COM+ 1.5, when used with:
    • the operating system: Microsoft Windows 2000
    • the operating system: Microsoft Windows XP
Keywords: 
kbnosurvey kbarchive kbbug kbfix kbwin2000presp3fix kbwin2000sp3fix kbwinxpsp1fix KB306414

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