Microsoft KB Archive/330094

= FIX: Open Database Connectivity Cursor Library Does Not Report Deadlock Errors to the Client =

Article ID: 330094

Article Last Modified on 10/11/2005

-

APPLIES TO


 * Microsoft Data Access Components 2.7
 * Microsoft Data Access Components 2.7 Service Pack 1

-



This article was previously published under Q330094





SYMPTOMS
If a deadlock condition occurs on Microsoft SQL Server in an application that uses the open database connectivity (ODBC) cursor library, a function call to the ODBC API SQLExtendedFetch returns SQL_SUCCESS instead of SQL_ERROR. This return is expected to indicate that the deadlock condition has occurred.



CAUSE
All function calls to SQLExtendedFetch that are issued to the ODBC cursor library are internally passed to the SQLFetch function of the ODBC driver. The ODBC cursor library filters the error messages that SQLFetch returns in the ODBC driver, and then sends them to SQLExtendedFetch in the cursor library.



RESOLUTION
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.7 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

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

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 typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix has the file attributes (or later) 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 ---  08-Oct-2002  16:00   3.520.9031.5    61,440   Odbccr32.dll 08-Oct-2002 16:00   3.520.9031.5    61,440   Odbccu32.dll



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Keywords: kbbug kbfix kbqfe kbhotfixserver KB330094

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.