SQL Server Errors or Failures Error: 658 to Error: 682

SQLServerF1

 

Error: 658, Severity: 16,
Could not enable support for %ls in database ‘%.*ls’ because %S_MSG.

Error: 659, Severity: 16,
Cannot disable %ls because a column or parameter of object id %d is collated in %ls. Please remove all references to that collation before disabling this feature.

Error: 660, Severity: 16,
Cannot disable %ls because database-default collation is %ls. Please remove all references to that collation before disabling this feature.

Error: 661, Severity: 16,
Cannot enable support for %ls in database ‘%.*ls’ because support for %ls is enabled and both are mutually exclusive.

Error: 662, Severity: 16,
Cannot disable %ls because a Selective XML Index exists on table id %d. Please drop all Selective XML Indexes before disabling this feature.

Error: 666, Severity: 16,
The maximum system-generated unique value for a duplicate group was exceeded for index with partition ID %I64d. Dropping and re-creating the index may resolve this; otherwise, use another clustering key.

Error: 667, Severity: 16,
The index “%.*ls” for table “%.*ls” (RowsetId %I64d) resides on a filegroup (“%.*ls”) that cannot be accessed because it is offline, is being restored, or is defunct.

Error: 669, Severity: 22,
The row object is inconsistent. Please rerun the query.

Error: 670, Severity: 16,
Large object (LOB) data for table “%.*ls” resides on an offline filegroup (“%.*ls”) that cannot be accessed.

Error: 671, Severity: 16,
Large object (LOB) data for table “%.*ls” resides on a read-only filegroup (“%.*ls”), which cannot be modified.

Error: 672, Severity: 10,
Failed to queue cleanup packets for orphaned rowsets in database “%.*ls”. Some disk space may be wasted. Cleanup will be attempted again on database restart.

Error: 674, Severity: 10,
Exception occurred in destructor of RowsetNewSS 0x%p. This error may indicate a problem related to releasing pre-allocated disk blocks used during bulk-insert operations. Restart the server to resolve this problem.

Error: 675, Severity: 10,
Worktable with partition ID %I64d was dropped successfully after %d repeated attempts.

Error: 676, Severity: 10,
Error occurred while attempting to drop worktable with partition ID %I64d.

Error: 677, Severity: 10,
Unable to drop worktable with partition ID %I64d after repeated attempts. Worktable is marked for deferred drop. This is an informational message only. No user action is required.

Error: 678, Severity: 10,
Active rowset for partition ID %I64d found at the end of the batch. This error may indicate incorrect exception handling. Use the current activity window in SQL Server Management Studio or the Transact-SQL KILL statement to terminate the server process id

Error: 679, Severity: 16,
One of the partitions of index ‘%.*ls’ for table ‘%.*ls'(partition ID %I64d) resides on a filegroup (“%.*ls”) that cannot be accessed because it is offline, restoring, or defunct. This may limit the query result.

Error: 680, Severity: 10,
Error [%d, %d, %d] occurred while attempting to drop allocation unit ID %I64d belonging to worktable with partition ID %I64d.

Error: 681, Severity: 16,
Attempting to set a non-NULL-able column’s value to NULL.

Error: 682, Severity: 16,
Internal error. Buffer provided to read column value is too small. Run DBCC CHECKDB to check for any corruption.

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 *