Tag: SQL Server Errors

SQL Server Error Msg 2398 – %sDuplicate id value found: ‘%ls’

SQL Server Error Msg 28031 – Connection handshake failed. An OS call failed: (%x) %ls. State %d.

SQL Server Error Msg 9101 – auto statistics internal

SQL Server Error Msg 5526 – The FILESTREAM log file ‘%.*ls’ cannot be removed because it is being referenced by a FILESTREAM data filegroup.

SQL Server Error Msg 45023 – %ls cannot be called on %S_MSG.

SQL Server Error Msg 6558 – %s failed because type ‘%s’ does not conform to %s specification due to method ‘%s’.

SQL Server Error Msg 14159 – Could not change property ‘%s’ for article ‘%s’ because there is an existing subscription to the article.

SQL Server Error Msg 16631 – Cannot delete sync member ‘%ls’ when it is syncing.

SQL Server Error Msg 21335 – Warning: column ‘%s’ already exists in the vertical partition.

SQL Server Error Msg Setting SYSTEM_VERSIONING to ON failed because history table ‘%.*ls’ has computed column specification. Consider dropping all computed column specifications and trying again. – 16

SQL Server Error Msg 21718 – For a COM resolver, the @resolver_clsid cannot be an empty string or NULL. Specify a valid value for @resolver_clsid.

SQL Server Error Msg 33554 – Encountered error 0x%08lx while waiting for encryption scan completion consensus. See the errorlog for details.

SQL Server Error Msg 8625 – Warning: The join order has been enforced because a local join hint is used.

SQL Server Error Msg 1702 – CREATE TABLE failed because column ‘%.*ls’ in table ‘%.*ls’ exceeds the maximum of %d columns.

SQL Server Error Msg 15100 – Usage: sp_bindefault defaultname, objectname [, ‘futureonly’]

SQL Server Error Msg 6397 – Path ‘%.*ls’ specified for selective XML index ‘%.*ls’ is too deep. The maximum allowed depth is %d levels.

SQL Server Error Msg 8677 – Cannot create the clustered index ‘%.*ls’ on view ‘%.*ls’ because it does not aggregate results. Consider changing the view definition.

SQL Server Error Msg 40926 – The operation cannot be performed because the geo-replication link is part of a Failover Group. You must remove the database from the group in order to individually terminate or failover.

SQL Server Error Msg 7646 – Fulltext predicate references columns from two different tables or indexed views ‘%.*ls’ and ‘%.*ls’ which is not allowed.

SQL Server Error Msg 22109 – The “context” argument for the CHANGE_TRACKING_CONTEXT WITH clause must be of type varbinary data type with a maximum length of 128.