Tag: SQL Server Errors

SQL Server Error Msg 40925 – Can not connect to the database in its current state.

SQL Server Error Msg 46826 – Output parameters are not supported with %.*ls.

SQL Server Error Msg 45038 – CREATE DATABASE AS COPY OF %S_MSG is not supported.

SQL Server Error Msg 4806 – SINGLE_CLOB requires a double-byte character set (DBCS) (char) input file. The file specified is Unicode.

SQL Server Error Msg 1447 – ALTER DATABASE “%.*ls” command cannot be executed until both partner server instances are up, running, and connected. Start the partner and reissue the command.

SQL Server Error Msg 4408 – Too many tables. The query and the views or functions in it exceed the limit of %d tables. Revise the query to reduce the number of tables.

SQL Server Error Msg 27198 – Failed to locate records for the specified operation (ID %I64d).

SQL Server Error Msg 20711 – The dynamic filters property for publication ‘%s’ has been incorrectly set. Use sp_changemergepublication to reset the value to true if the publication uses parameterized filters and false if it does not.

SQL Server Error Msg 40617 – The firewall rule name that starts with ‘%.*ls’ is too long. Maximum length is %d.

SQL Server Error Msg 5553 – SQL Server internal error. FILESTREAM manager cannot continue with current command.

SQL Server Error Msg 17255 – Secondary TempDB file ‘%.*ls’ resides on a removable drive and therefore will not be attached during startup.

SQL Server Error Msg 9466 – XML parsing: line %d, character %d, XML namespace xml namespace URI (http://www.w3.org/XML/1998/namespace) must be assigned only to prefix ‘xml’.

SQL Server Error Msg 22834 – Could not modify the the verbose logging status for table %s. The failure occurred when executing the command ‘%s’. The error returned was %d: ‘%s’. Use the action and error to determine the cause of the failure and resubmit the request.

SQL Server Error Msg 5095 – A database or filegroup cannot be set to read-only mode when any files are subject to a RESTORE PAGE operation. Complete the restore sequence involving file “%ls” before attempting to transition to read-only.

SQL Server Error Msg 28074 – Service Broker could not upgrade conversation with conversation_handle ‘%ls’. Use END CONVERSATION … WITH CLEANUP to delete this conversation, then try again to enable the broker. Use ALTER DATABASE … SET ERROR_BROKER to error all conversations in this database. Use ALTER DATABASE … SET NEW_BROKER to delete all conversations in this database.

SQL Server Error Msg 18784 – The alternate snapshot folder path generated by replication has been truncated. Reconfigure the publication to use a shorter alternate snapshot folder path, and then retry the operation.

SQL Server Error Msg 30022 – Warning: The configuration of a full-text stoplist was modified using the WITH NO POPULATION clause. This put the full-text index into an inconsistent state. To bring the full-text index into a consistent state, start a full population. The basic Transact-SQL syntax for this is: ALTER FULLTEXT INDEX ON table_name START FULL POPULATION.

SQL Server Error Msg 7812 – The endpoint ‘%.*ls’ has been established in metadata, but HTTP listening has not been enabled because HTTP support did not start successfully. Verify that the operating system and the edition of SQL Server supports native HTTP access. Check the SQL Server error log for any errors that might have occurred while starting HTTP support.

SQL Server Error Msg Cannot create a row of size %d which is greater than the allowable maximum row size of %d. – 16

SQL Server Error Msg 20694 – One or more rows to be updated for table %s contain changes in the column %s, which is used in one or more filters; merge replication cannot use batch processing for these changes. No action is required, but if this condition occurs frequently, verify that data is partitioned optimally. Batch updates can improve the performance of merge replication.