Tag: SQL Server Errors

SQL Server Error Msg 4303 – The roll forward start point is now at log sequence number (LSN) %.*s. Additional roll forward past LSN %.*s is required to complete the restore sequence.

SQL Server Error Msg 10730 – A nested INSERT, UPDATE, DELETE, or MERGE statement is not allowed in the FROM clause of an UPDATE or DELETE statement.

SQL Server Error Msg 41632 – The system encountered SQL Error %d (severity: %d, state: %d), which has no corresponding error text.  Refer to the SQL Error number for more information regarding the cause and corrective action.

SQL Server Error Msg 16014 – Failed to create fulltext index because key column ‘%.*ls’ has a masking function defined on it.

SQL Server Error Msg 14568 – (above normal)

SQL Server Error Msg 33041 – Cannot create login token for existing authenticators. If dbo is a windows user make sure that its windows account information is accessible to SQL Server.

SQL Server Error Msg 40554 – Exiting because of XEvent %ls.

SQL Server Error Msg 9500 – The data type ‘%.*ls’ used in the VALUE method is invalid.

SQL Server Error Msg 17659 – Warning: System table ID %d has been updated directly in database ID %d and cache coherence may not have been maintained. SQL Server should be restarted.

SQL Server Error Msg 39127 – External script execution for ‘%.*s’ script ran out of resources. External script request id is: %s.

SQL Server Error Msg 46654 – database scoped credential

SQL Server Error Msg 12106 – The path name ‘%.*ls’ is already used by another database file. Change to another valid and UNUSED name.

SQL Server Error Msg 28702 – Request aborted due to communication errors: incoming message format violation.

SQL Server Error Msg 16007 – The column ‘%.*ls’ does not have a data masking function.

SQL Server Error Msg 7002 – OPENXML XPath must be of a string data type, such as nvarchar.

SQL Server Error Msg 45371 – Cannot cancel management operation ‘%ls’ in the current state.%ls

SQL Server Error Msg 11325 – Multiple Active Result Sets (MARS) and bound sessions are not supported inside ATOMIC blocks.

SQL Server Error Msg 35260 – During an attempted database recovery, an availability database manager was not found for database id %d with availability group ID %d and group database ID %ls.  Recovery was terminated. The most likely cause of this error is that the availability group manager is not running, but the cause could be a metadata error. Ensure that the availability group manager and the WSFC cluster are started, and retry the recovery operation.

SQL Server Error Msg 8384 – Use of space as a separator for table hints is a deprecated feature and will be removed in a future version. Use a comma to separate individual table hints.

SQL Server Error Msg 40067 – Corrupted row sequence.