Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/171101

From BetaArchive Wiki
Knowledge Base

Article ID: 171101

Article Last Modified on 10/3/2003


  • Microsoft SQL Server 6.5 Service Pack 1

This article was previously published under Q171101

BUG #: 16172 (Windows NT: 6.5)


If a cursor is declared and deallocated, but not opened on the first execution of a stored procedure or trigger, the next execution of the stored procedure or trigger where the cursor is opened results in the following error:

Msg 16916, Level 16, State 1
A cursor with the name '<cursor>' does not exist

This error may be followed by a handled access violation (AV) that terminates the client connection.


To work around this problem, open the cursor before deallocating it.


Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.5. This problem does not occur in U.S. Service Pack 2 for Microsoft SQL Server version 6.5. For more information, contact your primary support provider.


If you try to drop the stored procedure after the handled access violation, you will encounter the following error message:

Msg 3702, Level 16, State 3 Cannot drop the procedure '<procedure>' because it is currently in use.

You must restart SQL Server to drop and re-create the procedure.

Keywords: kbbug kbusage kbsqlserv650bug KB171101