RESOLUTION
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Prerequisites
Before you install this update, you must have MDAC 2.8 installed
on your computer.
To determine the version of MDAC that you are
running, view the following registry key:
HKEY_LOCAL_MACHINE\Software\Microsoft\DataAccess\FullInstallVer
After you install the cumulative hotfix, the
FullInstallVer subkey will change to represent the cumulative build number value
of
2.80.nnnn.xx, where
nnnn is the build number of
this hotfix. By comparing the build number of any other MDAC 2.80 hotfix, you
can determine whether the build is a later build that includes additional fixes
or if it is an earlier build that will not install.
For more information about how to determine your version of
MDAC, click the following article number to view the article in the Microsoft Knowledge Base:
301202
How to check for MDAC
version
Hotfix update information
The following hotfixes have been released for MDAC 2.8. The following hotfixes are
found in packages with a
FullInstallVer subkey value of
2.80.1054 or a later version:
823109 FIX: An access violation may occur when a program calls the UpdateBatch method of an ADO Recordset object by using the OLE DB Provider for ODBC in Data Access Components
887576 FIX: You may receive an access violation in your application when you bind too many parameters to an ODBC statement handle and then you clean up the statement handle
896108 FIX: You notice a small memory leak when a direct or indirect call to the WrapDSOandSession method of ADO Connection object is made and the MSDataShape provider is not used in MDAC 2.8
This hotfix is packaged with new installer technology. This new
installer technology provides many benefits, including Uninstall. However, you should test this new
installer technology before you apply it to servers in production.
The
following fix is found in packages with a
FullInstallVer subkey value of
2.80.1048.0 and later:
322968 FIX: CColumnsInfo reference count leak in MSDAORA REF CURSOR when you retrieve data from an Oracle
function
The following fixes are found in packages with a
FullInstallVer subkey value of
2.80.1045.0 and later:
832483 MS04-003: Buffer overrun in an MDAC function could allow code execution
292648 FIX:
Bcp.exe ignores -R regional settings switch when using format file
(-f)
328514 FIX:
Binding an output parameter of an Oracle stored procedure to adBSTR results in
an incorrect value
329964 FIX:
Microsoft SQL Server ODBC driver cannot retrieve output parameters of a remote
stored procedure on a linked server
330019 FIX: SQLXML
that includes MDAC 2.7 returns GUID fields without "{}" characters
817518 Passing
ADODB::Field object to ADO Command.CreateParameter method causes a memory
leak
822841 FIX:
Setting of connection attribute fails when you use connection pooling for the
SQL Server ODBC connection
826770 FIX:
Incorrect native SQL error information when you use SQLXML to retrieve
data
827452 FIX: General network error when you try to back up or restore a SQL Server database on a computer that is running Windows Server 2003
830497 Floating
point exception in Msadrh15!CRowsetHelper::ProcessAccessor
831715 Catastrophic failure" error message when you use the "SQL Server Login"
dialog box to set the database name
836830 FIX: Query performance declines when you use the SET FMTONLY Hint in the Microsoft ODBC Driver for SQL Server and the Microsoft OLE DB Provider for SQL Server
837311 FIX: You cannot import data from a text file that is greater than 32 MB by using the BCP utility
838405 FIX: "Argument passed to data shaping service was invalid" error after you apply MDAC 2.8
838768 FIX: Accessibility error occurs when you configure a UDL file on a computer that is running a 64-bit operating system
838976 FIX: SQLOLEDB stops responding when the sqlxmlx.dll file unloads unexpectedly
831832 Oracle ODBC driver returns SQL_DECIMAL for all convert function calls
834905 FIX: You receive an "ORA-01012" error message when you connect to an Oracle database by using MSDAORA
815701 FIX: Memory leak may occur in Microsoft OLE DB Provider for Oracle when you use the REF CURSOR data type and the LONG data type
835677 FIX: You
may receive the "Cannot insert or update columns from multiple tables" error
message when you try to insert or to update data in a multi-table view by using a
server-side cursor
843248 FIX: You receive a "Cannot generate SSPI context" error message when you try to connect to a SQL Server 2000 SP3 server computer
887576 FIX: You may receive an access violation in your application when you bind too many parameters to an ODBC statement handle and then you clean up the statement handle
890470 FIX: A deadlock condition may occur when you call the SQLFetch function or the SQLFetchScroll function in MDAC 2.8
890759 FIX: You may receive the "Server: Msg 7399, Level 16, State 1, Line 1" error message when you run a query against a remote view through a linked server in SQL Server 2000
File information
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
--------------------------------------------------------------
10-Dec-2004 16:09 2000.85.1057.0 73,728 Dbnetlib.dll
10-Dec-2004 16:10 2000.85.1057.0 28,672 Dbnmpntw.dll
10-Dec-2004 16:09 2.80.1057.0 315,392 Msadce.dll
10-Dec-2004 16:09 2.80.1057.0 135,168 Msadco.dll
10-Dec-2004 16:09 2.80.1057.0 49,152 Msadcs.dll
10-Dec-2004 16:09 2.80.1057.0 147,456 Msadds.dll
10-Dec-2004 16:09 2.80.1057.0 507,904 Msado15.dll
10-Dec-2004 16:10 2.80.1057.0 163,840 Msadomd.dll
10-Dec-2004 16:10 2.80.1057.0 184,320 Msadox.dll
10-Dec-2004 16:09 2.80.1057.0 53,248 Msadrh15.dll
10-Dec-2004 16:10 2.80.1057.0 225,280 Msdaora.dll
10-Dec-2004 16:09 2.80.1057.0 192,512 Msdaprst.dll
10-Dec-2004 16:09 2.80.1057.0 147,456 Msdart.dll
10-Dec-2004 16:09 2.80.1057.0 303,104 Msdasql.dll
10-Dec-2004 16:10 2.575.1057.0 139,264 Msorcl32.dll
10-Dec-2004 16:09 3.525.1057.0 221,184 Odbc32.dll
10-Dec-2004 16:10 2000.85.1057.0 24,576 Odbcbcp.dll
10-Dec-2004 16:09 2.80.1057.0 442,368 Oledb32.dll
10-Dec-2004 16:09 2000.85.1057.0 503,808 Sqloledb.dll
10-Dec-2004 16:09 2000.85.1057.0 401,408 Sqlsrv32.dll
10-Dec-2004 15:57 2000.85.1057.0 208,896 Sqlxmlx.dll
Note: When you receive this hotfix from Microsoft Product Support Services, the article number that is listed in the hotfix package may be different from the cumulative article number.
STATUS
Microsoft has confirmed that this is a bug in the Microsoft
products that are listed in the "Applies to"
section.