Microsoft KB Archive/870983

= FIX: Transactional Component does not use the nontransactional connection in OLE DB resource pooling =

Article ID: 870983

Article Last Modified on 11/15/2007

-

APPLIES TO


 * Microsoft Data Access Components 2.8

-





SYMPTOMS
A nontransactional component connects to a remote computer that is running Microsoft SQL Server 2000 Service Pack 3 (SP3) through ActiveX Data Objects (ADO) by using OLE DB resource pooling. Then the connection is closed, and the ADO object is released.

When a transactional component is called from this nontransactional component, the transactional component uses the same ADO connection string to connect to the same SQL Server. This call from the nontransactional component establishes a new connection in the SQL Server instead of reusing the nontransactional connection from the OLE DB resource pooling.



RESOLUTION
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.    Date         Time   Version            Size    File name --  29-Jun-2004  23:22  2.80.1047.0       147,456  Msadds.dll 29-Jun-2004 23:22  2.80.1047.0       512,000  Msado15.dll 29-Jun-2004 23:22  2.80.1047.0       163,840  Msadomd.dll 29-Jun-2004 23:22  2.80.1047.0       184,320  Msadox.dll 29-Jun-2004 23:22  2.80.1047.0        53,248  Msadrh15.dll 29-Jun-2004 23:22  2.80.1047.0       225,280  Msdaora.dll 29-Jun-2004 23:22  2.80.1047.0       147,456  Msdart.dll 29-Jun-2004 23:23  2.575.1047.0      139,264  Msorcl32.dll 29-Jun-2004 23:22  3.525.1047.0      221,184  Odbc32.dll 29-Jun-2004 23:23  2000.85.1047.0     24,576  Odbcbcp.dll 29-Jun-2004 23:22  2.80.1047.0       442,368  Oledb32.dll 29-Jun-2004 23:22  2000.85.1047.0    503,808  Sqloledb.dll 29-Jun-2004 23:22  2000.85.1047.0    401,408  Sqlsrv32.dll 29-Jun-2004 14:25  2000.85.1047.0    208,896  Sqlxmlx.dll



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

