SQL Server 2016
- The cluster group '{0}' contains resource '{1}' of type '{2}' that are not permitted in a SQL cluster group. Ensure the cluster ...
- The cluster group cannot be determined for the instance name '{0}'. This indicates there is a problem with the product registry ...
- The cluster group name cannot be null or empty and cannot contain ' or \. To continue, specify a valid group name and retry, ...
- The cluster group name for group '{0}' could not be determined. Error: {1}. Ensure that the name you provided is correct, ...
- The cluster group type for group '{0}' could not be determined. Error: {1}. Ensure that the group name you provided is correct, ...
- The Cluster Group {0} is active on the node where SQL Server Setup is running. To continue, the group must be either be owned ...
- The Cluster Group {0} is not owned by the node where SQL Server Setup is running. To continue, run Setup again on the node ...
- The cluster network '{0}' does not have a bound IPv4 address which indicates IPv4 is not supported for that network. Bind ...
- The cluster network '{0}' does not have a bound IPv6 address which indicates IPv6 is not supported for that network. Bind ...
- The cluster network name '{0}' could not be taken offline. To continue, take the network name offline before you delete it. ...
- The cluster node name '{0}' is invalid. The specified computer is not a cluster node in this SQL Server failover cluster. ...
- The cluster on this computer does not have a shared disk available. To continue, at least one shared disk must be available. ...
- The cluster operation cannot be completed because no clustered feature is available. The failover cluster name cannot be ...
- The cluster resource '{0}' could not be brought online due to an error bringing the dependency resource '{1}' online. Refer ...
- The cluster resource with type '{0}' and property '{1}' = '{2}'could not be found on the cluster. Please check if it exists. ...
- The Cluster Service function call '%1!s!' failed with error code '%2!s!' while verifying the file path. Verify that your ...
- The clustered index '%1!s!' on table '%2!s!' cannot be disabled because the table has change tracking enabled. Disable change ...
- The clustered index '{0}.{1}.{2}' will not be scripted for article '{3}' because it references the unpublished column '{4}'. ...
- The clustered index on materialized view '%1!s!' may not contain nullable columns if it is to be published using the transaction-based ...
- The clustering method the algorithm uses can be either: Scalable EM (1), Non-scalable EM (2), Scalable K-means (3), or Non-scalable ...
- The ClusterProbability function returns the probability of the input case belonging to the specified (or most likely) cluster. ...
- The code page %1!d! specified on column "%2!s!" (%3!d!) is not supported. You must first convert this column to DT_WSTR which ...
- The code page %1!d! specified on output column "%2!s!" (%3!d!) is not valid. Select a different code page for output column ...
- The code pages do not match in a binary operation. The code page of the left operand does not match the code page of the ...
- The code pages do not match in a conditional operation. The code page of the left operand does not match the code page of ...
- The code pages for operands of binary operator "%1!s!" for type "%2!s!" must match. Currently, the code page of the left ...
- The code pages must match for operands of conditional operation "%1!s!" for type %2!s!. The code page of the left operand ...
- The code pages of the DT_STR source column "%1!s!" and the DT_STR dest column "%2!s!" do not match. This may cause unexpected ...
- The COLLATE CATALOG_DEFAULT clause cannot be used in a constraint, computed column, index filter expression, or any schema-bound ...
- The collation you specified does not support the supplementary characters flag. To proceed, specify a Windows collation version ...
- The collection in the projection is of type '{0}'. For a collection to be materialized to a projection, it must be of type ...
- The collection navigation property '{0}' of type '{1}' returned null. For a collection to be initialized automatically, it ...
- The column "%1!s!" (%2!d!) cannot be matched to any input file column. The output column name or input column name cannot ...
- The column "%1!s!" at index %2!d! in the flat file connection manager was not found at index %3!d! in the column collection ...
- The column "%1!s!" in the pre-built index "%2!s!" was not found in the reference table/query. This happens if the schema/query ...
- The column '%1!s!' cannot be added to a full-text index. Full-text indexes are limited to 1024 columns. When you create a ...
- The column '%1!s!' cannot be added to table '%2!s!' as it is a FileTable. Adding columns to the fixed schema of a FileTable ...
- The column '%1!s!' could not be added to table '%2!s!' because the column contains filestream data and the table is referenced ...
- The column '%1!s!' does not have a valid data type for the ORDER hint specified for data source '%2!s!'. The text, ntext, ...
- The column '%1!s!' in table '%2!s!' is involved in a foreign key relationship with a column in table '%3!s!', but this column ...
- The column '%1!s!' in the table '%2!s!' cannot be referenced in a CHECK constraint or computed column definition because ...
- The column '%1!s!' of the object '%2!s!' is encrypted. The currently installed edition of SQL Server does not support encrypted ...
- The column '%1!s!' specified in the SEMANTICSIMILARITYTABLE, SEMANTICKEYPHRASETABLE or SEMANTICSIMILARITYDETAILSTABLE function ...
- The column '%1!s!' that was returned from the nodes() method cannot be used directly. It can only be used with one of the ...
- The column '%{column/}' in table '%{table/}' has the SortByColumn property set to column '%{name/}' which belongs to table ...
- The column '%{column/}' in table '%{table/}' has the SortByColumn property set to column '%{name/}' which has been deleted. ...
- The column '%{IMBIColumnId/}', in the table '%{IMBITableId/}', has attribute hierarchy with column usage set to DAX Usage, ...
- The column '%{IMBIColumnId/}', in the table '%{IMBITableId/}', has property Column Usage set to DAX Usage, and this requires ...
- The column '%{table/}[%{column/}]' cannot be of type Empty. The Empty data type can only be set on a column if the column ...
- The column '%{table/}[%{column/}]' doesn't have a relationship to table '%{maintable/}' which is used in the decision tree ...
- The column '%{table/}[%{column/}]' either doesn't exist or doesn't have a relationship to any table available in the current ...
- The column '%{table/}[%{column/}].[%{variation/}]' either doesn't exist or doesn't have a relationship to any table available ...
- The column '{0}' is mapped to a domain that is marked to be indexed as a single value, which has a limitation of 900 characters. ...
- The column '{0}' that was returned from the nodes() method cannot be used directly. It can only be used with one of the four ...
- The column contains mixed data types and the data was pasted as text. PowerPivot can automatically add a calculated column ...
- The column encryption key has been successfully decrypted but its length: %2!s! does not match the length: %3!s! for the ...
- The column msrepl_tran_version has been predefined and allows NULLs. This column will be dropped and recreated to not allow ...
- The column name "{0}" cannot be used as a column name for DataTable "{1}" since it is identical to another DataColumn ColumnName ...
- The column name "{0}" specified in the UNPIVOT operator conflicts with the existing column name in the UNPIVOT argument. ...
- The column name '%1!s!' is specified more than once in the SET clause or column list of an INSERT. A column cannot be assigned ...
- The column name '{0}' is specified more than once in the SET clause or column list of an INSERT. A column cannot be assigned ...
- The column name '{0}' is specified more than once in the SET clause. A column cannot be assigned more than one value in the ...
- The column name '{0}' is specified more than once in the SET clause. A column cannot be assigned more than one value in the ...
- The column or parameter '%1!s!' uses a data type not supported by SOAP. SOAP only supports data types supported in SQL Server ...
- The Column property of the {0} refers to the {1}, which has the data type Binary. The Column property of an Entity cannot ...
- The column reference "%1!s!.%2!s!" is not allowed because it refers to a base table that is not being modified in this statement. ...
- The column referenced as '%1!s!' resolves differently in the target metadata collation '%2!s!' than in the current metadata ...
- The column referenced by the PerspectiveColumn '%{perspcolumn/}' in table '%{persptable/}' in perspective '%{persp/}' cannot ...
- The column that was returned from the nodes() method cannot be converted to the data type %1!s!. It can only be used with ...
- The column with ID of '%{propertyid/}', Name of '%{propertyname/}' referred to by the '%{aggregationdimension/}' table cannot ...
- The column you selected to be the Row Identifier does not contain unique values. Select a column that contains unique values ...
- The column's data type is about to be changed. This will affect how data is stored and can impact data precision or result ...
- The column, '{0}', cannot be used as the time stamp because it contains null values. Choose a column that does not contain ...
- The columns and types of the DATATABLE function do not appear to be correctly paired (the number of arguments must be odd). ...
- The columns are defined by fixed widths. An extra column, delimited by the new line characters, is added to define row delimiters. ...