SQL Server 2008
- 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!' that was returned from the nodes() method cannot be used directly. It can only be used with one of 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 '%1!s!' is specified more than once in the SET clause. A column cannot be assigned more than one value in ...
- 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 "inserted.%1!s!" is not allowed because it refers to a base table that is not being modified in this ...
- 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, '{0}', cannot be used as the time stamp because it contains null values. Choose a column that does not contain ...
- The columns are defined by fixed widths. An extra column, delimited by the new line characters, is added to define row delimiters. ...
- The columns cannot be matched using the names. Try to map them manually by choosing appropriate ones from the list of available ...
- The combination of scheduled polling and incremental updates can only be specified when the storage mode is MOLAP. The current ...
- The command %1!s! failed. The values specified for the @ins_cmd, @del_cmd or @upd_cmd cannot be appended with schema name ...
- The command line specified in the definition file is too long; the maximum length allowed is %1!u! characters. Use a user-defined ...
- The command line specified is too long. The maximum length allowed is %1!u! characters. Shorten the command line or use an ...
- The command specified for the dataset '{0}' is using an expression. Expressions are not supported in command text field when ...
- The command type '{1}' specified for the dataset '{0}' is not supported when rendering a report in Management Studio. The ...
- The commit transaction operation cannot be executed since it is attempting to modify the contents of the read only database ...
- The common criteria compliance enabled option enables the following: Residual Information Protection (RIP), the ability to ...
- The common generation watermark is invalid at this replica since it does not exist or metadata for changes not yet propagated ...
- The comparison flags for "%1!s!" must be zero because its type is not a string type. ComparisonFlags can only be non-zero ...
- The ComparisonFlags property cannot be set to a non-zero value for "%1!s!" because the "%2!s!" is not a source output. The ...
- The compatibility level of the new database does not support a management data warehouse. Select a different database, or ...
- The COMPLEXITY_PENALTY parameter for the '%{modelname/}' model is not valid. COMPLEXITY_PENALTY must be greater than 0 and ...
- The component could not be added to the Data Flow task. Verify that this component is properly installed. Component information: ...
- The component has detected potential metadata corruption during validation. {0} Click OK to continue to the advanced editor. ...
- The component has detected potential metadata corruption during validation. {0} Due to limitations of the Advanced Editor ...
- The component has detected potential metadata corruption during validation. {0} It may not be possible to recover to a valid ...
- The component has no available input columns and cannot be configured correctly. To correct the problem, connect an output ...
- The component is missing, not registered, not upgradeable, or missing required interfaces. The contact information for this ...
- The component is not in a valid state. The validation errors are: {0} Do you want the component to fix these errors automatically? ...
- The component locale ID has not been set. Flat file adapters need to have the locale ID on the flat file connection manager ...
- The component metadata for "%1!s!" could not be upgraded to the newer version of the component. The PerformUpgrade method ...
- The component reported the following warnings: {0} Choose OK if you want to continue with the operation. Choose Cancel if ...
- The component view ID is incorrect. The component view may be out of synchronization. Try releasing the component view and ...
- The component was not able to set the value, "{0}", from the data flow element, "{1}", to table element, "{2}", because of ...
- The compressed size of the cabinet has just exceeded the SQL Replication's predefined limit of {0} bytes, retry the operation ...
- The computed column '{0}.{1}.{2}' may not be created successfully at the subscriber because it references the max (varchar, ...
- The computed column '{0}.{1}.{2}' may not be created successfully at the subscriber because it references the user-defined ...
- The computed column '{0}.{1}.{2}' may not be created successfully at the subscriber because it references the xml column ...
- The computer cannot access the Internet. There might be delays in starting a .NET application like Management Studio. If ...
- The concurrent snapshot for publication '%1!s!' is not available because it has not been fully generated or the Log Reader ...
- The conditional expression "%1!s!" of the conditional operator has an invalid data type of "%2!s!". The conditional expression ...
- The conditional expression of the conditional operator has invalid data type. The conditional expression must be of type ...
- The conditional operation "%1!s!" failed with error code 2!8.8X!. There was an internal error or an out-of-memory error. ...
- The configuration entry "%1!s!" had an incorrect format. This can occur because of a missing delimiter or formatting errors, ...
- The configuration entry "%1!s!" in the configuration file was not valid, or failed to configure the variable. The name indicates ...
- The configuration entry, "%1!s!", has an incorrect format because it does not begin with package delimiter. There was no ...
- The configuration entry, "%1!s!", has an incorrect format because it does not begin with the package delimiter. Prepend "\package" ...
- The configuration environment variable was not found. The environment variable was: "%1!s!". This occurs when a package specifies ...
- The configuration file loaded, but is not valid. The file is not formatted correctly, may be missing an element, or may be ...
- The configuration information for mapping restrictions, properties, and other XML for Analysis objects has not been loaded ...
- The configuration of secondary database {0}].[{1} has been changed at the secondary server instance. The database is no longer ...
- The configuration of secondary database {0}].[{1} has been changed at the secondary server instance. The database is now ...
- The configuration parameter SharePointIntegrated is set to True but Share Point Object Model cannot be loaded. The error ...
- The configuration path could not be retrieved from the active node. Check whether you can reach the active node from the ...
- The configuration path on the passive node is different from the configuration path on the active node. The passive node's ...
- The configuration settings could not be applied to the '{0}' partition in the '{1}' measure group in the '{2}' cube because ...
- The configuration that is associated with blob store ID in the database has the invalid EnumerationOptimizationLevel value: ...
- The configuration type for configuration "%1!s!" is not valid. This may occur when an attempt is made to set the type property ...
- The configuration type for the registry configuration was not found in key "%1!s!". Add a value called ConfigType to the ...
- The configuration type in one of the configuration entries was not valid. Valid types are listed in the DTSConfigurationType ...
- The configuration value for the registry configuration was not found in key "%1!s!". Add a value called Value to the registry ...
- The configurations settings could not be applied to the '{0}' data source because the data source does not exist in the database. ...
- The configurations settings could not be applied to the '{0}' dimension because the dimension is not present in the database. ...
- The configurations settings could not be applied to the '{0}' measure group in the '{1}' cube because the measure group is ...
- The configurations settings could not be applied to the '{0}' mining structure because the mining structure is not present ...
- The configured working directory '{0}' does not exist or External Activator service does not have the permission to access ...
- The conflict resolver chose to delete this row at '%1' due to a conflict in the logical record between '%1' and '%2' in which ...
- The conflict resolver chose to update or insert this row at '%1' with the data from '%2' due to a conflict in the logical ...
- The connected user is not an Analysis Services server administrator. Only an administrator can make changes to server properties. ...
- The connection "%1!s!" is not found. This error is thrown by Connections collection when the specific connection element ...