SQL Server 2008 R2

  1. The function "%1!s!" does not support the data type "%2!s!" for parameter number %3!d!. The type of the parameter could not ...
  2. The function "%1!s!" requires %2!d! parameter, not %3!d! parameters. The function name was recognized, but the number of ...
  3. The function "%1!s!" requires %2!d! parameters, not %3!d! parameter. The function name was recognized, but the number of ...
  4. The function "%1!s!" requires %2!d! parameters, not %3!d! parameters. The function name was recognized, but the number of ...
  5. The function %{function/} takes an argument that evaluates to numbers or dates and cannot work with values of type %{datatype/}. ...
  6. The function LOG cannot operate on zero or negative values, and a zero or negative value was passed to the LOG function. ...
  7. The functionality you're trying to execute is disabled inside SQLCLR, if you still want to execute this functionality you ...
  8. The functions IsInNode or IsDescendant should be used only once and no OR operator should be used together at line %d{Line/}, ...
  9. The fuzzy lookup specified between input column "%1!s!" and reference column "%2!s!" is not valid because fuzzy joins are ...
  10. The Generate SQL Server Scripts Wizard allows you to generate scripts for databases and objects inside databases. This wizard ...
  11. The generated script file path '%1' has exceeded the length limit of %2!d! characters imposed by the Snapshot agent. Reducing ...
  12. The geometry index n ({0}) passed to STGeometryN is less than 1. The number must be greater than or equal to 1 and should ...
  13. The geometryType argument to InstanceOf ('{0}') is not valid. This argument must contain one of the following types: Geometry, ...
  14. The GetEnumerator method of the ForEach Enumerator has failed with error 1!8.8X! "%2!s!". This occurs when the ForEach Enumerator ...
  15. The given base allocator cannot be used by this delegating allocator because its page size is too small. The page size must ...
  16. The given inner allocator cannot be used by this small size allocator because its page size is too small. The page size must ...
  17. The given network name is unusable because there was a failure trying to determine if the network name is valid for use by ...
  18. The given XML instance is not valid because its top-level tag was {0}. The top-level element of the input Geographic Markup ...
  19. The Goal Seek tool provides useful recommendations when you know the desired value for a column of the current row (the Target ...
  20. The granularity attribute and intermediate granularity attribute should have same number of key columns (the granularity ...
  21. The granularity attribute has key column #{0} with data type '{1}' different than '{2}' from intermediate granularity attribute. ...
  22. The granularity attribute of the intermediate dimensions that are used to resolve many-to-many relationships should generally ...
  23. The graphical query designer is not available when connecting to a Microsoft SQL Server 2008 R2 data source using the Microsoft ...
  24. The group {3}' in the {0} {1}' is marked to create page break for each group. Page breaks are not supported for column groupings ...
  25. The group {3}' in the {0} {1}' is marked to create page break for each group. Page breaks are not supported for {2} in charts. ...
  26. The group {3}' in the {0} {1}' is marked to create page break for each group. Page breaks are not supported for {2} in gauges. ...
  27. The group {3}' in the {0} {1}' is marked to create page break for each group. Page breaks are not supported for {2} in maps. ...
  28. The grouping '{3}' in the {0} '{1}' has DataSet '{4}' as its domain scope. Only DataRegions and Grouping are allowed for ...
  29. The grouping '{3}' in the {0} '{1}' has {2} '{4}' and Parent defined. Domain scope is only allowed if Parent is not defined. ...
  30. The grouping '{3}' in the {0} '{1}' has {2} '{4}' with Parent defined. Grouping with parent defined cannot be a domain scope ...
  31. The hash value is not a one-dimensional array of bytes (error: %1!s!). This occurs in CPackage::LoadUserCertificateByHash. ...
  32. The Header or Footer is too complex to export to Word. Please group the ReportItems together into rectangles to simplify. ...
  33. The Health based load balancer did not find a healthy server to handle this request. Please add more resources to the farm. ...
  34. The heterogeneous log reader was unable to enter a tracer token into the distribution database: article ID = %1, publication ...
  35. The hidden field {0} is included in the query. Hidden fields cannot be hidden from the list browser when hidden fields are ...
  36. The hierarchy with ID of '%{hierarchyid/}', Name of '%{hierarchyname/}' referenced by the %{detaildimension/} measure group ...
  37. The hierarchy with ID of '%{hierarchyid/}', Name of '%{hierarchyname/}' referenced by the '%{cubedimension/}' cube dimension, ...
  38. The highest incompatible Management Data Warehouse version number "%s" is incorrectly formatted. Please contact your system ...
  39. The highest incompatible Management Data Warehouse version number "%s" stored in the configuration store is invalid. Please ...
  40. The Highlight Exceptions tool detects rows in your table that do not conform to the rules and generalizations that govern ...
  41. The highlighted volumes do not have enough disk space available for the currently selected features. You can remove files ...
  42. The HISTORIC_MODEL_COUNT parameter for the mining model, %{modelname/}, is not valid. The count must not be negative and ...
  43. The HISTORIC_MODEL_GAP parameter for the mining model, %{modelname/}, is not valid. The gap between the mining models must ...
  44. The History Cleanup task deletes historical data about Backup and Restore, SQL Server Agent, and Maintenance Plan operations. ...
  45. The History Cleanup task deletes historical data about Backup and Restore, SQL Server Agent, and Maintenance Plan operations. ...
  46. The history queue has reached maximum capacity before the history connection is set, the history connection should have been ...
  47. The HOLDOUT_PERCENTAGE parameter for the mining model, %{modelname/}, is not valid. HOLDOUT_PERCENTAGE must be greater than ...
  48. The ID property for the {0} is in the empty (or SMDL) namespace but it is not a GUID. IDs in the empty (or SMDL) namespace ...
  49. The ID, %1!lu!, is neither an input ID nor an output ID. The specified ID must be the input ID or the output ID that the ...
  50. The identifier '%1!s!' cannot be bound. Only source columns are allowed in the 'WHEN NOT MATCHED' clause of a MERGE statement. ...
  51. The identifier '%1!s!' cannot be bound. Only target columns are allowed in the 'WHEN NOT MATCHED BY SOURCE' clause of a MERGE ...
  52. The identity property was attempted to be set for column %1!Iu!. Only columns of integer and numeric types can be marked ...
  53. The identity range allocation entry for the Publisher could not be found in the system table MSmerge_identity_range. Ensure ...
  54. The ImpersonationInfo for datasource '%{Datasource/}' contains an ImpersonationMode that can only be used by a server administrator. ...
  55. The import population for database %1!s! (id: %2!s!), catalog %3!s! (id: %4!s!) is being cancelled because of a fatal error ...
  56. The incoming tabular data stream (TDS) protocol stream is incorrect. The multiple active result sets (MARS) TDS header is ...
  57. The incoming tabular data stream (TDS) protocol stream is incorrect. The Query Notification TDS header contained errors. ...
  58. The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Meta-information is invalid ...
  59. The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %1!s! ("%2!s!"): ...
  60. The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %1!s! ("%2!s!"): ...
  61. The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %1!s! ("%2!s!"): ...
  62. The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %1!s! ("%2!s!"): ...
  63. The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %1!s! ("%2!s!"): ...
  64. The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %1!s! ("%2!s!"): ...
  65. The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %1!s! ("%2!s!"): ...
  66. The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %1!s! ("%2!s!"): ...
  67. The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %1!s! ("%2!s!"): ...
  68. The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %1!s! ("%2!s!"): ...
  69. The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %1!s! ("%2!s!"): ...
  70. The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %1!s! ("%2!s!"): ...
  71. The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %1!s! ("%2!s!"): ...
  72. The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %1!s! ("%2!s!"): ...
  73. The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %1!s! ("%2!s!"): ...
  74. The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %1!s! ("%2!s!"): ...
  75. The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter %1!s! ("%2!s!"): ...