SQL Server 2012
- The expression contained a token that was not recognized. The expression could not be parsed because it contains invalid ...
- The expression contains an unexpected equal sign (=). This error usually occurs when a double equals sign (=) is needed. ...
- The expression contains an unrecognized token that appears to be an input column reference, but the input column collection ...
- The expression contains an unsupported data type conversion. The source type cannot be converted to the destination type. ...
- The expression contains multiple columns, but only a single column can be used in a True/False expression that is used as ...
- The expression contains unrecognized token "%1!s!". If "%1!s!" is a variable, it should be expressed as "@%1!s!". The specified ...
- The expression evaluated to NULL, but a Boolean result is required. Modify the error row disposition on the output to treat ...
- The Expression for the {0} is not an aggregate expression, but the IsAggregate property is true. An aggregate expression ...
- The Expression for the {0} returns a set of values for each instance of the {1}. This expression must return a single value ...
- The expression invokes an object that was defined by using an MDX calculated member or script. Such objects are not supported ...
- The expression referenced a relationship between '%{FKTable/}'[%{FKColumn/} and '%{PKTable/}'[%{PKColumn/}], which does not ...
- The expression referenced column '%{table/}'[%{column/} which does not hold any data because it needs to be recalculated ...
- The expression references an item '{0}', which does not exist in the Globals collection. Letters in the names of Globals ...
- The expression references an item '{0}', which does not exist in the User collection. Letters in the names of User collection ...
- The expression references the data source '{0}', which does not exist in the DataSource collection. Letters in the names ...
- The expression references the dataset '{0}', which does not exist in the DataSets collection. Letters in the names of datasets ...
- The expression references the field '{0}', which does not exist in the Fields collection. Expressions can only refer to fields ...
- The expression references the parameter '{0}', which does not exist in the Parameters collection. Letters in the names of ...
- The expression references the report item '{0}', which does not exist in the ReportItems collection. Expressions can only ...
- The expression references the variable '{0}', which does not exist in the Variables collection. Expressions can only refer ...
- The expression that is being aggregated must either be a simple aggregate field, or a filter applied to an aggregate field. ...
- The expression that specifies the binding field '{3}' for layer '{2}' in the {0} '{1}' is not valid. The data type does not ...
- The expression that you specified as the argument to the ALLEXCEPT function includes all columns in the table; therefore, ...
- The expression used for calculated field '{1}' includes a variable reference. Variable values cannot be used in calculated ...
- The expression used for parameter '{1}' in the dataset '{3}' includes a variable reference. Variable values cannot be used ...
- The expression used for parameter {1}' in the dataset {3}' includes the RowNumber function. RowNumber cannot be used in query ...
- The expression used for parameter {1}' in the dataset {3}' refers to a report item. Report items cannot be used in query ...
- The expression used for the calculated field '{1}' includes an aggregate, RowNumber, RunningValue, Previous or lookup function. ...
- The expression used for the language of '{1}' includes a variable reference. Variable values cannot be used in report language ...
- The expression used for the language of '{1}' includes an aggregate or lookup function. Aggregate and lookup functions cannot ...
- The expression used for the language of '{1}' refers to a data source. Data sources cannot be used in report language expressions. ...
- The expression used for the language of '{1}' refers to a dataset. Datasets cannot be used in report language expressions. ...
- The expression used for the language of '{1}' refers to a report item. Report items cannot be used in report language expressions. ...
- The expression used for the language of '{1}' uses the Previous aggregate function. Previous cannot be used in report language ...
- The expression used for the language of '{1}' uses the RowNumber function. RowNumber cannot be used in report language expressions. ...
- The expression used for the language of '{1}' uses the RunningValue aggregate function. RunningValue cannot be used in report ...
- The expression used for the parameter '{1}' in the dataset '{3}' includes an aggregate or lookup function. Aggregate and ...
- The expression used for the parameter {1}' in the dataset {3}' refers to a data source. Data sources cannot be used in query ...
- The expression used for the parameter {1}' in the dataset {3}' refers to a dataset. Datasets cannot be used in query parameter ...
- The expression used for the parameter {1}' in the dataset {3}' refers to a field. Fields cannot be used in query parameter ...
- The expression used for the parameter {1}' in the dataset {3}' uses the Previous aggregate function. Previous cannot be used ...
- The expression used for the parameter {1}' in the dataset {3}' uses the RunningValue aggregate function. RunningValue cannot ...
- The expression will not be evaluated because it contains sensitive parameter variable "%1!s!". Verify that the expression ...
- The expression will not be evaluated because it contains the variable "%1!s!" that references sensitive parameter variables ...
- The Extended Event engine could not be initialized. Check the SQL Server error log and the Windows event logs for information ...
- The Extended Event engine has been disabled by startup options. Features that depend on Extended Events may fail to start. ...
- The Extended Events session named "%1!s!" was modified during the upgrade and one of the bucketizer targets was excluded ...
- The extension id {2} given in the {0} element which defined the {1} package for the localized description is not a valid ...
- The extension interface '{1}' defined for the extension type '{2}' in the assembly '{0}' is not an interface type. Extension ...
- The extension interface '{1}' defined for the extension type '{2}' in the assembly '{0}' is not implemented by '{2}'. Check ...
- The extension interface '{1}' defined in the assembly '{0}' does not implement the base interface '{2}'. Modify the mutable ...
- The extension type '{1}' defined in the assembly '{0}' as a '{3}' extension does not extend the base class '{2}'. Modify ...
- The extension type '{1}' defined in the assembly '{0}' does not implement any extension interfaces. Modify the type to implement ...
- The extension type '{2}' in the assembly '{0}' cannot be defined as a default extension for all '{1}'. Default extensions ...
- The extension, "%1!s!", was implicitly upgraded to "%2!s!". Add a mapping for this extension to the UpgradeMappings directory. ...
- The extension, "{0}", was implicitly upgraded to "{1}". Add a mapping for this extension to the UpgradeMappings directory. ...
- The external column "%1!s!" of "%2!s!" has a data type that cannot be mapped to a Data Flow task data type. The Data Flow ...
- The external metadata collection is improperly used by this component. The component should use external metadata when appending ...
- The extraction point could not be created. You must be logged on as a Windows authenticated user to perform this action. ...
- The Extraction Point Creation Wizard creates an extraction point that extracts impact and data lineage metadata for Integration ...
- The factory type '{1}' defined in the assembly '{0}' does not implement the interface '{2}'. Modify the type to implement ...
- The factory type '{2}' defined for the extension type '{1}' defined in the assembly '{0}' cannot be found in the assembly. ...
- The failed attempt by sp_refresh_heterogeneous_publisher to refresh publisher '%1!s!' did not alter any meta data at the ...
- The failover cluster group is already owned by the upgraded nodes of the SQL Server instance, so it is not possible to transfer ...
- The failover instance name could not be retrieved. The settings cannot be updated. Check whether the Active Node is accessible ...
- The FAILOVER_MODE option has not been specified for the replica '%1!s!'. Reenter the command, specifying a failover mode ...
- The fast load destination is not valid. To use fast load, a table or a view must be selected or an SQL statement of the form ...
- The FastAppend loading mode does not support the use of transactions. If this is the desired load mode, uncheck the "Rollback ...
- The feature state notification message received from the MSI has an invalid number of arguments. Each feature must include ...
- The FeatureUpgradeIncompleteCondition element cannot be the root element of a document, it can only be used as the child ...
- The federation member with ID {0} belonging to federation {1} could not be retrieved. Verify that the specified federation ...
- The field with the name {1}' in the dataset {3}' has both or neither of the following properties: DataField and Value. Fields ...
- The file "%1!s!" has been modified in the system catalog. The new path will be used the next time the database is started. ...
- The file "%1!s!" is ambiguous. The identity in the backup set does not match the file that is currently defined in the online ...
- The file "%1!s!" is missing. Roll forward stops at log sequence number %2!s!. The file is created at log sequence number ...