SQL Server 2008
- The XML node returned by the XPath query '{0}' on the XML document at the root path '{1}' in the data store is neither an ...
- The XML page cannot be displayed Cannot view XML input using %3 style sheet. Please correct the error and then click the ...
- The xml schema collection for return parameter of module '%1!s!' has been altered while the batch was being executed. Please ...
- The xml schema collection for variable '%1!s!' has been altered while the batch was being executed. Remove all XML schema ...
- The XML schema data type information for "%1!s!" on element "%2!s!" has changed. Please re-initialize the metadata for this ...
- The XML script engine does not support script fragments. This error was probably caused by having a script tag with the language ...
- The XML Source Adapter was unable to process the XML data. An inline schema must be the first child node in the source Xml. ...
- The XML Source Adapter was unable to process the XML data. No inline schema was found in the source XML, but the "UseInlineSchema" ...
- The XML Source Adapter was unable to process the XML data. The content of an element can not contain a reference (ref) to ...
- The Xml source document contains the "xsi:nil" attribute with a value of true on the "{0}" element, therefore the element ...
- The Xml source document contains the fixed value for "{0}" of "{1}" which is not consistent with the value of "{2}" provided. ...
- The XP callback function '%1!s!' failed in extended procedure '%2!s!' because it was executed within an INSERT-EXEC statement ...
- The XP callback function '%1!s!' failed in extended procedure '%2!s!' because the extended procedure is called inside an ...
- The xp_cmdshell extended stored procedure runs operating system commands from within the Database Engine. Enable xp_cmdshell ...
- The xp_cmdshell extended stored procedure runs operating system commands from within the Database Engine. Enable xp_cmdshell ...
- The xp_cmdshell proxy account information cannot be retrieved or is invalid. Verify that the '%1!s!' credential exists and ...
- The XSLT path is invalid. It refers to an external resource, uses invalid syntax, or the XSLT was not found in the catalog ...
- The {0} '{1}' contains a set of TablixMembers with FixedData set to true in the TablixColumnHierarchy which is incompatible ...
- The {0} '{1}' contains an invalid {2} (Expected: {3}; Actual {4}). The {2} of inner or nested DataRegions must be the same ...
- The {0} '{1}' contains an invalid {2} Name, '{3}'. The name must be greater than 0 and less than or equal to {4} characters. ...
- The {0} '{1}' contains an invalid {2}. There is a {3} with an invalid {4} at level {5}. If there is a {3} with a {4} in this ...
- The {0} '{1}' has an inconsistent number of {2}Cells within the {2}Row. Each {2}Row must have the same number of {2}Cells. ...
- The {0} '{1}' has an incorrect number of TablixCells. The number of TablixCells in a TablixRow must equal the number of innermost ...
- The {0} '{1}' has an incorrect number of TablixRows. The number of TablixRows must equal the number of innermost TablixMembers ...
- The {0} '{1}' has an incorrectly set {2} properties within the {3}. All TablixMembers with FixedData set to true must be ...
- The {0} '{1}' has an incorrectly set {2} property within the {3}. Only the outermost TablixMembers in a hierarchy can have ...
- The {0} '{1}' has an incorrectly set {2} property. {2} is not allowed to be set on row TablixMember, unless it is also set ...
- The {0} '{1}' has an incorrectly set {2} property. {2} is not allowed to be set on the first column TablixMember when Tablix.GroupBeforeRowHeaders ...
- The {0} '{1}' has an invalid set of TablixCells. The combined value of the ColSpan properties of the TablixCells within a ...
- The {0} '{1}' has an invalid TablixCell. The {2} of the TablixCell is invalid. The TablixCell cannot span columns under TablixMembers ...
- The {0} '{1}' has an invalid TablixHeader. The {2} of the TablixHeader is invalid. The TablixHeader can only span one column. ...
- The {0} '{1}' has an invalid TablixHeader. The {2} of the TablixHeader is invalid. The TablixHeader can only span one row. ...
- The {0} '{1}' has an invalid TablixMember. The child TablixMember with Group name '{2}' is not a dynamic TablixMember and ...
- The {0} '{1}' has an invalid {2}. A {2} that is dynamic (i.e., has a Group specified) or has dynamic descendants must have ...
- The {0} '{1}' has an invalid {2}. The CellContents for this {2} must be omitted because it is covered by a span from another ...
- The {0} '{1}' has an invalid {2}. The {2} has an invalid {3}, '{4}'. Child {2} elements of Static {2} elements must be Dynamic ...
- The {0} '{1}' has an invalid {2}. The {2} has an invalid {3}, '{4}'. Non-Static {3} elements must contain at least 1 {5}. ...
- The {0} '{1}' has an invalid {2}. The {2} must have the same value set for the {3} property as those following or preceding ...
- 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' ...
- The {0} '{1}' is bound to a data source using the {2} data extension. The data extension returned an invalid database collation ...
- The {0} '{1}' was created, but an error occurred setting permissions. Use the object properties dialog to set permissions ...
- The {0} algorithm cannot be used, because it requires a KEY TIME column, which is not present in the {1} structure. Select ...
- The {0} contains a Function "{1}" which takes Argument "{2}" with data type Float but the value supplied has data type Decimal. ...
- The {0} contains a Function "{1}" with a literal set for Argument "{2}". This argument cannot take a literal set as a value. ...
- The {0} contains a Function "{1}" with an Argument "{2}" that is not valid. Cannot convert from a {3} entity key to a {4} ...
- The {0} contains a Function "{1}" with an Argument "{2}" that is not valid. The argument must contain a ParameterRef, a static ...
- The {0} contains a Function "{1}" with an Argument "{2}" that is not valid. The value of the argument is outside the range ...
- The {0} contains a Function "{1}" with the literal value "{3}" for Argument "{2}". The interval value must be one of the ...
- The {0} contains a Literal that has both or neither of the following elements: Value and Values. Literal must have exactly ...
- The {0} contains an AttributeRef that has both or neither of the following: AttributeID and AttributeName. AttributeRef must ...
- The {0} contains an Expression that has none or more than one of the following: Function, AttributeRef, EntityRef, ParameterRef, ...
- The {0} contains Details, but the Grouping {1} is not an EntityRef. The Grouping may contain Details only if the Grouping ...
- The {0} contains the function "Aggregate" with a non-aggregate argument. The Aggregate function can not take non-aggregate ...
- The {0} control '{1}' does not have a naming container. Ensure that the control is added to the page before calling DataBind. ...
- The {0} cube attribute cannot be used because this cube attribute is not related to the {1} cube attribute of the mining ...
- The {0} cube contains one or more measure groups linked from the same source database as the {1} dimension. Do you want to ...
- The {0} dimension has the time type, but without time binding information. The dimension will be treated as regular dimension. ...
- 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 ...
- The {0} has none or more than one of the following: Function, AttributeRef, EntityRef, ParameterRef, Literal, Null. Expression ...
- The {0} mining model is not found. The mining model may have been deleted from the mining structure. Choose a different mining ...
- The {0} perspective no longer has a valid Default Measure because the measure specified as the default is not included in ...
- The {0} project cannot be added to the current solution because a project with either the same name or project file name ...
- The {0} property of the {1} references the {2}. Based on the Path used to reach the {2}, this property can only reference ...
- The {0} property of the {1} references the {2}. Based on the Path used to reach the {2}, this property can only reference ...
- The {0} property of the {1} references the {2}. This property must reference a Relation for which the Source is the {3} and ...
- The {0} returns a set of values for each instance of the {1}. This expression must return a single value for each instance ...
- 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. ...
- The {0} uses a version of Visual Studio Tools for Application (VSTA) that is not supported in this release of Integration ...
- The {0} {1}' contains a definition for the {2} {3}'. This field is missing from the returned result set from the data source. ...
- The {0} {1}' contains a definition for the {2} {3}({4})'. The data extension returned an error during reading the field property. ...
- The {0} {1}' contains a different number of ChartSeries elements than the number of StaticSeries elements. If the {0} contains ...
- The {0} {1}' contains a different number of DataPoints per ChartSeries element than the number of StaticCategory elements. ...
- The {0} {1}' contains a wrong number of DataCells per DataRow element. {2} DataCells per DataRow element are expected, because ...
- The {0} {1}' contains a wrong number of DataRow elements. {2} DataRow elements are expected, because there must be as many ...
- The {0} {1}' contains a {2} grouping level with both of the following: static and non-static groups. Multiple groups on the ...