SQL Server Errors or Failures from Error: 22511 to Error: 22530

SQLServerF1

 

Error: 22511, Severity: 16, The merge completed successfully.
Error: 22512, Severity: 16, Cannot use partition groups with unfiltered publications. Set “use_partition_groups” to “false” using sp_changemergepublication.
Error: 22513, Severity: 16, Cannot use partition groups because the join filter between the following articles contains one or more functions: “%s” and “%s”.
Error: 22514, Severity: 16, Cannot use partition groups because one or more filters reference the following view, which contains functions: “%s”.

Error: 22515, Severity: 16, The publication cannot use precomputed partitions because there is at least one circular reference in the join filters specified for the articles in the publication. To use precomputed partitions, ensure that no circular join filter relationships exist.
Error: 22516, Severity: 16, The publication “%s” was defined as having dynamic filters, but it does not contain any dynamic filters.
Error: 22517, Severity: 16, The publication was defined as having no dynamic filters, but contains one or more dynamic filters.

Error: 22518, Severity: 16, Cannot use column of type image, ntext, xml, CLR type, varchar(max), nvarchar(max), or varbinary(max) in a subset or join filter for article: ‘%s’.
Error: 22519, Severity: 16, Cannot add a logical record relationship between tables “%s” and “%s” because a text, image, ntext, xml, varchar(max), nvarchar(max), or varbinary(max) column was referenced in the join clause.
Error: 22520, Severity: 10, A filtering type changed for the article. Any pending or future changes made in this article by a Subscriber in a given partition will no longer be propagated to Subscribers in other partitions. Check the documentation for details.
Error: 22521, Severity: 10, Unable to synchronize the row because the row was updated by a different process outside of replication.
Error: 22522, Severity: 16, Article ‘%s’ cannot be published because it is published in another merge publication. An article that has a value of 3 for the @partition_options parameter of sp_addmergearticle (nonoverlapping partitions with a single subscription per partition) cannot
Error: 22523, Severity: 16, An article cannot use @partition_options 2 or 3 (nonoverlapping partitions) and be a part of a logical record relationship at the same time. Check article “%s”.
Error: 22524, Severity: 16, Article ‘%s’ is published in another merge publication, with a different value specified for the @partition_options parameter of sp_addmergearticle. The specified value must be the same in all merge publications. Either specify the same value as the exist
Error: 22525, Severity: 16, The publication “%s” cannot allow multiple subscriptions per partition if it contains articles using @partition_options = 3.
Error: 22526, Severity: 16, An invalid value was specified for %s. Valid values are 0 (none), 1 (enforced partitions), 2 (nonoverlapping partitions with multiple subscriptions per partition), and 3 (nonoverlapping partitions with single subscription per partition).
Error: 22527, Severity: 16, Invalid value specified for %s. Valid values are ‘day’, ‘days’, ‘dd’, ‘year’, ‘years’, ‘yy’, ‘yyyy’, ‘month’, ‘months’, ‘mm’, ‘week’, ‘weeks’, ‘wk’, ‘hour’, ‘hours’, ‘hh’, ‘minute’, ‘minutes’, ‘mi’.
Error: 22528, Severity: 16, Cannot use a retention period unit other than “days” for publication “%s” because the compatibility level of the publication is lower than 90. Use sp_changemergepublication to set publication_compatibility_level to 90RTM.
Error: 22529, Severity: 16, Cannot change the retention period unit for publication “%s” because the compatibility level of the publication is lower than 90. Use sp_changemergepublication to set publication_compatibility_level to 90RTM.
Error: 22530, Severity: 16, Cannot update any column in article “%s” that is used in a logical record relationship clause.

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: 7369 to Error: 7401

SQLServerF1

 

Error: 7369, Severity: 16, The OLE DB provider ‘%ls’ for linked server ‘%ls’ provided invalid collation. LCID = %08x, Compflags = %08x, SortOrder = ‘%.*ls’.
Error: 7370, Severity: 16, One or more properties could not be set on the query for OLE DB provider “%ls” for linked server “%ls”. %ls
Error: 7371, Severity: 16, The server option ‘collation name’ in linked server ‘%ls’ for OLE DB provider ‘%ls’ has collation id %08x which is not supported by SQL Server.
Error: 7372, Severity: 16, Cannot get properties from OLE DB provider “%ls” for linked server “%ls”.

Error: 7373, Severity: 16, Cannot set the initialization properties for OLE DB provider “%ls” for linked server “%ls”.
Error: 7374, Severity: 16, Cannot set the session properties for OLE DB provider “%ls” for linked server “%ls”.
Error: 7375, Severity: 16, Cannot open index “%ls” on table “%ls” from OLE DB provider “%ls” for linked server “%ls”. %ls
Error: 7376, Severity: 16, Could not enforce the remote join hint for this query.
Error: 7377, Severity: 16, Cannot specify an index hint for a remote data source.
Error: 7380, Severity: 16, Table-valued parameters are not allowed in remote calls between servers.

Error: 7390, Severity: 16, The requested operation could not be performed because OLE DB provider “%ls” for linked server “%ls” does not support the required transaction interface.
Error: 7391, Severity: 16, The operation could not be performed because OLE DB provider “%ls” for linked server “%ls” was unable to begin a distributed transaction.
Error: 7392, Severity: 16, Cannot start a transaction for OLE DB provider “%ls” for linked server “%ls”.
Error: 7393, Severity: 16, The OLE DB provider “%ls” for linked server “%ls” reported an error 0x%08X aborting the current transaction.
Error: 7394, Severity: 16, The OLE DB provider “%ls” for linked server “%ls” reported an error committing the current transaction.
Error: 7395, Severity: 16, Unable to start a nested transaction for OLE DB provider “%ls” for linked server “%ls”. A nested transaction was required because the XACT_ABORT option was set to OFF.
Error: 7396, Severity: 16, Varchar(max), nvarchar(max), varbinary(max) and large CLR type data types are not supported as return value or output parameter to remote queries.
Error: 7397, Severity: 16, Remote function returned varchar(max), nvarchar(max), varbinary(max) or large CLR type value which is not supported.
Error: 7399, Severity: 16, The OLE DB provider “%ls” for linked server “%ls” reported an error. %ls
Error: 7401, Severity: 16, The OLE DB provider “%ls” returned invalid literal prefix/suffix string.

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: 5310 to Error: 5331

SQLServerF1

 

Error: 5310, Severity: 16, Aggregates are not allowed in the VALUES list of an INSERT statement.
Error: 5311, Severity: 16, Invalid quote character ‘%lc’. A remote server or user command used an invalid quote character.
Error: 5312, Severity: 16, The input to the function ‘ntile’ cannot be bound.
Error: 5313, Severity: 16, Synonym ‘%.*ls’ refers to an invalid object.
Error: 5315, Severity: 16, The target of a MERGE statement cannot be a remote table, a remote view, or a view over remote tables.
Error: 5316, Severity: 16, The target ‘%.*ls’ of the MERGE statement has an INSTEAD OF trigger on some, but not all, of the actions specified in the MERGE statement. In a MERGE statement, if any action has an enabled INSTEAD OF trigger on the target, then all actions must have enab

Error: 5317, Severity: 16, The target of a MERGE statement cannot be a partitioned view.
Error: 5318, Severity: 16, In a MERGE statement, the source and target cannot have the same name or alias. Use different aliases for the source and target to ensure that they have unique names in the MERGE statement.
Error: 5319, Severity: 16, Aggregates are not allowed in a WHEN clause of a MERGE statement.
Error: 5321, Severity: 16, The ‘%ls’ function is not allowed in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
Error: 5322, Severity: 16, An aggregate function is not allowed in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
Error: 5323, Severity: 15, Subqueries are not allowed in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.

Error: 5324, Severity: 15, In a MERGE statement, a ‘%S_MSG’ clause with a search condition cannot appear after a ‘%S_MSG’ clause with no search condition.
Error: 5325, Severity: 15, The order of the data in the data file does not conform to the ORDER hint specified for the BULK rowset ‘%.*ls’. The order of the data must match the order specified in the ORDER hint for a BULK rowset. Update the ORDER hint to reflect the order in which
Error: 5326, Severity: 15, The data in the data file does not conform to the UNIQUE hint specified for the BULK rowset ‘%.*ls’. The data in the data file must be unique if the UNIQUE hint is specified for a BULK rowset. Remove the UNIQUE hint, or update the input data file to ensur
Error: 5327, Severity: 15, The column ‘%.*ls’ does not have a valid data type for the ORDER hint specified for data source ‘%.*ls’. The text, ntext, image, xml, varchar(max), nvarchar(max) and varbinary(max) data types cannot be used in the ORDER hint for a BULK rowset or CLR TVF.
Error: 5328, Severity: 15, Cannot insert explicit value for the identity column ‘%.*ls’ in the target table ‘%.*ls’ of the INSERT statement when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
Error: 5329, Severity: 15, Windowed functions are not allowed in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
Error: 5330, Severity: 16, Full-text predicates cannot appear in the OUTPUT clause.
Error: 5331, Severity: 16, Full-text predicates cannot appear in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.

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: 1709 to Error: 1728

SQLServerF1

 

Error: 1709, Severity: 16,
Cannot use TEXTIMAGE_ON when a table has no text, ntext, image, varchar(max), nvarchar(max), non-FILESTREAM varbinary(max), xml or large CLR type columns.

Error: 1710, Severity: 10,
Cannot use alias type with rule or default bound to it as a column type in table variable or return table definition in table valued function. Type ‘%.*ls’ has a %S_MSG bound to it.

Error: 1711, Severity: 16,
Cannot define PRIMARY KEY constraint on column ‘%.*ls’ in table ‘%.*ls’. The computed column has to be persisted and not nullable.

Error: 1712, Severity: 16,
Online index operations can only be performed in Enterprise edition of SQL Server.

Error: 1713, Severity: 16,
Cannot execute %ls on/using table ‘%.*ls’ since the table is the target table or part of cascading actions of a currently executing trigger.

Error: 1714, Severity: 16,
Altr table failed because unique column IDs have been exhausted for table ‘%.*ls’.

Error: 1715, Severity: 16,
Foreign key ‘%.*ls’ creation failed. Only NO ACTION referential update action is allowed for referencing computed column ‘%.*ls’.

Error: 1716, Severity: 16,
FILESTREAM_ON cannot be specified when a table has no FILESTREAM columns. Remove the FILESTREAM_ON clause from the statement, or add a FILESTREAM column to the table.

Error: 1717, Severity: 16,
FILESTREAM_ON cannot be specified together with a partition scheme in the ON clause.

Error: 1718, Severity: 16,
Change tracking must be enabled on database ‘%.*ls’ before it can be enabled on table ‘%.*ls’.

Error: 1719, Severity: 16,
FILESTREAM data cannot be placed on an empty filegroup.

Error: 1720, Severity: 16,
Cannot drp FILESTREAM filegroup or partition scheme since table ‘%.*ls’ has FILESTREAM columns.

Error: 1721, Severity: 16,
Altering table ‘%.*ls’ failed because the row size using vardecimal storage format exceeds the maximum allowed table row size of %d bytes.

Error: 1722, Severity: 16,
Cannot %S_MSG %S_MSG ‘%.*ls’ since a partition scheme is not specified for FILESTREAM data.

Error: 1723, Severity: 16,
Cannot %S_MSG %S_MSG ‘%.*ls’ since a partition scheme was specified for FILESTREAM data but not for the table.

Error: 1724, Severity: 16,
Filegroup ‘%.*ls’ is not a FILESTREAM filegroup or partition scheme of FILESTREAM filegroups.

Error: 1725, Severity: 16,
Cannot add FILESTREAM column to %S_MSG ‘%.*ls’ because an INSTEAD OF trigger exists on the %S_MSG.

Error: 1726, Severity: 16,
Cannot add FILESTREAM filegroup or partition scheme since table ‘%.*ls’ has a FILESTREAM filegroup or partition scheme already.

Error: 1727, Severity: 16,
Cannot create non-clustered index ‘%.*ls’ on table ‘%.*ls’ with the FILESTREAM_ON clause.

Error: 1728, Severity: 16,
Cannot create index ‘%.*ls’ on table ‘%.*ls’ because the computed column ‘%.*ls’ uses a FILESTREAM column.

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.