FIX: Lock Timeout on Scrollable Cursor May Occur if Page Locking is Disabled (323248)



The information in this article applies to:

  • Microsoft SQL Server 2000 (all editions)

This article was previously published under Q323248
BUG #: 358073 (SHILOH_BUGS)

SYMPTOMS

If you use the sp_indexoption stored procedure to disable page locks for an index, you may unexpectedly experience the following lock timeout error message when an application fetches data from a server-side scrollable cursor:
Server: Msg 1222, Level 16, State 52, Line 8 Lock request time out period exceeded.
This error message is returned immediately. If you issue
SELECT @@LOCK_TIMEOUT
				
on this connection, the result is a -1, which indicates that no lock timeout threshold has been defined. The error message only occurs if the table is being modified simultaneously by a different connection.

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

290211 INF: How To Obtain the Latest SQL Server 2000 Service Pack

NOTE: The following hotfix was created before the release of Microsoft SQL Server 2000 Service Pack 3.

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
   ------------------------------------------------------------------

   20-May-2002   16:48   8.00.0630   7,454,801 bytes   Sqlservr.exe     
				
NOTE: Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
This problem was first corrected in Microsoft SQL Server 2000 Service Pack 3.

Modification Type:MinorLast Reviewed:9/27/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix kbSQLServ2000preSP3fix KB323248