FIX: Nested Cursors Can Cause a Handled Access Violation
Article ID: 157846
Article Last Modified on 10/3/2003
APPLIES TO
- Microsoft SQL Server 6.5 Standard Edition
This article was previously published under Q157846
BUG #: 15710 (6.50)
SYMPTOMS
A nested cursor fetch on basic select type cursors can cause a handled
access violation, as well as the inability to locate locally defined
variables or the cursor. The SQL Server error log will contain a
Language Exec error, followed by a stack trace. The following errors, as
well as a client disconnect, are reported on the client:
16921 Cursorfetch: Must declare variable '%s'.
16916 A cursor with the name '%s' does not exist.
WORKAROUND
Do not use cursors in a nested fashion where the inner cursor relies on the
results of the outer cursor.
STATUS
Microsoft has confirmed this to be a problem in Microsoft SQL Server
version 6.5. This problem has been corrected in U.S. Service Pack 2 for
Microsoft SQL Server version 6.5. For more information, contact your
primary support provider.
Additional query words: AV
Keywords: kbbug kbfix kbnetwork KB157846