SQL Server Errors or Failures from Error: 28102 to Error: 30025

SQLServerF1

Error: 28102, Severity: 16, Batch execution is terminated because of debugger request.

Error: 28201, Severity: 10, SQLSQM.EXE cannot be launched. This can either be caused if the required information in the registry is missing or corrupted or SQLSQM.EXE cannot be found.
Error: 29001, Severity: 16, To connect to this server you must use SQL Server Management Studio or SQL Server Management Objects (SMO).
Error: 29003, Severity: 16, Invalid parameter combinations.
Error: 29004, Severity: 16, Unknown property specified: %s.
Error: 29801, Severity: 16, GDM request processing failed. See previous error for details.
Error: 29802, Severity: 16, GDM failed to allocate message via communication stack API.
Error: 29803, Severity: 10, Global Deadlock Monitor is inactive. This is an informational message only. No user action is required.

Error: 30003, Severity: 16, A fulltext system view or stvf cannot open database id %d.
Error: 30004, Severity: 16, A fulltext system view or stvf cannot open user table object id %d.
Error: 30005, Severity: 16, The name specified for full-text index fragment %.*ls is not valid.
Error: 30006, Severity: 16, A fulltext system view or stvf cannot open fulltext index for user table object id %d.
Error: 30007, Severity: 16, Parameters of dm_fts_index_keywords, dm_fts_index_keywords_by_document, and dm_fts_index_keywords_by_property cannot be null.
Error: 30008, Severity: 16, This is an internal error when invoking the TVF to access the full-text index. The level number specified for the TVF is not valid. Valid level numbers start from 0 and must be less than the number of levels of the compressed index.
Error: 30009, Severity: 16, The argument data type ‘%ls’ specified for the full-text query is not valid. Allowed data types are char, varchar, nchar, nvarchar.

Error: 30020, Severity: 16, The full-text query parameter for %S_MSG is not valid.
Error: 30022, Severity: 10, 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
Error: 30023, Severity: 16, The fulltext stoplist ‘%.*ls’ does not exist or the current user does not have permission to perform this action. Verify that the correct stoplist name is specified and that the user had the permission required by the Transact-SQL statement.
Error: 30024, Severity: 16, The fulltext stoplist ‘%.*ls’ already exists in the current database. Duplicate stoplist names are not allowed. Rerun the statement and specify a unique stoplist name.
Error: 30025, Severity: 16, The search property list ‘%.*ls’ does not exist or you do not have permission to perform this action. Verify that the correct search property list name is specified and that you have the permission required by the Transact-SQL statement. For a list of the

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 

SQL Server Errors or Failures from Error: 8179 to Error: 8302

SQLServerF1

 

Error: 8179, Severity: 16, Could not find prepared statement with handle %d.
Error: 8180, Severity: 16, Statement(s) could not be prepared.
Error: 8181, Severity: 16, Text for ‘%.*ls’ is missing from the system catalog. The object must be dropped and re-created before it can be used.
Error: 8183, Severity: 16, Only UNIQUE or PRIMARY KEY constraints can be created on computed columns, while CHECK, FOREIGN KEY, and NOT NULL constraints require that computed columns be persisted.
Error: 8184, Severity: 16, Error in binarychecksum. There are no comparable columns in the binarychecksum input.

Error: 8185, Severity: 16, Error expanding “*”: An incomparable column has been found in an underlying table or view.
Error: 8186, Severity: 16, Function ‘%.*ls’ can be used only on user and system tables.
Error: 8187, Severity: 16, The prepared handle %d is currently being used by another command (error state: %d).
Error: 8188, Severity: 16, There is already a SQL type for assembly type “%.*ls” on assembly “%.*ls”. Only one SQL type can be mapped to a given assembly type. CREATE TYPE fails.
Error: 8189, Severity: 16, You do not have permission to run ‘%ls’.
Error: 8190, Severity: 16, Cannot compile replication filter procedure without defining table being filtered.

Error: 8191, Severity: 16, Replication filter procedures can only contain SELECT, GOTO, IF, WHILE, RETURN, and DECLARE statements.
Error: 8192, Severity: 16, Replication filter procedures cannot have parameters.
Error: 8193, Severity: 16, Cannot execute a procedure marked FOR REPLICATION.
Error: 8195, Severity: 16, Cannot create “%.*ls” on “%.*ls”. Insert, Update, and Delete triggers can only be created on user tables and views.
Error: 8196, Severity: 16, Duplicate column specified as ROWGUIDCOL.
Error: 8197, Severity: 16, The object ‘%.*ls’ does not exist or is invalid for this operation.
Error: 8199, Severity: 16, In EXECUTE , procname can only be a literal or variable of type char, varchar, nchar, or nvarchar.
Error: 8301, Severity: 10, Use of level0type with value ‘USER’ in procedure sp_addextendedproperty, sp_updateextendedproperty and sp_dropextendedproperty and in table-valued function fn_listextendedproperty has been deprecated and will be removed in a future version of SQL Server.
Error: 8302, Severity: 10, CREATE RULE and DROP RULE will be removed in a future version of SQL Server. Avoid using CREATE RULE and DROP RULE in new development work, and plan to modify applications that currently use them. Use check constraints instead, which are created using the

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 

SQL Server Errors or Failures from Error: 6611 to Error: 6717

SQLServerF1

 

Error: 6611, Severity: 16, The XML data type is damaged.
Error: 6613, Severity: 16, Specified value ‘%ls’ already exists.
Error: 6621, Severity: 16, XML encoding or decoding error occurred with object name ‘%.*ls’.
Error: 6622, Severity: 16, Invalid data type for column “%ls”. The data type cannot be text, ntext, image, binary, varchar(max), nvarchar(max), varbinary(max), or xml.
Error: 6623, Severity: 16, Column ‘%ls’ contains an invalid data type. Valid data types are char, varchar, nchar, and nvarchar.
Error: 6624, Severity: 16, XML document could not be created because server memory is low. Use sp_xml_removedocument to release XML documents.

Error: 6625, Severity: 16, Could not convert the value for OPENXML column ‘%ls’ to sql_variant data type. The value is too long. Change the data type of this column to text, ntext or image.
Error: 6626, Severity: 16, Unexpected end of data stream.
Error: 6627, Severity: 16, The size of the data chunk that was requested from the stream exceeds the allowed limit.
Error: 6628, Severity: 16, %.*ls can only process untyped XML. Cast the input value to XML or to a string type.
Error: 6629, Severity: 16, The result of the column expression for column “%ls” is not compatible with the requested type “XML”. The result must be an element, text node, comment node, processing instruction, or document node.
Error: 6630, Severity: 16, Element-centric mapping must be used with OPENXML when one of the columns is of type XML.
Error: 6631, Severity: 16, The requested OpenXML document is currently in use by another thread, and cannot be used.

Error: 6632, Severity: 16, Invalid data type for the column “%ls”. CLR types cannot be used in an OpenXML WITH clause.
Error: 6633, Severity: 16, The version of MSXMLSQL.DLL that was found is older than the minimum required version. Found version “%d.%d.%d”. Require version “%d.%d.%d”.
Error: 6634, Severity: 16, OpenXML cannot be used as the target of a DML or OUTPUT INTO operation.
Error: 6700, Severity: 16, XQuery: The ‘ %ls’ operation is not supported.
Error: 6701, Severity: 16, The version of the XML index that you are trying to use is not supported anymore. Please drop and recreate the XML index.
Error: 6716, Severity: 16, XML Node ID is invalid. Re-build the database if the problem persists.
Error: 6717, Severity: 16, XQuery: The document tree is too deep. If the problem persists you must simplify the XML hierarchy.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 

SQL Server Errors or Failures from Error: 3903 to Error: 3925

SQLServerF1

 

Error: 3903, Severity: 16, The ROLLBACK TRANSACTION request has no corresponding BEGIN TRANSACTION.
Error: 3904, Severity: 21, Cannot unsplit logical page %S_PGID in object ‘%.*ls’, in database ‘%.*ls’. Both pages together contain more data than will fit on one page.
Error: 3906, Severity: 16, Failed to update database “%.*ls” because the database is read-only.
Error: 3908, Severity: 16, Could not run BEGIN TRANSACTION in database ‘%.*ls’ because the database is in emergency mode or is damaged and must be restarted.
Error: 3909, Severity: 16, Session binding token is invalid.

Error: 3910, Severity: 16, Transaction context in use by another session.
Error: 3912, Severity: 16, Cannot bind using an XP token while the server is not in an XP call.
Error: 3913, Severity: 16, TDS reset connection protocol error. Client driver requested both ResetConnectionKeepLocalXact and ResetConnectionKeepDTCXact at the same time. This is not expected in server.
Error: 3914, Severity: 16, The data type “%s” is invalid for transaction names or savepoint names. Allowed data types are char, varchar, nchar, varchar(max), nvarchar, and nvarchar(max).
Error: 3915, Severity: 16, Cannot use the ROLLBACK statement within an INSERT-EXEC statement.

Error: 3916, Severity: 16, Cannot use the COMMIT statement within an INSERT-EXEC statement unless BEGIN TRANSACTION is used first.
Error: 3917, Severity: 16, Session is bound to a transaction context that is in use. Other statements in the batch were ignored.
Error: 3918, Severity: 16, The statement or function must be executed in the context of a user transaction.
Error: 3919, Severity: 16, Cannot enlist in the transaction because the transaction has already been committed or rolled back.
Error: 3920, Severity: 10, The WITH MARK option only applies to the first BEGIN TRAN WITH MARK statement. The option is ignored.
Error: 3921, Severity: 16, Cannot get a transaction token if there is no transaction active. Reissue the statement after a transaction has been started
Error: 3922, Severity: 16, Cannot enlist in the transaction because the transaction does not exist.
Error: 3923, Severity: 10, Cannot use transaction marks on database ‘%.*ls’ with bulk-logged operations that have not been backed up. The mark is ignored.
Error: 3924, Severity: 10, The session was enlisted in an active user transaction while trying to bind to a new transaction. The session has defected from the previous user transaction.
Error: 3925, Severity: 16, Invalid transaction mark name. The ‘LSN:’ prefix is reserved.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 

SQL Server Errors or Failures Error: 268 to Error: 289

SQLServerF1

You may receive various errors in SQL Server while working. Below are some of the SQL Server Errors from Error: 268 to Error: 289

Error: 268, severity 16,
Cannot run SELECT INTO in this database. The database owner must run sp_dboption to enable this option.

Error: 270, severity 16,
Object ‘%.*ls’ cannot be modified.

Error: 271, severity 16,
The column “%.*ls” cannot be modified because it is either a computed column or is the result of a UNION operator.

Error: 272, severity 16,
Cannot update a timestamp column.

Error: 273, severity 16,
Cannot insert an explicit value into a timestamp column. Use INSERT with a column list to exclude the timestamp column, or insert a DEFAULT into the timestamp column.

Error: 275, severity 16,
Prefixes are not allowed in value or pivot columns of an UNPIVOT operator.

Error: 276, severity 16,
Pseudocolumns are not allowed as value or pivot columns of an UNPIVOT operator.

Error: 277, severity 16,
The column “%.*ls” is specified multiple times in the column list of the UNPIVOT operator.

Error: 278, severity 16,
The text, ntext, and image data types cannot be used in a GROUP BY clause.

Error: 279, severity 16,
The text, ntext, and image data types are invalid in this subquery or aggregate expression.

Error: 280, severity 16,
Only base table columns are allowed in the TEXTPTR function.

Error: 281, severity 16,
%d is not a valid style number when converting from %ls to a character string.

Error: 282, severity 10,
The ‘%.*ls’ procedure attempted to return a status of NULL, which is not allowed. A status of 0 will be returned instead.

Error: 283, severity 16,
READTEXT cannot be used on inserted or deleted tables within an INSTEAD OF trigger.

Error: 284, severity 16,
Rules cannot be bound to text, ntext, or image data types.

Error: 285, severity 16,
The READTEXT, WRITETEXT, and UPDATETEXT statements cannot be used with views or functions.

Error: 286, severity 16,
The logical tables INSERTED and DELETED cannot be updated.

Error: 287, severity 16,
The %ls statement is not allowed within a trigger.

Error: 288, severity 16,
The PATINDEX function operates on char, nchar, varchar, nvarchar, text, and ntext data types only.

Error: 289, severity 16,
Cannot construct data type %ls, some of the arguments have values which are not valid.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.