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: 8391 to Error: 8413

SQLServerF1

 

Error: 8391, Severity: 10, The usage of 2-part names in DROP INDEX is deprecated. New-style syntax DROP INDEX ON { | }
Error: 8393, Severity: 10, The ability to not specify a column name when the datatype is timestamp 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.
Error: 8394, Severity: 10, Usage of deprecated index option syntax. The deprecated relational index option syntax structure will be removed in a future version of SQL Server. Avoid using this syntax structure in new development work, and plan to modify applications that currently u

Error: 8396, Severity: 10, %ls 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. Use %ls instead.
Error: 8397, Severity: 10, The TEXT, NTEXT, and IMAGE data types will be removed in a future version of SQL Server. Avoid using them in new development work, and plan to modify applications that currently use them. Use the varchar(max), nvarchar(max), and varbinary(max) data types
Error: 8398, Severity: 10, The use of more than two-part column names 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.
Error: 8399, Severity: 10, %ls 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.

Error: 8401, Severity: 16, This message could not be delivered because the target user with ID %i in database ID %i does not have permission to receive from the queue ‘%.*ls’.
Error: 8402, Severity: 16, The data type of the ‘%S_MSG’ in the ‘%S_MSG’ statement must be %s. The %s data type is not allowed.
Error: 8403, Severity: 16, The message type ‘%.*ls’ is specified more than once. Remove the duplicate message type.
Error: 8404, Severity: 16, The service contract ‘%.*ls’ is specified more than once. Remove the duplicate service contract.
Error: 8405, Severity: 16, An error occurred in the service broker queue rollback handler, while trying to disable a queue. Database ID: %d, Queue ID: %d, Error: %i, State: %i.
Error: 8406, Severity: 16, The dialog lifetime can not be NULL. Specify a valid dialog lifetime value from %d to %d.
Error: 8407, Severity: 16, Received a message that contains invalid header fields. This may indicate a network problem or that another application is connected to the Service Broker endpoint.
Error: 8408, Severity: 16, Target service ‘%.*ls’ does not support contract ‘%.*ls’.
Error: 8409, Severity: 16, This message could not be delivered because the targeted service does not support the service contract. Targeted service: ‘%.*ls’, service contract: ‘%.*ls’.
Error: 8410, Severity: 16, The conversation timer cannot be set beyond the conversation’s lifetime.
Error: 8411, Severity: 16, The dialog lifetime value of %d is outside the allowable range of %d to %d. Specify a valid dialog lifetime value.
Error: 8412, Severity: 16, The syntax of the service name ‘%.*ls’ is invalid.
Error: 8413, Severity: 16, The syntax of the broker instance ‘%.*ls’ is invalid. The specified broker instance is too long, the maximum size is 256 bytes.

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: 4988 to Error: 5009

SQLServerF1

 

Error: 4988, Severity: 16, Cannot persist computed column ‘%.*ls’. Underlying object ‘%.*ls’ has a different owner than table ‘%.*ls’.
Error: 4989, Severity: 16, Cannot drop the ROWGUIDCOL property for column ‘%.*ls’ in table ‘%.*ls’ because the column is not the designated ROWGUIDCOL for the table.
Error: 4990, Severity: 16, Cannot alter column ‘%.*ls’ in table ‘%.*ls’ to add or remove the FILESTREAM column attribute.
Error: 4991, Severity: 16, Cannot alter NOT FOR REPLICATION attribute on column ‘%.*ls’ in table ‘%.*ls’ because this column is not an identity column.
Error: 4992, Severity: 16, Cannot use table option LARGE VALUE TYPES OUT OF ROW on a user table that does not have any of large value types varchar(max), nvarchar(max), varbinary(max), xml or large CLR type columns in it. This option can be applied to tables having large values com

Error: 4993, Severity: 16, ALTR TABLE SWITCH statement failed. The table ‘%.*ls’ has different setting for Large Value Types Out Of Row table option as compared to table ‘%.*ls’.
Error: 4994, Severity: 16, Computed column ‘%.*ls’ in table ‘%.*ls’ cannot be persisted because the column type, ‘%.*ls’, is a non-byte-ordered CLR type.
Error: 4995, Severity: 16, Vardecimal storage format cannot be enabled on table ‘%.*ls’ because database ‘%.*ls’ is a system database. Vardecimal storage format is not available in system databases.
Error: 4996, Severity: 16, Change tracking is already enabled for table ‘%.*ls’.
Error: 4997, Severity: 16, Cannot enable change tracking on table ‘%.*ls’. Change tracking requires a primary key on the table. Create a primary key on the table before enabling change tracking.
Error: 4998, Severity: 16, Change tracking is not enabled on table ‘%.*ls’.

Error: 4999, Severity: 16, Cannot enable change tracking on table ‘%.*ls’. Change tracking does not support a primary key of type timestamp on a table.
Error: 5001, Severity: 16, User must be in the master database.
Error: 5002, Severity: 16, Database ‘%.*ls’ does not exist. Verify the name in sys.databases and try the operation again.
Error: 5003, Severity: 16, Database mirroring cannot be enabled while the database has offline files.
Error: 5004, Severity: 16, To use ALTR DATABASE, the database must be in a writable state in which a checkpoint can be executed.
Error: 5005, Severity: 16, Specified recovery time of %I64d seconds is less than zero or more than the maximum of %d seconds.
Error: 5006, Severity: 16, Could not get exclusive use of %S_MSG ‘%.*ls’ to perform the requested operation.
Error: 5008, Severity: 16, This ALTR DATABASE statement is not supported. Correct the syntax and execute the statement again.
Error: 5009, Severity: 16, One or more files listed in the statement could not be found or could not be initialized.

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: 4171 to Error: 4196

SQLServerF1

 

Error: 4171, Severity: 16, Alias was not specified for an aggregate in the PROB_MATCH SELECT list.
Error: 4172, Severity: 16, Incorrect use of full-text %s.
Error: 4173, Severity: 16, %.*s is not a valid scoring function name.
Error: 4174, Severity: 16, Delayed CLR type instantiation fetch value query may only reference column of a large object or large value type.
Error: 4175, Severity: 16, Nested updates cannot be performed on CLR types that are not Format.Structured.

Error: 4176, Severity: 16, Too many parameters were specified for FULLTEXTTABLE of type “Simple”. The maximum number of parameters is %d.
Error: 4177, Severity: 16, The FROM clause of a PROB_MATCH query must consist of a single derived table.
Error: 4184, Severity: 16, Cannot retrieve table data for the query operation because the table “%.*ls” schema is being altered too frequently. Because the table “%.*ls” contains a filtered index or filtered statistics, changes to the table schema require a refresh of all table dat
Error: 4185, Severity: 16, This action cannot be performed on a system type.

Error: 4186, Severity: 16, Column ‘%ls.%.*ls’ cannot be referenced in the OUTPUT clause because the column definition contains a subquery or references a function that performs user or system data access. A function is assumed by default to perform data access if it is not schemabo
Error: 4187, Severity: 16, Data type %ls of receiving variable cannot store all values of the data type %ls of column ‘%.*ls’ without data loss.
Error: 4188, Severity: 16, Column or parameter ‘%.*ls’ has type ‘%ls’ and collation ‘%.*ls’. The legacy LOB types do not support Unicode supplementary characters whose codepoints are U+10000 or greater. Change the column or parameter type to varchar(max), nvarchar(max) or use a col
Error: 4189, Severity: 16, Cannot convert to text/ntext or collate to ‘%.*ls’ because these legacy LOB types do not support the Unicode supplementary characters whose codepoints are U+10000 or greater. Use types varchar(max), nvarchar(max), or a collation which does not have the _S
Error: 4190, Severity: 16, PIVOT operator is not allowed in the recursive part of a recursive common table expression ‘%.*ls’.
Error: 4191, Severity: 16, Cannot resolve collation conflict for %ls operation.
Error: 4192, Severity: 16, Cannot resolve collation conflict.
Error: 4193, Severity: 16, ‘%.*ls’ is not a valid window frame and cannot be used with the OVER clause.
Error: 4194, Severity: 15, RANGE is only supported with UNBOUNDED and CURRENT ROW window frame delimiters.
Error: 4195, Severity: 16, The reference to column “%.*ls” is not allowed in an argument to the NTILE function. Only references to columns at an outer scope or standalone expressions and subqueries are allowed here.
Error: 4196, Severity: 16, Column ‘%ls.%.*ls’ cannot be referenced in the OUTPUT clause because the column definition contains an expression using a window function.

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.

 
1 2