SQL Server 2008

  1. The element name "{0}" cannot be used as a DataTable TableName since it only differs from the TableName of another DataTable ...
  2. The element that indicates the attributes that the client application should use to identify an instance of the entity to ...
  3. The encoded address '{0}' contains too many sections '{1}'. Sections are semicolon-delimited (;), and an encoded address ...
  4. The encoded address '{0}' does not have enough sections '{1}'. IPv4 and IPv6 sections are semicolon-delimited (;), and an ...
  5. The encoded IPv4 address '{0}' does not have enough sections'{1}. IPv4 sections are type, address, network, and subnet mask, ...
  6. The end of the data file was reached while reading header rows. Make sure the header row delimiter and the number of header ...
  7. The endpoint "%1!s!" is a built-in endpoint and cannot be dropped. Use the protocol configuration utilities to ADD or DROP ...
  8. The endpoint '%1!s!' has been established in metadata, but HTTP listening has not been enabled because HTTP support did not ...
  9. The endpoint of the line {1}' is negative. The value for Left plus the value for Width of a line cannot result in a negative ...
  10. The endpoint of the line {1}' is negative. The value for Top plus the value for Height of a line cannot result in a negative ...
  11. The endpoints of the server instances you have specified have conflicting port numbers. Endpoints for instances on the same ...
  12. The entered value is out of the allowed range for the "{0}" data type. The valid values are greater than or equal to {1} ...
  13. The entire result set must be returned before this row can be updated. This operation is in progress and might take a long ...
  14. The entry point class name "{1}" was found during the migration of "{0}". The class will be renamed to "{2}" in the migrated ...
  15. The enumerator that defines how the client application generates a context-sensitive name for the attribute when the entity ...
  16. The enumerator that indicates the attribute's data type. If an Expression data type is also present, the Expression and DataType ...
  17. The enumerator that indicates whether this attribute should be sorted Ascending or Descending when the main attribute is ...
  18. The enumerator that overrides the ContextualName setting for attributes in the role's target entity when the role is used ...
  19. The error described above occurred when trying to delete this data at this location, possibly because the deletion violated ...
  20. The error described above occurred when trying to delete this data at this location, possibly because the deletion violated ...
  21. The error described above occurred when trying to delete this row. If you ignore this conflict, you should resolve it through ...
  22. The error described above occurred when trying to insert or update this data at the other server. If you ignore this conflict, ...
  23. The error log file could not be created. Make sure you have the appropriate permissions and that the ErrorLogFilePath is ...
  24. The error message id "%1!s!" is out of the allowed range of user defined error messages. User defined error message ids are ...
  25. The error output cannot receive any error rows. This occurs for several reasons: Input columns or output columns are not ...
  26. 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 ...
  27. 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 ...
  28. The evaluation condition expression on the For Loop "%1!s!" is empty. There must be a Boolean evaluation expression in the ...
  29. The evaluation expression for the loop is not valid. The expression needs to be modified. There should be additional error ...
  30. The evaluation period for this instance of Microsoft SQL Server Reporting Services has expired. A license is now required. ...
  31. The event Id=%d{EventId/} does not contain the column Id=%d{ColId/}. Please refer to product documentation for a list of ...
  32. The event session option, "%1!s!", is set more than once. Remove the duplicate session option and re-issue the statement. ...
  33. The exact lookup columns, "%1!s!" and "%2!s!", do not have equal data types or are not comparable string types. Exact joins ...
  34. The Exchange Spill event class indicates that communication buffers in a parallel query plan have been temporarily written ...
  35. The ExcludePartition option does not apply to the source object. This scripting option applies only to Database, Cube, and ...
  36. The ExcludePermissions option does not apply to the source object. This scripting option applies to only Database, Dimension, ...
  37. The ExcludePermissions option does not apply to the source object. This scripting option only applies to Database, Dimension, ...
  38. The executable "%1!s!" was pasted successfully. However a log provider that was associated with the executable was not found ...
  39. The executable has been added to the Executables collection of another container. This occurs when a client tries to add ...
  40. The executable, dtshost.exe, cannot be run in standalone mode. It can be run only from within SQL Server Integration Services. ...
  41. The Execute DTS 2000 Package task requires the SQL Server 2000 Data Transformation Services (DTS) runtime. To install the ...
  42. The Execute method on the task returned error code 1!8.8X! (%2!s!). The Execute method must succeed, and indicate the result ...
  43. The Exhaustive option requires that the entire reference be loaded into main memory. Since a memory limit has been specified ...
  44. The existing property value specifies multiple directories. You can select only one directory in the Browse for Folders dialog ...
  45. The existing replication configuration is incomplete. Please complete the configuration by setting 'creation_script' values ...
  46. The ExitCode property specifies a Win32 error code defining any problems encountered in starting or stopping the service. ...
  47. The expanded dynamic snapshot view definition of one of the articles exceeds the system limit of 3499 characters. Consider ...
  48. The expected starting point for synchronization at '%1' is invalid. This can occur when the publication or subscription database ...
  49. The expression "%1!s!" is not valid and cannot be parsed. The expression may contain invalid elements or it may not be well-formed. ...
  50. The expression "%1!s!" on "%2!s!" evaluated to NULL, but the "%3!s!" requires a Boolean results. Modify the error row disposition ...
  51. The expression "%1!s!" will always result in a truncation of data. The expression contains a static truncation (the truncation ...
  52. The expression contained a token that was not recognized. The expression could not be parsed because it contains invalid ...
  53. The expression contains an unexpected equal sign (=). This error usually occurs when a double equals sign (=) is needed. ...
  54. The expression contains an unrecognized token that appears to be an input column reference, but the input column collection ...
  55. The expression contains an unsupported data type conversion. The source type cannot be converted to the destination type. ...
  56. The expression contains unrecognized token "%1!s!". If "%1!s!" is a variable, it should be expressed as "@%1!s!". The specified ...
  57. The expression evaluated to NULL, but a Boolean result is required. Modify the error row disposition on the output to treat ...
  58. The Expression for the {0} is not an aggregate expression, but the IsAggregate property is true. An aggregate expression ...
  59. The Expression for the {0} returns a set of values for each instance of the {1}. This expression must return a single value ...
  60. The expression that is being aggregated must either be a simple aggregate field, or a filter applied to an aggregate field. ...
  61. The expression used for the calculated field '{1}' includes a variable reference. Variable values cannot be used in calculated ...
  62. The expression used for the calculated field '{1}' includes an aggregate function. Aggregate functions cannot be used in ...
  63. The expression used for the language of '{1}' includes a variable reference. Variable values cannot be used in report language ...
  64. The expression used for the language of '{1}' includes an aggregate function. Aggregate functions cannot be used in report ...
  65. The expression used for the language of '{1}' refers to a data source. Data sources cannot be used in report language expressions. ...
  66. The expression used for the language of '{1}' refers to a dataset. Datasets cannot be used in report language expressions. ...
  67. The expression used for the language of '{1}' refers to a report item. Report items cannot be used in report language expressions. ...
  68. The expression used for the language of '{1}' uses the aggregate function Previous. Previous cannot be used in report language ...
  69. The expression used for the language of '{1}' uses the aggregate function RunningValue. RunningValue cannot be used in report ...
  70. The expression used for the language of '{1}' uses the function RowNumber. RowNumber cannot be used in report language expressions. ...
  71. The expression used for the parameter '{1}' in the dataset '{3}' includes a variable reference. Variable values cannot be ...
  72. The expression used for the parameter '{1}' in the dataset '{3}' includes an aggregate function. Aggregate functions cannot ...
  73. The expression used for the parameter {1}' in the dataset {3}' includes the function RowNumber. RowNumber cannot be used ...
  74. The expression used for the parameter {1}' in the dataset {3}' refers to a data source. Data sources cannot be used in query ...
  75. The expression used for the parameter {1}' in the dataset {3}' refers to a dataset. Datasets cannot be used in query parameter ...