SYMPTOMS
When you call the
SQLFetch function or the
SQLFetchScroll function to return a result set from Microsoft SQL Server, a
deadlock condition may occur. The deadlock condition occurs when the following
conditions are true:
- You use the LOCK_TIMEOUT setting in SQL Server.
- You set the rowset size to a value that is larger than
1.
The deadlock condition occurs more frequently when you
repeatedly call the
SQLFetch function or the
SQLFetchScroll function.
Note This problem does not occur when you set the rowset size to a
value of 1.
RESOLUTION
Hotfix information
A
supported hotfix is now available from Microsoft, but it is only intended to
correct the problem that is described in this article. Only apply it to systems
that are experiencing this specific problem. This hotfix may receive additional
testing. Therefore, if you are not severely affected by this problem, we
recommend that you wait for the next Microsoft Data Access Components (MDAC)
2.8 service pack that contains this hotfix.
To resolve this problem
immediately, 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
No prerequisites are required.
Restart requirement
You must restart your computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
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 item in Control Panel.
Date Time Version Size File name
---------------------------------------------------------
03-Dec-2004 15:20 2000.85.1056.0 73,728 Dbnetlib.dll
03-Dec-2004 15:21 2000.85.1056.0 28,672 Dbnmpntw.dll
03-Dec-2004 15:20 2.80.1056.0 315,392 Msadce.dll
03-Dec-2004 15:20 2.80.1056.0 135,168 Msadco.dll
03-Dec-2004 15:20 2.80.1056.0 49,152 Msadcs.dll
03-Dec-2004 15:20 2.80.1056.0 147,456 Msadds.dll
03-Dec-2004 15:20 2.80.1056.0 512,000 Msado15.dll
03-Dec-2004 15:20 2.80.1056.0 163,840 Msadomd.dll
03-Dec-2004 15:20 2.80.1056.0 184,320 Msadox.dll
03-Dec-2004 15:20 2.80.1056.0 53,248 Msadrh15.dll
03-Dec-2004 15:20 2.80.1056.0 225,280 Msdaora.dll
03-Dec-2004 15:20 2.80.1056.0 192,512 Msdaprst.dll
03-Dec-2004 15:20 2.80.1056.0 147,456 Msdart.dll
03-Dec-2004 15:20 2.80.1056.0 303,104 Msdasql.dll
03-Dec-2004 15:21 2.575.1056.0 139,264 Msorcl32.dll
03-Dec-2004 15:20 3.525.1056.0 221,184 Odbc32.dll
03-Dec-2004 15:21 2000.85.1056.0 24,576 Odbcbcp.dll
03-Dec-2004 15:20 2.80.1056.0 442,368 Oledb32.dll
03-Dec-2004 15:20 2000.85.1056.0 503,808 Sqloledb.dll
03-Dec-2004 15:20 2000.85.1056.0 401,408 Sqlsrv32.dll
03-Dec-2004 15:08 2000.85.1056.0 208,896 Sqlxmlx.dll