The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

Knowledge Base

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

Article ID: 246775

Article Last Modified on 3/14/2006

APPLIES TO

Microsoft SQL Server 7.0 Standard Edition

This article was previously published under Q246775

BUG #: 54992 (SQLBUG_70)

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.

Keywords: kbbug kbfix KB246775

Microsoft KB Archive/246775

Contents