FIX: AV If Extended Cursor Opens SP Without Execute PermissionID: Q162906
|
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().
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.
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 : kbusage SSrvGPF SSrvStProc SSrvTran_SQL kbbug6.50
Version : 6.5
Platform : WINDOWS
Issue type :
Last Reviewed: April 8, 1999