SQL Server 2008 R2
- The error described above occurred when trying to insert or update this data at the other server. If you ignore this conflict, ...
- The error log file could not be created. Make sure you have the appropriate permissions and that the ErrorLogFilePath is ...
- The error message id "%1!s!" is out of the allowed range of user defined error messages. User defined error message ids are ...
- The error output cannot receive any error rows. This occurs for several reasons: Input columns or output columns are not ...
- The error row disposition on "%1!s!" cannot be set to redirect the row when the fast load option is turned on, and the maximum ...
- The evaluation condition expression on the For Loop "%1!s!" is empty. There must be a Boolean evaluation expression in the ...
- The evaluation expression for the loop is not valid. The expression needs to be modified. There should be additional error ...
- The evaluation period for Microsoft StreamInsight CTP3 has ended. Please contact Microsoft to obtain an updated version of ...
- The evaluation period for Microsoft StreamInsight instance '{0}' has expired. For information on how to upgrade your evaluation ...
- The evaluation period for this instance of Microsoft SQL Server Reporting Services has expired. A license is now required. ...
- The evaluation period for this instance of Microsoft SQL Server Reporting Services has expired. A license is now required. ...
- The event Id=%d{EventId/} does not contain the column Id=%d{ColId/}. Please refer to product documentation for a list of ...
- The event is too big to fit into one page. The page size is '{0}' bytes. Either reduce the size of the event payload or increase ...
- The event is too big to fit into one page. With event page size of '{0}' bytes, the maximum allowed event payload size is ...
- The event session option, "%1!s!", is set more than once. Remove the duplicate session option and re-issue the statement. ...
- The exact lookup columns, "%1!s!" and "%2!s!", do not have equal data types or are not comparable string types. Exact joins ...
- The Excel workbook, file '%{XLSXPathname/}', does not contain embedded PowerPivot data, or a data corruption error was detected. ...
- The Exchange Spill event class indicates that communication buffers in a parallel query plan have been temporarily written ...
- The ExcludePartition option does not apply to the source object. This scripting option applies only to Database, Cube, and ...
- The ExcludePermissions option does not apply to the source object. This scripting option applies to only Database, Dimension, ...
- The ExcludePermissions option does not apply to the source object. This scripting option only applies to Database, Dimension, ...
- The executable "%1!s!" was pasted successfully. However a log provider that was associated with the executable was not found ...
- The executable has been added to the Executables collection of another container. This occurs when a client tries to add ...
- The executable, dtshost.exe, cannot be run in standalone mode. It can be run only from within SQL Server Integration Services. ...
- The Execute DTS 2000 Package task requires the SQL Server 2000 Data Transformation Services (DTS) runtime. To install the ...
- The Execute method on the task returned error code 1!8.8X! (%2!s!). The Execute method must succeed, and indicate the result ...
- The execution settings returned by the report server are not recognized by this version of SharePoint. The "live data" option ...
- The Exhaustive option requires that the entire reference be loaded into main memory. Since a memory limit has been specified ...
- The existing property value specifies multiple directories. You can select only one directory in the Browse for Folders dialog ...
- The existing replication configuration is incomplete. Please complete the configuration by setting 'creation_script' values ...
- The existing text you want to replace. If the case of old_text does not match the case in the existing text, SUBSTITUTE will ...
- The ExitCode property specifies a Win32 error code defining any problems encountered in starting or stopping the service. ...
- The expanded dynamic snapshot view definition of one of the articles exceeds the system limit of 3499 characters. Consider ...
- The expected starting point for synchronization at '%1' is invalid. This can occur when the publication or subscription database ...
- The expression "%1!s!" is not valid and cannot be parsed. The expression may contain invalid elements or it may not be well-formed. ...
- The expression "%1!s!" on "%2!s!" evaluated to NULL, but the "%3!s!" requires a Boolean results. Modify the error row disposition ...
- The expression "%1!s!" will always result in a truncation of data. The expression contains a static truncation (the truncation ...
- 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 Boolean expression that is used as a ...
- 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 that is being aggregated must either be a simple aggregate field, or a filter applied to an aggregate field. ...
- The expression that references an item '{0}' does not exist in the Globals collection. Letters in the names of Globals collection ...
- The expression that references an item '{0}' does not exist in the User collection. Letters in the names of User collection ...
- The expression that references the data source '{0}' does not exist in the DataSource collection. Letters in the names of ...
- The expression that references the dataset '{0}' does not exist in the DataSets collection. Letters in the names of datasets ...
- The expression that references the field '{0}' does not exist in the Fields collection. Expressions can only refer to fields ...
- The expression that references the parameter '{0}' does not exist in the Parameters collection. Letters in the names of parameters ...
- The expression that references the report item '{0}' does not exist in the ReportItems collection. Expressions can only refer ...
- The expression that references the variable '{0}' does not exist in the Variables collection. Expressions can only refer ...
- 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 the calculated field '{1}' includes a variable reference. Variable values cannot be used in calculated ...
- 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 aggregate function Previous. Previous cannot be used in report language ...
- The expression used for the language of '{1}' uses the aggregate function RunningValue. RunningValue cannot be used in report ...
- The expression used for the language of '{1}' uses the function RowNumber. RowNumber cannot be used in report language expressions. ...
- The expression used for the parameter '{1}' in the dataset '{3}' includes a variable reference. Variable values cannot be ...
- 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}' includes the function RowNumber. RowNumber cannot be used ...
- 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}' refers to a report item. Report items cannot be used in query ...