FIX: AV If Extended Cursor Opens SP Without Execute Permission

 Last reviewed: June 27, 1997
Article ID: Q162906
The information in this article applies to:
  • Microsoft SQL Server, version 6.5
BUG #: 16434 (6.5)

SYMPTOMS

A handled access violation (AV) may occur if an extended cursor (not a Transact-SQL ANSI cursor) is opened on a stored procedure to which you do not have execute permission. For example, suppose in a Visual Basic program using the Remote Data Objects (RDO) interface, you call the function OpenResultSet on a stored procedure. OpenResultSet in turn calls the ODBC function SQLExecDirect, which then calls sp_cursoropen. If this is called on a stored procedure to which you do not have execute permission, you may receive a handled AV in xpcursordeclare().

WORKAROUND

Ensure all necessary permissions are granted on stored procedures in the database. Under some conditions, it may be necessary to drop and re-create the stored procedures before granting permissions on them.

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 3 for Microsoft SQL Server version 6.5. For more information, contact your primary support provider.

Keywords : kbbug6.50 kbusage SSrvGPF SSrvStProc SSrvTran_SQL
Version : 6.5
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: June 27, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.