FIX: A deadlock condition may occur when you call the SQLFetch function or the SQLFetchScroll function in MDAC 2.8

This article has been archived. It is offered "as is" and will no longer be updated.
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.

Hotfix information

A supported hotfix is 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 software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.


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
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
When you call the SQLFetch function or the SQLFetchScroll function, a lock time-out error is not returned. Because a lock time-out error is not returned, your application cannot react appropriately, and the application may stop responding (hang).

For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
839801 FIX: Hotfixes are available for MDAC 2.8
824684 Description of the standard terminology that is used to describe Microsoft software updates

Article ID: 890470 - Last Review: 01/17/2015 09:29:49 - Revision: 3.1

Microsoft Data Access Components 2.8

  • kbnosurvey kbarchive kbautohotfix kbhotfixserver kbbug kbqfe kbprb KB890470