SQL Server Errors or Failures from Error: 16963 to Error: 17057

SQLServerF1

 

Error: 16963, Severity: 16, You cannot specify scroll locking on a cursor that contains a remote table.
Error: 16964, Severity: 16, For the optimistic cursor, timestamp columns are required if the update or delete targets are remote.
Error: 16965, Severity: 16, Cursor scroll locks were invalidated due to a transaction defect. Reissue the UPDATE or DELETE statement after a cursor fetch.
Error: 16966, Severity: 16, %ls: Specified concurrency control option %d (%ls) is incompatible with static or fast forward only cursors. Only read-only is compatible with static or fast forward only cursors.

Error: 16992, Severity: 16, The cursor operation is required to wait for cursor asynchronous population to complete. However, at this point the transaction cannot be yielded to let the asynchronous population to continue.
Error: 16996, Severity: 16, %ls cannot take output parameters.
Error: 16998, Severity: 16, The asynchronous cursor worktable population thread spawn failed.
Error: 16999, Severity: 20, Internal Cursor Error: The cursor is in an invalid state.
Error: 17000, Severity: 10, Usage: sp_autostats
[, {ON|OFF} [, ] ]

Error: 17001, Severity: 16, Failure to send an event notification instance of type ‘%s’ on conversation handle ‘%s’. Error Code = ‘%s’.
Error: 17002, Severity: 16, Failed to post QUEUE_ACTIVATION event. Error code: ‘0x%s’.
Error: 17003, Severity: 16, Closed event notification conversation endpoint with handle ‘%s’, due to the following error: ‘%.*ls’.
Error: 17004, Severity: 16, Event notification conversation on dialog handle ‘%s’ closed without an error.
Error: 17005, Severity: 16, Event notification ‘%ls’ in database ‘%ls’ dropped due to send time service broker errors. Check to ensure the conversation handle, service broker contract, and service specified in the event notification are active.
Error: 17049, Severity: 16, Unable to cycle error log file from ‘%ls’ to ‘%ls’ due to OS error ‘%s’. A process outside of SQL Server may be preventing SQL Server from reading the files. As a result, errorlog entries may be lost and it may not be possible to view some SQL Server erro
Error: 17051, Severity: 16, SQL Server evaluation period has expired.
Error: 17053, Severity: 16, %ls: Operating system error %ls encountered.
Error: 17054, Severity: 16, The current event was not reported to the Windows Events log. Operating system error = %s. You may need to clear the Windows Events log if it is full.
Error: 17056, Severity: 10, The evaluation period for your edition of SQL Server expires in %d day(s).
Error: 17057, Severity: 16, Security context for operating system objects could not be created. SQL Server cannot be started. Look for corresponding entries in the event viewer to help diagnose the root cause.

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.

Thanks,
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 *