FIX: Error 7102 with Keyset-Driven Cursors on Table with Text Column

Article translations Article translations
Article ID: 246775 - View products that this article applies to.
This article was previously published under Q246775
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 54992 (SQLBUG_70)
Expand all | Collapse all

Symptoms

A keyset-driven cursor on a SELECT statement that uses the NOLOCK option on a table with a text column returns error 7102, if during fetching the data one of the records of the cursor's result set is deleted from another connection.

Error message 7102 is:
Server: Msg 7102, Level 20, State 99, Procedure sp_cursorfetch, Line 24
SQL Server Internal Error. Text manager cannot continue with current statement.

Workaround

To work around this problem, use either of the following:
  • Remove the NOLOCK option from the SELECT statement.

    -or-
  • Change the cursor to any other type (for example, static, dynamic, or fast_forward).

Status

Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
254561 INF: How to Obtain Service Pack 2 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.

Properties

Article ID: 246775 - Last Review: October 26, 2013 - Revision: 3.0
Applies to
  • Microsoft SQL Server 7.0 Standard Edition
Keywords: 
kbnosurvey kbarchive kbbug kbfix KB246775

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com