SQL Server Errors or Failures from Error: 16915 to Error: 16941



Error: 16915, Severity: 16, A cursor with the name ‘%.*ls’ already exists.
Error: 16916, Severity: 16, A cursor with the name ‘%.*ls’ does not exist.
Error: 16917, Severity: 16, Cursor is not open.
Error: 16922, Severity: 16, Cursor Fetch: Implicit conversion from data type %s to %s is not allowed.
Error: 16924, Severity: 16, Cursorfetch: The number of variables declared in the INTO list must match that of selected columns.
Error: 16925, Severity: 16, The fetch type %hs cannot be used with dynamic cursors.

Error: 16926, Severity: 16, sp_cursoroption: The column ID (%d) does not correspond to a text, ntext, or image column.
Error: 16927, Severity: 16, Cannot fetch into text, ntext, and image variables.
Error: 16928, Severity: 16, sp_cursor: Exec statement is not allowed as source for cursor insert.
Error: 16929, Severity: 16, The cursor is READ ONLY.
Error: 16930, Severity: 16, The requested row is not in the fetch buffer.
Error: 16931, Severity: 16, There are no rows in the current fetch buffer.
Error: 16932, Severity: 16, The cursor has a FOR UPDATE list and the requested column to be updated is not in this list.

Error: 16933, Severity: 16, The cursor does not include the table being modified or the table is not updatable through the cursor.
Error: 16934, Severity: 10, Optimistic concurrency check failed. The row was modified outside of this cursor.
Error: 16935, Severity: 16, No parameter values were specified for the sp_cursor-%hs statement.
Error: 16936, Severity: 16, sp_cursor: One or more values parameters were invalid.
Error: 16937, Severity: 16, A server cursor cannot be opened on the given statement or statements. Use a default result set or client cursor.
Error: 16938, Severity: 16, sp_cursoropen/sp_cursorprepare: The statement parameter can only be a batch or a stored procedure with a single select, without FOR BROWSE, COMPUTE BY, or variable assignments.
Error: 16941, Severity: 16, Cursor updates are not allowed on tables opened with the NOLOCK option.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.


Leave a Reply

Your email address will not be published. Required fields are marked *