SQL Server 2016

  1. The {0} '{1}' has an invalid {2}. The {2} has an invalid {3}, '{4}'. Non-Static {3} elements must contain at least 1 {5}. ...
  2. The {0} '{1}' has an invalid {2}. The {2} must have the same value set for the {3} property as those following or preceding ...
  3. The {0} '{1}' has an {2} with an invalid {3}. The {3} can be an integer between -90 an 90, inclusive, or the values 'RightAngle' ...
  4. The {0} '{1}' has PageBreak set on grouping '{2}'. To support banding, Tablix is not allowed to have a grouping that sets ...
  5. The {0} '{1}' in dataset '{3}' does not contain a Boolean value and is used as a {2} for the {0} '{4}'. {0} objects used ...
  6. The {0} '{1}' in dataset '{3}' specifies an invalid {2} value. {2} values must be the name of another {0} in the same dataset. ...
  7. The {0} '{1}' in dataset '{4}' specifies a {2} value on a calculated field. {2} and {3} must not both be specified on the ...
  8. The {0} '{1}' is bound to a data source using the {2} data extension. The data extension returned an invalid database collation ...
  9. The {0} '{1}' is not bound to any data region or scope, but defines a relationship to other datasets. Relationships are ignored ...
  10. The {0} '{1}' is not bound to any data region or scope. Only first dataset-scoped aggregates are supported in that case. ...
  11. The {0} '{1}' is referenced by {2} '{3}' and {4} '{5}'. Nested {2} objects using join relationships may only reference a ...
  12. The {0} '{1}' is referenced by {2} '{3}' and {4} '{5}'. Nested {2} objects within the same top level DataRegion may only ...
  13. The {0} '{1}' specifies a Band of navigation type {2} with an invalid report item reference, '{3}'. It must reference a report ...
  14. The {0} '{1}' specifies a Band of navigation type {2}. The Band must define either a ReportItemReference or a ReportItem, ...
  15. The {0} '{1}' specifies a {2} for {0} '{3}'. The {2} requires at least one JoinCondition when its NaturalJoin property is ...
  16. The {0} '{1}' specifies a {2} that is missing the {3} property or sets the {3} property to false. The {3} property in a {2} ...
  17. The {0} '{1}' specifies BandLayoutOptions with more than one navigation type. Only one navigation element can be specified, ...
  18. The {0} '{1}' uses a relationship or default relationship with no JoinConditions. Relationships with no JoinConditions are ...
  19. The {0} '{1}' was created, but an error occurred setting permissions. Use the object properties dialog to set permissions ...
  20. The {0} algorithm cannot be used, because it requires a KEY TIME column, which is not present in the {1} structure. Select ...
  21. The {0} and {1} parameters have the same value of "{2}". However, these parameters must have different values. Specify a ...
  22. The {0} business rule cannot be created. The rule contains an action to automatically generate a value for the Code attribute. ...
  23. The {0} command failed because either there is a missing - option or the name is not in quotes. All names that contain spaces ...
  24. The {0} contains a Function "{1}" which takes Argument "{2}" with data type Float but the value supplied has data type Decimal. ...
  25. The {0} contains a Function "{1}" with a literal set for Argument "{2}". This argument cannot take a literal set as a value. ...
  26. The {0} contains a Function "{1}" with an Argument "{2}" that is not valid. Cannot convert from a {3} entity key to a {4} ...
  27. The {0} contains a Function "{1}" with an Argument "{2}" that is not valid. The argument must contain a ParameterRef, a static ...
  28. The {0} contains a Function "{1}" with an Argument "{2}" that is not valid. The value of the argument is outside the range ...
  29. The {0} contains a Function "{1}" with the literal value "{3}" for Argument "{2}". The interval value must be one of the ...
  30. The {0} contains a Literal that has both or neither of the following elements: Value and Values. Literal must have exactly ...
  31. The {0} contains an AttributeRef that has both or neither of the following: AttributeID and AttributeName. AttributeRef must ...
  32. The {0} contains an Expression that has none or more than one of the following: Function, AttributeRef, EntityRef, ParameterRef, ...
  33. The {0} contains Details, but the Grouping {1} is not an EntityRef. The Grouping may contain Details only if the Grouping ...
  34. The {0} contains the function "Aggregate" with a non-aggregate argument. The Aggregate function can not take non-aggregate ...
  35. The {0} control '{1}' does not have a naming container. Ensure that the control is added to the page before calling DataBind. ...
  36. The {0} could not be registered with the MetadataWorkspace because its version ('{1}') is different from the version ('{2}') ...
  37. The {0} cube attribute cannot be used because this cube attribute is not related to the {1} cube attribute of the mining ...
  38. The {0} cube contains one or more measure groups linked from the same source database as the {1} dimension. Do you want to ...
  39. The {0} deployment failed with the following message: {1}. Please see the server log for further details. Operation ID: {2} ...
  40. The {0} dimension has the time type, but without time binding information. The dimension will be treated as regular dimension. ...
  41. The {0} does not contain any Groupings or MeasureGroups. SemanticQuery must contain at least one of these elements. This ...
  42. The {0} from the {1} to the {2} is optional, but the {3} is bound to a column. All roles involving entities bound to columns ...
  43. The {0} has none or more than one of the following: Function, AttributeRef, EntityRef, ParameterRef, Literal, Null. Expression ...
  44. The {0} mining model is not found. The mining model may have been deleted from the mining structure. Choose a different mining ...
  45. The {0} object could not be serialized. This type of object cannot be serialized when the RelationshipManager belongs to ...
  46. The {0} perspective no longer has a valid Default Measure because the measure specified as the default is not included in ...
  47. The {0} project cannot be added to the current solution because a project with either the same name or project file name ...
  48. The {0} property of the {1} references the {2}. Based on the Path used to reach the {2}, this property can only reference ...
  49. The {0} property of the {1} references the {2}. Based on the Path used to reach the {2}, this property can only reference ...
  50. The {0} property of the {1} references the {2}. This property must reference a Relation for which the Source is the {3} and ...
  51. The {0} returns a set of values for each instance of the {1}. This expression must return a single value for each instance ...
  52. The {0} subscription view cannot be created or updated. A subscription view with that name already exists for a different ...
  53. The {0} subscription view cannot be created. A subscription view with that name already exists. The view will be created ...
  54. The {0} table cannot be used as a lookup table because this table does not have a one-to-many relationship with the {1} table. ...
  55. The {0} uses a version of Visual Studio Tools for Application (VSTA) that is not supported in this release of Integration ...
  56. The {0} {1} instance cannot be found. Use the "MDSModelDeploy listservices" command to list the available service instances. ...
  57. The {0} {1}' contains a definition for the {2} {3}'. This field is missing from the returned result set from the data source. ...
  58. The {0} {1}' contains a definition for the {2} {3}({4})'. The data extension returned an error during reading the field property. ...
  59. The {0} {1}' contains a different number of ChartSeries elements than the number of StaticSeries elements. If the {0} contains ...
  60. The {0} {1}' contains a different number of DataPoints per ChartSeries element than the number of StaticCategory elements. ...
  61. The {0} {1}' contains a wrong number of DataCells per DataRow element. {2} DataCells per DataRow element are expected, because ...
  62. The {0} {1}' contains a wrong number of DataRow elements. {2} DataRow elements are expected, because there must be as many ...
  63. The {0} {1}' contains a {2} grouping level with both of the following: static and non-static groups. Multiple groups on the ...
  64. The {0} {1}' contains at least one PlotType setting, which is different from the default setting "Auto". The PlotType will ...
  65. The {0} {1}' has a CategoryGrouping with both or neither of the following: DynamicCategories and StaticCategories. CategoryGrouping ...
  66. The {0} {1}' has a ChartData element that contains a collection of {3} DataPoint element(s), which is different from the ...
  67. The {0} {1}' has a ColumnGrouping with both or neither of the following: DynamicColumns and StaticColumns. ColumnGrouping ...
  68. The {0} {1}' has a RepeatWith property. Data regions, subreports, and rectangles that contain a data region or subreport ...
  69. The {0} {1}' has a RowGrouping with both or neither of the following: DynamicRows and StaticRows. RowGrouping must have exactly ...
  70. The {0} {1}' has a SeriesGrouping with both or neither of the following: DynamicSeries and StaticSeries. A SeriesGrouping ...
  71. The {0} {1}' has a {2} using aggregates without explicit scopes and the {3} is omitted. Aggregates without an explicit scope ...
  72. The {0} {1}' has an Action that has more than one of the following: Hyperlink, BookmarkLink or Drillthrough. Action must ...
  73. The {0} {1}' has an incorrect number of {2}. The number of {2} must equal the number of innermost TablixMembers (TablixMembers ...
  74. The {0} {1}' has an incorrect number of {2}. The number of {2} must equal the number of levels in the TablixColumnHierarchy ...
  75. The {0} {1}' has an incorrect number of {2}. The number of {2} within TablixCornerRow at index: {3} must equal the number ...