Tag: SQL Server Errors

SQL Server Error Msg 35327 – ALTER INDEX REBUILD statement failed because specifying %S_MSG is not allowed when rebuilding a columnstore index. Rebuild the columnstore index without specifying %S_MSG.

SQL Server Error Msg 7866 – XML attribute and element values larger than 4000 characters are only allowed within the SOAP Body node.

SQL Server Error Msg 27017 – Failed to drop index on reference table copy.

SQL Server Error Msg 10785 – The %S_MSG ‘%ls’ is supported only with %S_MSG.

SQL Server Error Msg 3139 – Restore to snapshot is not allowed with the master database.

SQL Server Error Msg 7873 – The endpoint “%.*ls” is a built-in endpoint and cannot be dropped. Use the protocol configuration utilities to ADD or DROP Transact-SQL endpoints.

SQL Server Error Msg 19409 – The Windows Server Failover Clustering (WSFC) cluster context of Always On Availability Groups has been changed to the local WSFC cluster. An ALTER SERVER CONFIGURATION SET HADR CLUSTER LOCAL command switched the cluster context from the remote WSFC cluster, ‘%.*ls’, to the local WSFC cluster. On this local WSFC cluster, availability databases no longer belong to any availability group, and they are transitioning to the RESTORING state. This is an informational message only. No user action is required.

SQL Server Error Msg 4921 – ALTER TABLE failed because trigger ‘%.*ls’ does not belong to table ‘%.*ls’.

SQL Server Error Msg 8035 – The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Table-valued parameter %d (“%.*ls”), row %I64d, column %d: Data type 0x%02X (sql_variant) has an invalid instance length.

SQL Server Error Msg 21792 – The table ‘%s.%s’ already appears in the transactional publication ‘%s’ on Publisher ‘%s’. The Oracle Gateway publishing option (the default) allows a table to be included as an article in any number of snapshot publications, but only in one transactional publication. To publish a table in more than one transactional publication, use the Oracle Complete publishing option. To change publishing options, you must drop and reconfigure the Publisher.

SQL Server Error Msg 13405 – The ability to use ‘@’ and names that start with ‘@@’ as Transact-SQL identifiers will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use it.

SQL Server Error Msg 18774 – The stored procedure %s must be executed within a transaction.

SQL Server Error Msg 35427 – set option

SQL Server Error Msg 11257 – A corrupted message has been received. The MIC and session key ID are in an invalid state. This occurred in the message with Conversation ID ‘%.*ls’, Initiator: %d, and Message sequence number: %I64d.

SQL Server Error Msg 35268 – Synchronization of a secondary database, ‘%.*ls’, was interrupted, leaving the database in an inconsistent state. The database will enter the RESTORING state. To complete recovery and bring the database online, use current log backups from the primary database to restore the log records past LSN %S_LSN. Alternatively, drop this secondary database, and prepare a new one by restoring a full database backup of the primary database followed by all subsequent log backups.

SQL Server Error Msg 16999 – Internal Cursor Error: The cursor is in an invalid state.

SQL Server Error Msg 41212 – No semantic language statistics database is registered.

SQL Server Error Msg 3992 – Transaction count has been changed from %d to %d inside of user defined routine, trigger or aggregate “%.*ls”. This is not allowed and user transaction will be rolled back. Change application logic to enforce strict transaction nesting.

SQL Server Error Msg 9641 – A cryptographic operation failed. This error indicates a serious problem with SQL Server. Check the SQL Server error log and the operating system error log for further information.

SQL Server Error Msg 8443 – The conversation with ID ‘%.*ls’ and initiator: %d references a missing conversation group ‘%.*ls’. Run DBCC CHECKDB to analyze and repair the database.