Tag: SQL Server Errors

SQL Server Error Msg 4202 – BACKUP LOG is not possible because bulk logged changes exist in the database and one or more filegroups are unavailable.

SQL Server Error Msg 11299 – A corrupted message has been received. An unsequenced message had a non-zero sequence number. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.

SQL Server Error Msg Cannot create %S_MSG on a temporary object. – 15

SQL Server Error Msg 21649 – Cannot change the property ‘%s’. Non-SQL Server Publishers do not support this property.

SQL Server Error Msg Cannot use the OUTPUT option when passing a constant to a stored procedure. – 15

SQL Server Error Msg 8419 – Both the error code and the description must be provided for END CONVERSATION WITH ERROR. Neither value can be NULL.

SQL Server Error Msg 3280 – Backups on raw devices are not supported. ‘%ls’ is a raw device.

SQL Server Error Msg 22949 – Could not update the Change Data Capture metadata for capture instance ‘%s’ and source table ‘%s.%s’. Refer to previous errors in the current session to identify the cause and correct any associated problems.

SQL Server Error Msg 2761 – The ROWGUIDCOL property can only be specified on the uniqueidentifier data type.

SQL Server Error Msg 9910 – Warning: Error occurred during full-text %ls population for table or indexed view ‘%ls’, database ‘%ls’ (table or indexed view ID ‘%d’, database ID ‘%d’). Error: %ls.

SQL Server Error Msg 20555 – 6.x publication.

SQL Server Error Msg 15187 – The %S_MSG cannot be dropped because it is used by one or more %S_MSG(s).

SQL Server Error Msg 22901 – The database ‘%s’ is not enabled for Change Data Capture. Ensure that the correct database context is set and retry the operation. To report on the databases enabled for Change Data Capture, query the is_cdc_enabled column in the sys.databases catalog view.

SQL Server Error Msg 14269 – Job ‘%s’ is already targeted at server ‘%s’.

SQL Server Error Msg 13923 – Pseudocolumn ‘%.*s’ is invalid because it references a node or edge table that is not in the current database.

SQL Server Error Msg 45190 – ‘%ls’ is an invalid name because it contains one or more unsupported unicode characters.

SQL Server Error Msg 9654 – Attempting to use database and it doesn’t exist.

SQL Server Error Msg 34017 – Automated policies cannot reference conditions that contain script.

SQL Server Error Msg 5338 – Format option cannot be specified together with SINGLE_BLOB, SINGLE_CLOB or SINGLE_NCLOB option.

SQL Server Error Msg 2005 – The table ‘%.*ls’ is unavailable and needs to be rebuilt. Rebuild the table offline.