This section provides a detailed explanation and solution to the respective problems in the Report Viewer for parsing and processing the report.
The source of the report definition has not been specified.
The Report Viewer will not render the report when either the report path or stream is not set, or the given path is incorrect.
Provide Report Server information to get shared data source information.
Report with a shared data source must contain the Report Server information and credentials that are provided to render in the Report Viewer.
Make sure that the credentials in the Report Server URL are not empty and ensure that the correct information is provided to the Report Viewer. For example, refer to the below code.
Viewer.ReportServerUrl = @"https://demos.boldreports.com/services/api/ReportViewer";
Viewer.ReportServerCredential = new System.Net.NetworkCredential("username", "password");An error occurred while sending a request to the reporting service.
Report will not be rendered when there is a problem while connecting or retrieving the data from the provided reporting service’s URL.
If not, start the reporting service from the desktop shortcut (for example: Start BoldReports in IIS) or from an installed location.
Installed location path: (C:\Program Files (x86)\Bold Reports\Enterprise Reporting\Utilities\DeployIIS)
The report definition has an invalid schema version.
Report definition should contain the supported schema version (for example, 2008) to render the report in the Report Viewer.
Make sure that the provided schema in your report definition is supported in the Report Viewer. Supported versions are 2008, 2010, and 2016.
The requested file or assembly was not found. It may have either moved or renamed.
Any of the assembly related to the report platform is missing at the installation location.
(C:\Program Files (x86)\Bold Reports\Report Designer) or reinstall the Report Designer application.(C:\Program Files (x86)\Bold Reports\Embedded Reporting\Assemblies) or reinstall the Report Platform SDK application.(C:\Program Files (x86)\Bold Reports\Enterprise Reporting\Utilities\DeployIIS) or reinstall the Report Server application.Note: Please contact Syncfusion® support if you cannot resolve the issue.
Expressions are not used within the scope.
Report Viewer encounters an error when an expression must be used outside the scope.
Provide a valid expression within the scope. Note: Detailed description with the line number and position is mentioned in the Report Viewer instance error dialog.
An error occurred during the local report processing. There is an error that occurred while rendering the custom code.
Report Viewer encounters an error when compiling the custom code used in the report.
Provide valid custom code in your report based on detailed information mentioned in the Report Viewer instance error dialog. Note: Custom code exists in report properties.
The Value property of an image report item contains an invalid value.
Report will not be rendered to the Report Viewer when you try to use invalid image data or a non-existing image in the report.
Ensure that the value provided to the image report item is specified properly, and make sure that the image is available.
The data source used in a report does not exist or not accessible.
Report will not be rendered in the Report Viewer when the data source used in a report does not exist or it is not accessible due to permission rights.
Ensure whether the data source in a report exists in the referred location.
Fields cannot be used in report parameter expressions.
Report Viewer does not render the report when the parameter contains field expressions and fields cannot be used in report parameter expressions.
Remove the field expressions used in parameter expressions.
Forward dependencies are not valid.
Report will not be rendered when there is an existence of forward dependencies between parameters.
Make sure to remove the forward dependencies in your report definition before previewing the report. Example: First Parameter depends on Dataset 1 and Dataset 2 depends on Second Parameter, and then it results in forward dependency. Note: Parameters are executed based on the order.
Please select a value for the report parameter.
Report parameters must be supplied with values if it is non-nullable while trying to preview the report in the Report Viewer.
Enter the value of the parameter in a parameter block when it is non-nullable or allow blank.
The expression that references the parameter is not valid and does not exist in the parameter collection or forward dependencies.
Report Viewer throws errors when you try to use a non-existing report parameter or with forward dependencies.
Make sure to use the parameters that exist report definition and avoid forward dependencies in the report. Note: Letters in the names of parameters should be in the correct case.
The value provided for the report parameter is not valid for its type.
The report will not be rendered by the Report Viewer when the specified value for the report parameter is irrespective of its type.
Provide an appropriate value for the report parameter based on its data type while rendering the report. Example: A parameter with an integer data type allows integer values, not float values.
Report item refers to an invalid DataSetName.
Report will not be rendered in the Report Viewer when a non-existing dataset is used in the report.
Collection class or data table input is needed.
To render the RDLC report in the Report Viewer, the report must have a collection class or data table input to rendering the report.
Make sure to provide dataset collection to render the report. Supported collections are IEnumerable, System.Data.DataTable, and System.Data.Dataset.
Report variable or group variable reference cannot be used in report parameter expressions.
Report Viewer does not render the report when the parameter contains group or report variables. Variable values cannot be used in report parameter expressions.
Remove the variable reference used in the parameter expressions.
An invalid operator is used in expression.
Report Viewer encounters an error if it contains an invalid operator in an expression.
Make sure to use appropriate and supported operators in the expression. Note: Detailed information is provided with the expression, and the report item name is mentioned in the Report Viewer instance error dialog.
Data region items are not allowed in reports without datasets to render in the Report Viewer.
Report Viewer will not render the report when the data region items does not refer to the dataset.
Make sure to provide the dataset name property value in your report definition. Note: Report will render when the report definition has a single dataset; When the dataset count is greater than one, you must specify the dataset name property value to data region items (Tablix, Chart, Gauge, etc..).
Toggle items must be text boxes that share the same scope, and they are not allowed in page headers or footers.
In our Report Viewer, toggle items must be shared within the same scope, and they are not allowed in page headers and page footers.
Provide toggle items in the report in the same scope, not from their page header or page footer. Example: If a report item in the page header contains a toggle item, then the referred toggle item should be in the header region.
A ReportName cannot be an empty string or just white space.
In SubReport item, the ReportName property value cannot be an empty or just white space.
Make sure that the ReportName property value for the subreport item is not empty.
Aggregate and lookup functions cannot be used in report parameter expressions.
The value expression is used for report parameter, it includes an aggregate or lookup function. Aggregate and lookup functions cannot be used in report parameter expressions.
Remove Aggregate and Lookup functions in your report parameter expressions.
Lookup function has an incorrect number of parameters.
Provided lookup function has an incorrect number of parameters in report definition.
Provide the correct number of arguments for lookup expressions in respective report item expressions and refer to the syntax of the lookup expressions.
ReportItem expressions can be referred only to fields within the current dataset.
ReportItem expressions can be referred only to fields within the current dataset. Make sure that the field expression is referred to the current dataset.
Provide current dataset fields for report item expression.
Note: Tablix report item with scope Dataset1 must contain the fields in the dataset1. If field expression specified in another dataset is required, then you should specify the scope.
Example: =First(Fields!Name.Value, "Dataset2")
Each dataset, data region, or grouping in the report has different name for their report item. Dataset, data region, and grouping names must be unique within a report.
Report item referred dataset, data region, and grouping names must be unique within a report.
Provide a unique dataset, data region, and grouping name for their report item in your report definition.
An error has occurred on the Report Server.
Specified reporting service encounters an error while rendering the report in the Report Viewer.
(C:\Program Files\Bold Reports\Enterprise Reporting\idp\web\Logs)The value expression for the TextRun contains a colon or a line terminator.
The Textbox report item value expression contains a colon or a line terminator. Colons and line terminators are not valid in expressions.
Remove colons and line terminator used in the specified report item expression.
Cannot load sub report.
Sub report cannot be loaded with an invalid name or report path.
The subreport cannot be found at the specified location.
Report will not be rendered in the Report Viewer when the report does not exist in the specified location.
Make sure that the report name or path is correct, and the report exists in the specified directory.
Subreport cannot be shown.
Report Viewer will not render the sub report without the ReportPath or ReportServerUrl.
Provide a subreport ReportPath or ReportServerUrl in your report.
The tablix has a detail member with inner members. Detail members contain only static inner members.
In the tablix report item, detail members contain only static inner members.
In the tablix report item, provide static inner members for their detail members.
The tablix report item has an invalid Tablix member in the column hierarchy, and the KeepTogether property is not set to None.
All tablix member elements in a TablixColumnHierarchy must have the KeepWithGroup property as None.
Set KeepWithGroup property as None in a TablixColumnHierarchy for all Tablix members in the tablix report item.
Report Deserialization failed.
An error occurred during the deserialization of the report definition.
Provide Report Server information to get shared dataset information.
Report with shared datasets must contain the Report Server information and credentials to render in the Report Viewer.
Make sure that the credentials in the Report Server URL are not empty and ensure that the correct information is provided to the Report Viewer.
Example: Viewer.ReportServerUrl = @"https://demos.boldreports.com/services/api/ReportViewer"; Viewer.ReportServerCredential = new System.Net.NetworkCredential("username", "password");
The ReportServerUrl or ReportServerCredential is missing.
Server report or server referred items used in the report will not be rendered in the Report Viewer without ReportServerUrl and ReportServerCredential.
Make sure that the ReportServerUrl and ReportServerCredential are not empty and provided with proper data and are accessible.
The value for the DataSetName property is missing.
Data region items are not allowed in reports without datasets to render in the Viewer.
Make sure to provide a dataset name property value in your report definition and ensure that the property value is not empty.
Provide dataset inputs for the report.
To render the RDLC report, you must add the data source collection in the Report Viewer if any dataset is used in the report.
Make sure to add the dataset to render the report in Report Viewer if dataset fields are used.
Example: Viewer.DataSources.Add("Dataset1", object collection of data)
Note: Here, name (“Dataset 1”) is the dataset name used in the report definition.
Invalid Expression
Report Viewer does not render the report when an invalid expression is used.
Provide valid expressions in the respective report item. Note: Detailed description with line number and position is mentioned in the Report Viewer instance error dialog.
Unsupported Expression
Provided expression does not support in the Report Viewer. Object expressions do not have complete support.
Please use supported expressions in the Report Viewer to render the report.
The DateAdd function should have arguments.
Report Viewer encounters an error if DateAdd function does not contain any arguments.
Provide arguments for DateAdd function in the respective report item expression and refer to the syntax of the DateAdd function.
Example: =DateAdd("d",3,Fields!BirthDate.Value)
The DateDiff function should contain arguments.
Report Viewer encounters an error if DateDiff function does not contain arguments in an expression.
Provide arguments for DateDiff function in the respective report item expression and refer to the syntax of the DateDiff function.
Example: =DateDiff("yyyy",Fields!BirthDate.Value,"1/1/2010")
PaymentPeriod must be between 1 and numberOfPayments.
Report Viewer encounters an error if the payment period does not fall within the range.
Provide payment period value between 1 and numberOfPayments.
This implementation does not handle zero interest rate.
Report is not rendered in the Report Viewer when it holds the zero interest rate.
Provide greater than 0 or less than 0 interest rate. Does not provide 0 value for their interest rate.
Invalid Expression
The expression used in the report is incorrect scope, syntax, or unsupported.
Ensure that the expression used in the report is correct with valid scope and syntax. Note: Detailed information of report item along with line number and position is mentioned in the Report Viewer instance error dialog.
Method name is not a member in custom code.
Evaluated method name is not a member in your custom code.
Provide a valid method name. Make sure that the provided method name is present in your custom code.
Parameter is missing a value.
Report Viewer will not render the report when the hidden parameter does not contain a value that is non-nullable.
Provide value to hidden parameters in your report definition before rendering the report.
Note: Hidden parameters must contain a default value, or it should be nullable.
The report path value cannot be null or empty.
This error occurs when the ReportPath property of the Report Viewer is not assigned a valid report definition path.
Provide the valid relative or absolute path location of the report in the ReportPath property. Example: reportViewer.ReportPath = ../ReportTemplate.rdl;
The path {0} specified for the report is not valid or not found.
This error indicates that the path assigned to ReportPath either points to a non-existent report or is incorrectly formatted.
Ensure the valid report path is specified in the ReportPath property or make sure that the specified report exists and is accessible in the provided location.
The {0} file input stream is null.
This error is thrown when attempting to load a report using a stream, but the stream provided is null.
Make sure that the provided file input stream is not empty/null.
Example: reportViewer.LoadReport(reportStream);
The stream input is not available for the report subreport {0}.
This occurs when a subreport is expected, but the stream for the subreport is missing or not supplied.
To load a subreport, make sure to set the stream input in the LoadSubreport definition.
Example: reportViewer.LoadSubreport(subReportName, subReportStream);
The report server URL specified is invalid.
This error occurs when the ReportServerUrl provided to the viewer is incorrect or unreachable.
Provide the valid report server URL of a report in the ReportServerUrl property to load the server report.
Example: reportViewer.ReportServerUrl = @'http://localhost/reportserver';
The credentials required to access the report server are not supplied.
This error occurs when the ReportServerUrl provided to the viewer is incorrect or unreachable.
Specify report server credentials in the report viewer to access the report server.
Example: reportViewer.ReportServerCredential = new NetworkCredential('userName', 'password');
The server report details have been given and the processing mode set to local incorrectly.
This occurs when the processing mode is set to Local but server-related settings like ReportServerUrl are also specified, which causes a conflict.
Ensure the provided processing mode is correct. ‘Remote’ for server report processing and ‘Local’ to process a local report.
Example:
reportViewer.ProcessingMode = ProcessingMode.Remote //For remote processing
reportViewer.ProcessingMode = ProcessingMode.Local //For local report processing.
The provided credentials are invalid to access the report server. Login failed for user ‘{0}‘.
This error indicates that the authentication credentials supplied to the report server are incorrect.
Make sure that the provided credentials are valid to access the report server.
Example: reportViewer.ReportServerCredential = new NetworkCredential('userName', 'password');
Failed to retrieve the {0} ‘{1}’ stream from the provided server details ‘{2}’
This error occurs when the Report Viewer cannot retrieve a resource (like a report or subreport) from the report server due to incorrect server configuration or missing files.
Provide the valid report server information (ReportServerURL, ReportServerCredential, ReportPath) to retrieve the report stream from server.
An error occurred in communicating to the reporting service.
This error is thrown when there is a network or configuration issue preventing the Report Viewer from connecting to the report server.
Verify that the report server is reachable and that correct details are provided. Also, ensure that firewalls or proxies are not blocking communication.
The report definition is not valid.
This error occurs when the report definition (.rdl/.rdlc file) is invalid or corrupted. It may happen if required elements are missing or incorrectly formatted in the XML schema.
Ensure that the provided report has a valid report definition. Example : Report element missing in .rdl file.
An unexpected error occurred in Report Processing during serialization: {0}.
This error occurs when the Report Viewer encounters an unexpected issue during the report processing or serialization stage, often caused by corrupt data or misconfigured objects in the report.
Review the provided exception message {0} for more insight. Validate all expressions and report objects. Also, confirm the report does not contain circular references or unsupported data types.
The report definition is not valid or has an unsupported element by this version of ReportDefinition schema. The report definition contains XML that is not well formed or the XML is not valid based on the Report Definition schema. Details: {0}
This error occurs when the report uses an unsupported ReportDefinition schema version or contains elements not recognized by the current Report Viewer.
Make sure that the provided schema in your report definition is supported in report viewer. Supported versions are 2008, 2010, and 2016.
The dependent assembly was not found. It may have been either moved or renamed.
The dependent assembly was not found. It may have been either moved or renamed.
Ensure that dependent assemblies of report viewer exist in the referenced location. Check whether the assembly is missing at the installed location. If you are loading the report from report
designer : (%ProgramData%/Syncfusion/Report Designer/ReportDesigner)
SDK : (%ProgramData%/Report Platform SDK/Assemblies)
ReportServer : (%ProgramData%/Report Server/ReportServer.Web\bin)
The expression used for the language of ‘{1}’ refers to a field. Fields cannot be used in report language expressions.
This error occurs when a field expression is incorrectly used in the reports Language property.
Make sure to avoid the usage of field expressions in report language expressions.
The number of columns specified for the report body is not valid. The number of columns must be between 1 and 100.
This error is thrown when the column count defined in the report body layout is outside the valid range.
Ensure that the number of columns in the rdl/rdlc report are in the range from 1 to 100.
The {0} {1} is in the page header or footer and has a {2}. {2} cannot be used by a {0} in the page header or footer.
This error occurs when unsupported items (like a tablix or chart) are placed inside page headers or footers.
Make sure that a designed report contains report items in valid regions. Data visualization items (Tablix, chart, gauge, map, sparkline, databar, indicator) cannot be used in page headers or footers.
The {0} ‘{1}’ contains a {2} with a duplicate name, ‘{3}‘. {2} names must be unique within the report.
This error is thrown when two or more report items share the same identifier, which must be unique.
Ensure that the report contains a unique report item or group name.
A {2} in the {0} ‘{1}’ has an invalid {2} name, ‘{3}‘. {2} names must be CLS-compliant identifiers.
This error occurs when a name assigned to a report item or variable violates Common Language Specification (CLS) naming rules.
Provide the report item, variable, or group name with a valid format. The name should not contain spaces, and it must begin with a letter followed by letters, numbers, or the underscore character.
A {2} in the {0} ‘{1}’ has an invalid {2} name, ‘{3}‘. {2} names must be greater than 0 and less than or equal to {4} characters.
This error is caused when the name of a report element (like a variable or group) is either empty or exceeds the allowed length.
Provide a valid variable name: the name should not be empty or longer than 256 characters.
The {2} expression for the {0} ‘{1}’ refers to the global variable Aggregates, which is not defined.
This error occurs when an expression in a report references a global variable or collection named Aggregates, which is either undefined or incorrectly used in the current scope.
Ensure that the expression contains valid global collection variant types.
The First, Last aggregate functions cannot be specified as nested aggregates.
This error occurs when First() or Last() functions are used inside other aggregate functions (like Sum(First(...))), which is not supported.
Remove the First, Last aggregate functions used in nested expressions.
The expression that references the variable ‘{0}’ does not exist in the Variables collection. Expressions can only refer to variables within the report scope or a containing grouping scope. Letters in the names of variables must use the correct case.
This error is triggered when a report expression refers to a variable that hasn’t been defined in the scope or has incorrect casing.
Specify the valid variables in an expression that exists in the report definition. The name must match an item/group/data set in a report.
There is an error on line {4} of custom code: {3}
This error occurs when the custom embedded code in the report fails to compile due to a syntax or runtime error.
Make sure that the provided custom code is compiled successfully without an error.
More than one class instance in the report has the name ‘{1}‘. Class instance names must be unique within a report.
This error occurs when multiple code class instances in the report share the same name.
Provide a unique class instance name and ensure that the InstanceNames of a two or more classes are different in a report.
Error in class instance declaration for class {1}: {3}
This error indicates a problem in the class instance declaration, such as incorrect syntax, invalid reference, or missing class in custom code.
Modify the class instance declaration and ensure there is no compile error.
Failed to load assembly. Details: {3}
This error is triggered when a required assembly (DLL) referenced in the report cannot be found or loaded.
Add the assemblies to the Assemblies API in the Report Viewer.
Error while loading code module: ‘{3}‘. Details: {4}
This error occurs when a report references a code module that is either missing, corrupted, or improperly referenced.
Ensure that elements of Report.CodeModule exist in a report to use in the expression.
The report references the code module {3}, which is not a trusted assembly.
This error indicates that the report tries to use a code module that is not whitelisted or trusted in the current environment.
Add the trusted assembly references in the code module.
The report contains an invalid embedded image name, {1}. Embedded image names must be greater than 0 and less than or equal to {3} characters.
This error occurs when the name assigned to an embedded image is missing or exceeds the allowed length.
Provide the valid name in the Name property of EmbeddedImage; name length must be greater than zero and fewer than 256 characters.
More than one embedded image in the report has the name {1}. Embedded image names must be unique within a report.
This error occurs when multiple embedded images share the same name, which must be unique within a report definition.
Provide a unique name in EmbeddedImage and ensure that the name properties of two or more EmbeddedImages are different within the same report.
The report contains an embedded image with an invalid name {1}. Embedded image names must be CLS-compliant identifiers.
This error is thrown when the image name does not follow Common Language Specification (CLS) rules.
Provide the name property of EmbeddedImage with a valid format. The name should not contain spaces, and it must begin with a letter followed by letters, numbers, or the underscore character.
The embedded image {1} contains invalid data. Embedded image data must be a base 64 encoded string.
This error indicates that the image data stored in the embedded image node is not valid Base64-encoded data.
Make sure that the embedded image data is in the proper format.
The value of the {2} property for the {0} {1} is “{3}”, which is not a valid {2}.
This error occurs when a report property (like MIMEType or Source) is assigned an invalid or unsupported value.
Use the existing embedded image within a report, ensure that the provided image exists in the Report.EmbeddedImages element in an RDL file.
The report contains an invalid data source with the name {1}. Data source names must be greater than 0 and less than or equal to {3} characters.
This error occurs when the Name property of a DataSource is missing or exceeds the allowed length.
Provide the valid name in the ‘Name’ property of DataSource. Name length must be greater than zero and fewer than 256 characters.
The report contains an invalid data source with the name {1}. Data source names must be CLS-compliant identifiers.
This error occurs when the data source name includes invalid characters or formatting that violates CLS (Common Language Specification) naming rules.
Specify the name property of DataSource with a valid format. The name should not contain spaces, and it must begin with a letter followed by letters, numbers, or the underscore character.
The data source {1} has both or neither of the following: DataSourceReference and ConnectionProperties. The data source must have exactly one of these elements.
This error occurs when a data source is not properly configured. It must either reference a shared data source or provide connection properties for an embedded one, but not both or neither.
Provide a valid data source. A data source with same name must contain one of the following items in a report:
DataSourceReference—Specifies for shared data source.
ConnectionProperties—Embedded for data source.
The expression that references the data source ‘{0}’ does not exist in the DataSource collection. Letters in the names of data sources must use the correct case.
This error occurs when an expression refers to a non-existent or incorrectly cased data source name.
Use the existing data source name within a report, ensure that the provided data source exists in the DataSource element in a RDL file.
The type of the data source has not been specified.
This error occurs when the report’s data source type is empty.
Data source type must not be empty, type must be Shared or Embedded.
The data set {1} refers to the data source “{3}”, which does not exist.
This error occurs when a dataset references a data source that is not defined in the report.
Use the existing data source name within a report, ensure that the provided data source exists in the DataSource element in a RDL file.
More than one data source in the report has the name {1}. Data source names must be unique within a report.
This error occurs when duplicate names are used for different data sources in the same report.
Provide a unique name attribute in DataSource and ensure that the name properties of two or more data sources are different within the same report.
One or more data source credentials required to run the report have not been specified.
This error appears when secure data sources require authentication, but credentials are missing.
Specify the credentials to preview the report.
Error during processing of the ConnectString expression of data source {0}.
This error occurs when the ConnectString expression for a data source is incorrect or invalid.
Specify the valid connection string for the data source element in a report definition.
Enter a user name and password to access the data source:
This prompt is shown when the data source is protected and requires user credentials, but none were supplied.
Provide the user name and password to access and retrieve the data from the data source.
Data cannot be retrieved for ‘{1}’ dataset, Error Detail: ‘{4}’
This error occurs when the report viewer fails to retrieve data for the specified dataset due to permission issues or connectivity problems.
Ensure that permission is granted to create/access the data source.
Cannot impersonate user for data source ‘{0}‘.
This error occurs when impersonation is attempted with invalid or missing credentials, or the hosting environment doesn’t support impersonation.
Cannot create command for data source ‘{0}‘.
This error occurs when a command object cannot be created for the given data source.
Failed to commit transaction for data source ‘{0}‘.
This error occurs when the report’s attempt to commit a database transaction fails, possibly due to a connection error or database issue.
Failed to roll back transaction for data source ‘{0}‘.
This error occurs when a transaction rollback operation fails, typically due to connection loss or internal server/database failure.
Failed to close connection for data source ‘{0}‘.
This error appears when the report viewer cannot close a data source connection, possibly due to a lingering process, open reader, or a connection issue.
The data source ‘{0}’ uses a custom data processing extension that cannot be accessed.
This error occurs when a data source refers to a custom extension (like a plug-in or third-party connector) that is missing, not deployed correctly, or inaccessible at runtime.
Make sure that the custom data extension used in a data source exists and is accessible.
The {2} expression for the {0} {1} refers to a non-existing data source {3}. Letters in the names of data sources must use the correct case.
This error occurs when an expression references a data source name that does not exist or is misspelled (including casing mismatches) in the report definition.
Use the existing data source within a report and ensure that the provided data source exists in the DataSources global collection.
The expression used for the parameter {1} in the data set {3} refers to a data source. Data sources cannot be used in query parameter expressions.
This error occurs when a dataset query parameter improperly attempts to access or evaluate a data source object.
Modify the expression in the query parameter value that references the data source global collection in a report.
The expression used for the language of ‘{1}’ refers to a data source. Data sources cannot be used in report language expressions.
This error occurs when the Language property of the report attempts to derive its value from a data source, which is not allowed.
Modify the expression in the Report.Language property that references the data source global collection in a report.
A {2} expression used for the report parameter {1} refers to a data source. Data sources cannot be used in report parameter expressions.
This error occurs when a report parameter expression attempts to use the data source collection, which is not valid in that context.
Modify the expression in the ReportParameter RDL element if it references the data source global collection in a report.
The {2} expression for the {0} {1} refers to a data source. Data sources cannot be used in page headers or footers.
This error occurs when an expression in a header or footer attempts to access a data source, which is disallowed because headers and footers cannot access data-bound content directly.
Modify the expression in the PageHeader and PageFooter RDL elements if it references the data source global collection in a report.
More than one report parameter in the report has the name {1}. Report parameter names must be unique within a report.
This error occurs when two or more report parameters share the same name, causing conflicts in reference and evaluation.
Provide a unique name for ReportParameter in the ReportParameters collection. Ensure that the name properties of two or more ReportParameters are different within the same report.
More than one report parameter in the report has the (case-insensitive) name {1}. Report parameter names that only differ in case should be avoided.
Even though parameter names may technically differ by case, case-insensitive environments can lead to ambiguity or runtime conflicts.
Provide a unique ReportParameter name. Ensure that the parameter name is different, including case.
{1} is not a valid {0} name. Parameter names must be greater than 0 and less than or equal to {3} characters.
This error occurs when the parameter name is either empty or exceeds the maximum allowed length (typically 256 characters).
Provide the valid name in the ‘Name’ property of the ReportParameter element. The name length must be greater than zero and fewer than 256 characters.
A parameter in the {0} {1} has the name {3}. Parameter names must be CLS-compliant identifiers.
This error indicates that a parameter name contains invalid characters or formatting. It must follow CLS (Common Language Specification) naming rules.
Specify the name property of ReportParameter with a valid format. The name should not contain spaces, and it must begin with a letter followed by letters, numbers, or the underscore character.
More than one parameter in the {0} {1} has the name {3}. Parameter names must be unique within a {0}.
This error occurs when duplicate parameter names exist within the same context (Example: multiple parameters with the same name in the ReportParameters collection).
Provide a unique name attribute in ReportParameter and ensure that the name properties of two or more ReportParameters in the ReportParameters collection are different within a same report.
A {2} expression used for the report parameter {1} refers to a field. Fields cannot be used in report parameter expressions.
This error occurs when a report parameter expression references a Fields! collection, which is not accessible outside of a data region.
Modify the expression in the ReportParameter RDL element if it references Field from the Fields global collection in a report.
The report parameter {1} has a DefaultValue that has both or neither of the following: Values and DataSetReference. DefaultValue must have exactly one of these elements.
This occurs when the default value is incorrectly configured—either both a static value and dataset reference are provided, or neither is provided.
Specify the default value of a ReportParameter as one of the following: None, specific value, data set value. None is the default value.
The report parameter {1} has a DefaultValue that has a Values collection containing more than one value. For single-value parameters, only the first value in the Values collection will be used.
This warning/error appears when multiple default values are set for a parameter that only accepts a single value.
Provide the single default specific value for ReportParameter when the parameter is Single-Values (Multivalue is set to false).
The report parameter {1} is a multiple value parameter and accepts a null value. This is not allowed.
Multi-value parameters cannot accept null values because null cannot be included in a selection of multiple values.
Ensure that both the Multivalue and Nullable properties of ReportParameter are set to true. Since the Multivalue parameter does not accept a null value, remove Nullable.
The report parameter {1} has multiple default values and is not a multiple value parameter.
This error occurs when more than one default value is assigned to a parameter that is configured as single-valued.
ReportParameter contains multiple default values but Multivalue is not enabled. Set the Multivalue property value to true to use multiple default values.
The report parameter {1} has a ValidValues that has both or neither of the following: ParameterValues and DataSetReference. ValidValues must have exactly one of these elements.
This occurs when valid values are improperly defined using both static entries (ParameterValues) and a dataset (DataSetReference) or none at all.
Specify the valid value of a ReportParameter as one of the following: None, specific value, data set value. None is the default value.
The report parameter {1} valid values refers to a data set “{3}”, that does not exist.
This error occurs when the DataSetReference for valid values points to a dataset that isn’t defined in the report.
Provide the valid data set name in the DataSetReference element when ValidValue for ReportParameter is specified from a data set.
The parameter {1} has no default. A default is required for all non-nullable parameters that are defined as read-only.
A read-only parameter that doesn’t allow null values must have a default value set, since the user cannot provide input.
Provide a default value for all non-nullable parameters.
The parameter {1} has no default. A default is required for all non-nullable parameters without a prompt or the valid values list has to contain Null.
Non-nullable parameters that don’t prompt the user must be assigned a default value. Otherwise, the report cannot resolve the parameter value.
Specify a default value for all non-nullable parameters or ensure that valid value contains a ‘Null’ value.
The report parameter {1} default value refers to a data set “{3}”, which does not exist.
This error occurs when a report parameter’s default value references a dataset name that is not defined in the report.
Provide the valid data set name in the DataSetReference element when a default value for ReportParameter is specified from a data set.
The report parameter {1} has a DefaultValue or a ValidValue that depends on the report parameter “{3}”. Forward dependencies are not valid.
A forward dependency occurs when one report parameter depends on the value of another parameter that appears later in the evaluation order.
Remove the forward dependency of ReportParameter. Make sure that the dependent order of a parameter is correct.
The value of parameter ‘{0}’ is not valid or null.
The parameter has either not been provided a value or was given an invalid/null value that is not acceptable due to its constraints.
Add the valid value to ReportParameter
A {2} expression used for the report parameter {1} refers to a parameter. Parameters cannot be used in report parameter expressions.
This error occurs when a report parameter expression references another parameter, which is not supported in certain expression contexts.
The {2} expression for the {0} {1} refers to a non-existing report parameter {3}. Letters in the names of parameters must use the correct case.
An expression references a report parameter that does not exist in the report definition, or the name is misspelled or has incorrect casing.
Modify the non-existing ReportParameter expression in the subreport or Drillthrough Parameters collection in a report with a valid parameter.
One or more parameters required to run the report have not been specified.
Required parameters were not supplied when attempting to render or preview the report.
Provide the valid value to ReportParameter while previewing the parent/child report.
The {2} property of {0} {1} is false. However, the ‘{3}’ property contains a value that violates the {2} property condition.
This error occurs when a parameter property setting (Example: AllowBlank=false) is violated by the provided value (Example: an empty string).
Provide the valid value to ReportParameter based on its property value. For example: If a report parameter AllowBlank property value is false, then the parameter value must be non-empty.
Error during processing of {0} report parameter. The {1} property of the report parameter {0} references the value of field {2} in data set {3}, which contains an error: {4}
An error occurred while evaluating a parameter value that references a field in a dataset. The underlying dataset or field contains an error.
Error during processing of {0} report parameter.
A generic error occurred while processing the report parameter, typically due to an invalid expression, data type mismatch, or missing data.
The property {2} of {0} {1} doesn’t have the expected type.
The value assigned to a parameter or its property (Example: default value) does not match the expected data type defined in the report.
Specify the valid value or default value of ReportParameter with respect to its data type.
Parameter validation failed. It is not possible to provide valid values for all parameters.
Report parameter validation failed because not all parameters were supplied with valid or non-null values, making it impossible to execute the report.
The value ‘{0}’ is invalid. Valid values are between ‘{1}’ and ‘{2}‘.
The input value provided is outside the valid range defined for the parameter.
The {2} expression used in {0} {1} returned a numeric value that cannot fit in an Int32. In the target report, consider modifying the type of parameter ‘{3}’ to Text to be able to represent the numeric value.
An expression resulted in a numeric value that is too large to be represented as an Int32 data type.
Specify the value to report parameter with the correct format or else change the parameter type to Text to avoid casting errors.
The {0} {1} refers to an invalid {2} {3}.
A reference in the report points to an invalid or non-existent element such as a DataSet, ReportItem, or Parameter.
Specify the valid DataSetName property of an element, ensure that the data set name exists in the DataSets global collection.
A field in the data set {4} has the name {3}. Field names must be greater than 0 and less than or equal to {5} characters.
A field name in the dataset exceeds the allowed length or is missing.
Provide the valid name in ‘Name’ property of Field element, name length must be greater than zero or less than 256 characters.
A field in the data set {4} has the name {3}. Field names must be CLS-compliant identifiers.
The field name in the dataset is not a CLS-compliant identifier.
Provide the name property of data set Field with a valid format. The name should not contain spaces, and it must begin with a letter followed by letters, numbers, or the underscore character.
The data input collection null or empty for the data set : ‘{0}’ is used in the report.
The dataset used in the report has no input data or is null.
Provide data set inputs to preview the report in ReportViewer.
The data value input is not supplied for the data set ‘{0}‘.
No value was supplied for a dataset required by the report.
Provide data set values to the DataSet element to preview the report in ReportViewer.
The value input is not a supported data type for the data set ‘{0}‘.
The input data type for the dataset is unsupported.
Reporting controls support the following types, so provide input in any one of the following formats:
IEnumerable
System.Data.DataTable
System.Data.Dataset
The {0} {1} must define either a Query or a SharedDataSetReference, but not both.
A dataset cannot define both a Query and a SharedDataSetReference.
Provide a valid data set query. A data set with same name must contain one of the following items in a report: SharedDataSetReference—Specifies shared data set; Query—Embedded data set.
The report parameter {1} uses the field {3} in a data set reference, but the data set {4} does not contain that field.
A report parameter references a field in a dataset, but the field does not exist in that dataset.
Use the existing data set reference ‘Field’ in ReportParameter.
The data set {0} refers to a shared data set “{1}”, which is not available.
The dataset refers to a shared dataset that is not available or not published on the report server.
Use the existing data set name within a report, ensure that the provided shared data set exists in ReportServer or make sure that the permission is available.
The shared data set definition is not valid. Details: {3}
The shared dataset definition is invalid due to an internal error.
Provide the valid data set definition, make sure that SharedDataSet is accessible.
The expression that references the data set ‘{0}’ does not exist in the DataSets collection. Letters in the names of data sets must use the correct case.
An expression references a dataset that does not exist or has a case-sensitive mismatch.
Use the existing data source name within a report, ensure that the provided data source exists in the DataSource element in a RDL file.
The shared data set definition is not valid.
The shared dataset definition is not valid due to incorrect syntax or schema violation.
SharedDataset definition is not valid, provide the definition as per schema standards.
The data set {1} refers to the shared data source {3}, which is not published on the report server. The shared data source {3} must be published before this {2} can run.
The dataset references a shared data source that is not yet published on the server.
Publish the data source to ReportServer to set as DataSourceReference in DataSource element.
The {2} expression for the {0} {1} refers to a non-existing data set {3}. Letters in the names of data sets must use the correct case.
An expression refers to a dataset that does not exist in the report.
Use the existing data set within a report, ensure that the provided data set exists in the DataSets global collection.
The data set {1} refers to the shared data set {3}, which is not published on the report server. The shared data set {3} must be published before this report can run.
The report references a shared dataset that is not published.
Publish the data set to ReportServer to make the set a SharedDataSetReference in the DataSet element.
The {0} ‘{1}’ specifies zero fields.
The dataset defines no fields, making it unusable in the report.
Add the fields to the DataSet element in a report definition.
The field with the name {1} in the data set {3} has both or neither of the following properties: DataField and Value. Fields must have exactly one of these properties.
A field in the dataset is defined with both DataField and Value properties, or neither, which is invalid.
Ensure that the Field element in the report data set contains only one of the following properties: DataField, Value. It should not contain both properties.
More than one field in the data set {4} has the name {3}. Field names must be unique within a data set.
This occurs when two or more fields in a dataset are assigned the same name, which causes ambiguity during report processing.
Ensure that the Field element contains a unique name attribute in Dataset. Modify the data set fields with unique names.
The {0} ‘{1}’ contains a definition for the {2} ‘{3}’. This field is missing from the returned result set from the data source.
The report references a field that is not included in the dataset’s result set, possibly due to changes in the query or stored procedure.
Add the missing field in the Dataset element. Example: Field name used in a report is missing Stored Procedure.
The {0} ‘{1}’ specifies a database collation name that is not valid: {3}.
The collation name provided in the dataset or data source is not recognized by the database engine.
Provide the valid database collation name.
The {0} ‘{1}’ is bound to a data source using the {2} data extension. The data extension returned an invalid database collation culture name: {3}.
The data extension (For example: SQL, Oracle) returned a collation culture name that is not valid or supported.
Provide the valid database collation culture name.
Error during processing of the CommandText expression of data set ‘{0}’.
The SQL query or expression used in the dataset’s CommandText is invalid or improperly formatted.
Provide the valid command text expression in the Dataset element of the report definition.
Query execution failed for data set ‘{0}‘.
The dataset query could not be executed, possibly due to permission issues, syntax errors, or connection problems.
Ensure that permission is granted to execute or retrieve the values of a data set.
The query returned no rows for the data set. The expression therefore evaluates to null.
The dataset query executed successfully but returned no data, causing expressions to evaluate to null.
Make sure that values used in expression are not null. Also ensure that rows of data are returned from the data set.
The expression used for the parameter ‘{1}’ in the data set ‘{3}’ refers to a field. Fields cannot be used in query parameter expressions.
A query parameter is incorrectly referencing a field from the dataset, which is not allowed.
Modify the value expression of a query parameter that references data set fields in a report.
One or more parameters required to run the shared data set have not been specified.
One or more parameters needed to execute the shared dataset were not provided.
Specify the value to the query parameter while executing the shared data set query.
Cannot create a data reader for dataset ‘{0}‘.
The system failed to initialize a data reader, possibly due to connection or configuration issues.
Cannot create query parameter for dataset ‘{0}‘.
The system encountered an error while creating a query parameter, possibly due to invalid definitions.
Cannot read a data field for the dataset {0}.
A field expected in the dataset could not be read, possibly due to schema mismatch or missing data.
The {0} ‘{1}’ contains a definition for the {2} ‘{3}’. The data extension returned an error during reading the field. {4}
The data extension encountered an error while reading a specific field.
The {0} ‘{1}’ contains a definition for the {2} ‘{3}({4})’. The data extension returned an error during reading the field property. {5}
The data extension failed to read a property (For Example: data type, size) of a field.
Cannot read the next data row for the dataset {0}.
An error occurred while attempting to read the next row of data from the dataset.
Cannot set the command text for dataset ‘{0}‘.
The system was unable to assign the SQL command text to the dataset.
Cannot set the command type for dataset ‘{0}‘.
The dataset command type (For Example: Text, StoredProcedure) could not be set.
Cannot set the query timeout for dataset ‘{0}‘.
The system failed to apply the specified timeout setting for the dataset query.
Cannot set the transaction for dataset ‘{0}‘.
The dataset could not be associated with a transaction, possibly due to configuration issues.
The {2} expression for the {0} ‘{1}’ has an inner aggregate in an outer aggregate that specifies a dataset scope. An aggregate that specifies a dataset scope cannot contain other aggregates.
An aggregate function that specifies a dataset scope contains another aggregate, which is not permitted.
Cannot read IsAggregationField for a data field for the dataset {0}.
The system failed to determine whether a field is used in an aggregation, possibly due to a corrupted or incomplete dataset definition.
The {0} ‘{1}’ contains a definition for the {2} ‘{3}’. The data type for this field is not supported.
A field in the dataset uses a data type that is not supported by the reporting engine or data extension.
The {2} expression for the {0} ‘{1}’ refers to a dataset. Datasets cannot be used in page headers or footers.
Expressions in page headers or footers cannot reference datasets because these sections are processed before data is retrieved.
The expression used for the parameter ‘{1}’ in the dataset ‘{3}’ refers to a dataset. Datasets cannot be used in query parameter expressions.
Query parameters cannot reference datasets, as datasets are not yet available when parameters are evaluated.
The expression used for the language of ‘{1}’ refers to a dataset. Datasets cannot be used in report language expressions.
The report language setting cannot be dynamically set using dataset fields or expressions.
A {2} expression used for the report parameter ‘{1}’ refers to a dataset. Datasets cannot be used in report parameter expressions.
Report parameters cannot reference datasets, as parameters are evaluated before datasets are processed.
The {2} expression for the {0} ‘{1}’ refers to the global variable RenderFormat, which is not valid for this type of report item expression.
The RenderFormat global variable is used in an expression where it is not supported, such as in certain report items.
The {2} expression for the {0} ‘{1}’ refers to more than one report item. An expression in a page header or footer can refer to only one report item.
Expressions in headers or footers can only reference a single report item to avoid ambiguity during rendering.
The expression that references an item ‘{0}’ does not exist in the Globals collection. Letters in the names of Globals collection items must use the correct case.
The expression references a non-existent or incorrectly cased item in the Globals collection.
Specify the valid element in the expression that refers to the Globals collection. The name must match an item that exists in the Globals collection.
The expression that references the parameter ‘{0}’ does not exist in the Parameters collection. Letters in the names of parameters must use the correct case.
The expression references a parameter that does not exist or is incorrectly cased in the Parameters collection.
Specify the valid parameter in the expression that exists in the parameter collection. The name must match a parameter that exists in the Parameters collection.
The expression that references the report item ‘{0}’ does not exist in the ReportItems collection. Expressions can only refer to other report items within the same grouping. Letters in the names of report items must use the correct case.
The expression references a report item that does not exist, is misspelled, or is outside the current grouping scope.
Specify the valid variables in the expression in the report definition. The names must match items, groups, or data sets in the report.
The {2} expression for the {0} ‘{1}’ refers to the global variable OverallPageNumber or OverallTotalPages. These global variables can be used only in the page header and page footer.
These global variables are only valid in page headers or footers and cannot be used in the report body.
Remove or modify the expression that contains the OverallPageNumber or OverallTotalPages global collection, which exists in the report body collection instead of in the header or footer sections.
The {2} expression for the {0} ‘{1}’ refers to the global variable OverallPageNumber or OverallTotalPages in an aggregate function that specifies a dataset scope. These global variables cannot be used with an aggregate function that has a dataset scope in a page header or page footer.
These global variables cannot be used within aggregate functions that specify a dataset scope in headers or footers.
Remove or modify the expression in the PageSection or PageHeaderFooter. It contains the OverallPageNumber or OverallTotalPages global collection as scope aggregate.
The {2} expression for the {0} ‘{1}’ refers to the global variable PageNumber or TotalPages. These global variables can be used only in the page header and page footer.
These global variables are only valid in page headers or footers and cannot be used in the report body.
Remove or modify the expression that contains the PageNumber or TotalPages global collection and exists in the report body collection instead of in the header or footer sections.
The {2} expression for the {0} ‘{1}’ refers to the global variable PageNumber or TotalPages within a data set aggregate. These global variables cannot be used in scoped aggregates within the page header and page footer.
These global variables cannot be used within dataset-scoped aggregates in headers or footers.
Remove or modify the expression that exists in the PageSection or PageHeaderFooter and contains the PageNumber or TotalPages global collection as scope aggregate.
A group expression for the {0} ‘{1}’ refers to a report item. Report items cannot be used in group expressions.
Group expressions must be based on fields or parameters, not report items.
Remove or modify the group expression (Group.GroupExpressions) that references the ReportItems global collection.
The {2} expression for the {0} ‘{1}’ contains a report item reference in an argument to a Lookup or LookupSet function. Report item references cannot be used for the destination or result Expression parameter of a lookup function.
Report items cannot be used as arguments in Lookup or LookupSet functions for destination or result expressions.
Remove or modify the Lookup or LookupSet expression that references the ReportItems global collection in the resultant argument.
The expression used for the parameter ‘{1}’ in the dataset ‘{3}’ refers to a report item. Report items cannot be used in query parameter expressions.
Query parameters cannot reference report items, as report items are not available at query execution time.
Remove or modify the QueryParameter value expression that references the ReportItems global collection.
The expression used for the language of ‘{1}’ refers to a report item. Report items cannot be used in report language expressions.
The report language setting cannot be dynamically set using report items.
Remove or modify the Report.Language value expression that references the ReportItems global collection.
A {2} expression used for the report parameter ‘{1}’ refers to a report item. Report items cannot be used in report parameter expressions.
Report parameters cannot reference report items, as parameters are evaluated before report items are processed.
Remove or modify the expression that references the ReportItems global collection within the ReportParameter element.
The {2} expression for the {0} ‘{1}’ references report item ‘{3}’ in an aggregate expression with a scope. A scope is not allowed on aggregates in the page header or footer which reference report items.
An aggregate expression in a page header or footer references a report item and includes a scope. This is not allowed because scoped aggregates cannot reference report items in these sections.
Remove or modify the expression in the PageSection or PageHeaderFooter that contains the ReportItems global collection as scope aggregate.
A sort expression for the {0} ‘{1}’ refers to a report item. Report items cannot be used in sort expressions.
Sort expressions must be based on fields or parameters. Report items cannot be used because they are not evaluated in the context required for sorting.
Remove or modify the expression that references the ReportItems global collection within the UserSort.SortExpression or SortExpression.Value element.
The {2} value expression used for the language of ‘{1}’ refers to a report item. Variable values cannot be used in report language expressions.
The language of a report cannot be dynamically set using report items, as these are not available at the time the language is evaluated.
Remove or modify the expression that refers to the report item via the ReportItems global collection within the Variable.Value element.
The {2} expression for the {0} ‘{1}’ refers to the report item ‘{3}’. Report item expressions can only refer to other report items within the same grouping scope or a containing grouping scope. Letters in the names of report items must use the correct case.
A report item is referenced in an expression, but it is not within the same or a containing grouping scope, which is required for valid references.
Use the existing report item in an expression that is referenced through the ReportItems global collection.
The {2} expression for the {0} ‘{1}’ refers to the report item ‘{3}’. Report item expressions in a Page Header or Footer can only refer to report items within the same ReportSection. Letters in the names of report items must use the correct case.
Expressions in page headers or footers can only reference report items that exist within the same ReportSection.
Remove or modify the expression in PageSection that refers to report items via the ReportItems global collection and does not exist in the current ReportSection. Provide the expression based on scope.
The expression used for the calculated field ‘{1}’ includes a variable reference. Variable values cannot be used in calculated field expressions.
Variables cannot be used in calculated field expressions because fields are evaluated in a different context than variables.
Remove or modify the field expression that refers to the Variables global collection. Field elements must not contain the Variables global collection in a report.
A sort expression for the {0} ‘{1}’ includes a variable reference. Variable values cannot be used in data row sort expressions.
Variables cannot be used in sort expressions for data regions like Tablix, Chart, or GaugePanel, as sorting is evaluated before variables are processed.
Remove or modify the sort expressions of respective report items that refer to the Variables global collection. GaugePanel, Chart, or Tablix sort expressions must not reference Variables collection in a report definition.
A group expression for the {0} ‘{1}’ includes a variable reference. Variable values cannot be used in group expressions.
Group expressions must be based on fields or parameters. Variables are not allowed because they are not evaluated in the grouping context.
Remove or modify the group expression that refers to the Variables global collection. Group.GroupExpressions must not contain the Variables global collection in a report.
The {2} expression for the {0} ‘{1}’ contains a variable reference in the Expression argument of a Previous function. Variable values cannot be used in the Expression parameter of the Previous function.
The Previous function cannot use variables in its expression argument, as it relies on row context which variables do not support.
Remove or modify the Previous aggregate expression that refers to the Variables global collection. The Previous function must not contain the Variables global collection in a report definition.
The expression used for the parameter ‘{1}’ in the dataset ‘{3}’ includes a variable reference. Variable values cannot be used in query parameter expressions.
Variables cannot be used in query parameter expressions because parameters are evaluated before variables are initialized.
Remove or modify the QueryParameter value expression that refers to the Variables global collection. The QueryParameter.Value element must not contain the Variables global collection in a report definition.
The expression used for the language of ‘{1}’ includes a variable reference. Variable values cannot be used in report language expressions.
This error indicates that a report language setting is incorrectly using a variable. Language expressions must be static and cannot depend on runtime variables.
Remove or modify the Report.Language expression that refers to the Variables global collection. The Report.Language element must not contain the Variables global collection in a report definition.
The {2} expression used for the report parameter ‘{1}’ includes a variable reference. Variable values cannot be used in report parameter expressions.
A report parameter expression incorrectly references a variable. Such expressions should not include variable dependencies.
Remove or modify the ReportParameter expression that refers to the Variables global collection. The ReportParameter element must not contain the Variables global collection in a report definition.
The {2} expression for the {0} ‘{1}’ refers to a field. Fields cannot be used in page headers or footers.
A field is referenced in a page header or footer, which is not allowed. Fields are evaluated in the context of data regions, not page headers or footers.
Remove or modify the field expression in PageSection or PageHeaderFooter that refers to Field via the Fields global collection.
The {2} expression for the {0} ‘{1}’ uses a scope parameter for an aggregate function. The scope parameter cannot be used in page headers or footers.
An aggregate function with a scope parameter is used in a header or footer, which is not permitted.
Remove or modify the expression in PageHeaderFooter that refers to the aggregate function as scope.
A {2} for the {0} ‘{1}’ uses the aggregate function RunningValue. RunningValue cannot be used in filters.
The RunningValue function is used in a filter, which is invalid. RunningValue is not supported in filter expressions.
Remove or modify the Filter.FilterExpression element value expression that refers to the RunningValue aggregate function. Filter expressions must not contain the RunningValue aggregate function.
A filter value in the filter for {0} ‘{1}’ specifies a data type that is not supported by the ‘{3}’ operator. Verify that the data type for each filter value is {4}.
A filter value uses an unsupported data type for a specified operator.
Specify the valid data type for the filter value expression. Supported data types are: Text, Integer, Date Time, Boolean, Float.
A {2} for the {0} ‘{1}’ includes an aggregate function. Aggregate functions cannot be used in dataset filters or data region filters.
An aggregate function is incorrectly used in a dataset or data region filter.
Remove or modify the Filter.FilterExpression element or Filter.FilterValues expression that refers to an aggregate function. Filter expressions must not contain aggregate functions. Note: Previous, RunningValue, and RowNumber aggregate functions will display respective error codes.
Failed to evaluate the {2} of the {0} ‘{1}
Evaluation of a component (For example: expression or filter) failed, but further details are unspecified.
Failed to evaluate the {2} of the {0} ‘{1}’. It references a dataset field which has an error: {3}
Evaluation failed due to an error in a referenced dataset field.
A {2} for the {0} ‘{1}’ refers to a report item. Report items cannot be used in filters.
A report item is referenced in a filter, which is not allowed.
Remove or modify the expression that refers to report items via the ReportItems global collection within the Filter.FilterExpression or Filter.FilterValues element.
A filter expression for the {0} ‘{1}’ includes a variable reference. Variable values cannot be used in {0} filter expressions.
This error occurs when a filter expression includes a variable reference from the Variables global collection, which is not allowed in report filter expressions.
Remove or modify the FilterValues or FilterExpression that refers to the Variables global collection. Gauge filters, Chart filters, Tablix filters or Dataset filters must not refer to the Variables global collection in a report definition.
The dependent assembly ‘{0}’ is missing to export the report into required format.
This error is raised when a required dependent assembly is missing for exporting the report into the specified format.
More than one report item in the report has the name ‘{1}’. Report item names must be unique within a report.
This error indicates that multiple report items in a report have the same name, which must be unique.
Provide a unique Name attribute for the report item in the ReportItems collection. Ensure that the Name properties of two or more report items are different within the same report.
The {0} ‘{1}’ is invalid. The value for the {2} property is missing.
This error appears when a report item is missing a required property value, such as DataSetName, for certain data region items when there are multiple data sets.
Specify the DataSetName property value for Gauge, Tablix, List, etc. Data region report items must contain a non-empty DataSetName element if report contains more than one data set in the Datasets collection.
More than one {2} in the {0} ‘{1}’ has the name ‘{3}’. {2} names must be unique within a {0}.
This error arises when multiple items within a container, like a report or group, share the same name which should be unique.
Provide a unique Name attribute for the report item in a report or group within scope. Ensure that the Name properties of two or more items are different in the report definition.
The value of the {2} property for the {0} ‘{1}’ is negative. Negative sizes are not allowed.
This occurs when a size-related property in a report item is specified as a negative value, which is not allowed.
Specify a non-negative value in the Size element in the report definition.
The {0} ‘{1}’ has ‘{3}’ as a toggle item. Toggle items must be text boxes that share the same scope as the hidden item or are in a scope that contains the hidden item, and cannot be contained within the current report item unless current grouping scope has a Parent.
It flags an incorrect toggle item setup where the toggle is not within the proper scope or does not follow the scope rules related to grouping.
Provide the Visibility ToggleItem element within the same scope in a report definition.
The {0} ‘{1}’ contains CustomProperties. The CustomProperty({3}) is missing a {2} element, which is mandatory.
This error is reported when a required element for a custom property is missing, making it incomplete.
Specify a name attribute of CustomProperty. Custom property names are mandatory and the attribute should not be empty.
The {0} ‘{1}’ is in the page header or footer and has bookmark property. Bookmarks in page headers and page footers are not supported by all renderers.
This indicates unsupported bookmarks used in page headers or footers that certain renderers do not handle.
Remove the Bookmark property specified in a PageSection or PageHeaderFooter element.
The object ‘{0}’ does not exist in the collection.
This error is triggered when an object does not exist in the specified collection.
The {0} ‘{1}’ is in the page header or footer and has a {2} element. {2} cannot be used by text boxes in the page header or footer.
This error happens when a text box in a header or footer incorrectly uses an element that is not supported in those sections.
Specify the UserSort Textbox element within the scope.
The {0} ‘{1}’ has an Action that has more than one of the following: Hyperlink, BookmarkLink or Drillthrough. Action must have exactly one of these elements.
This is triggered when an action in a report item is configured with multiple elements like Hyperlink, BookmarkLink, or Drillthrough rather than just one.
Remove the multiple action info specified in an Action element. The ActionInfo of a Report Item element must contain one of the following: Hyperlink, Bookmark, or Drillthrough.
The {0} ‘{1}’ has multiple actions. Action label property is required.
This error indicates that an action label property is missing for report items that have multiple actions.
Remove the multiple action or specify the label for each action and provide valid action label.
The {2} expression for the {0} ‘{1}’ includes the function CountRows. CountRows cannot be used in page headers or footers.
This error is raised by using the CountRows function in page headers or footers, where it is not permitted.
The {2} for the {0} ‘{1}’ is not valid. A {2} can not be an empty string or just white space.
This arises when a property is an empty string or just whitespace, which is not valid for certain report elements.
Provide a value for the ReportName property of a Subreport or Drillthrough element. It should not be empty.
The {2} for the {0} ‘{1}’ is not valid. Item names cannot contain the following reserved characters {3}.
This warns against invalid characters in report item names which should not include reserved characters.
Remove the invalid or special character(s) in a name of a report.
The {2} for the {0} ‘{1}’ is not valid.
This error signifies that a report item contains invalid or special characters that are not supported in its name.
Remove the invalid or special character(s) for URI in name of report.
The value ‘{3}’ of the {2} property of the {0} ‘{1}’ has an invalid schema. URLs in reports may only use http://, https://, ftp://, mailto: or news:
This occurs when a URL in a report uses a schema that is not among the supported ones like http, https, ftp, etc.
Specify the valid URL. URL must begin with http://, https://, ftp://,mailto:, or news: and is referenced by the following elements, 1. Action.Hyperlink, 2. Image value of Background, Cap, Frame, Gauge, Image, MapMarker, Pointer, State, TopImage properties.
The {0} ‘{1}’ has the URL “{3}” as one of its properties. URLs in reports must begin with one of the following prefixes: {4}.
This error occurs when a URL specified in a report item (such as an image, hyperlink, or action) does not start with a valid or recognized URI scheme.
Specify the valid URL in an Image.Value element. URL must begin with http://, https://, ftp://,mailto:, or news:.
The URL {0} has an invalid schema. URLs in reports may only use http://, https://, ftp://, file:, mailto: or news:
This error occurs when a URL used in a report item (such as an image, hyperlink, or action) begins with a schema (protocol) that is not supported by BoldReports
Specify the valid and supported URL in the report. URL must begin with http://, https://, ftp://,mailto:, or news:.
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 value.
This error indicates that the endpoint calculations for line items result in a negative value, which is not permissible.
Specify non-negative values for the Left and Width elements of a line report item in a report definition.
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 value.
This signals a negative endpoint value for top plus height calculations of a line item.
Specify non-negative values for the Top and Height elements of a line report item in a report definition.
The {0} ‘{1}’ has a Toggle. Toggle is not allowed in page headers or footers.
This error arises when a toggle function is improperly placed in page headers or footers.
The SortItemId is invalid. It must be a positive integer and has to be existing.
This points to an invalid SortItemId, which must be existing and a positive integer.
The {0} ‘{1}’ has an invalid {2} “{3}”. The scope must be the current scope, a peer scope, which is a data region, or an ancestor scope. If the current scope and target scope are groupings, then both scopes must be along the same axis.
Indicates an invalid scope for a report element, requiring it be a current, peer, or ancestor scope.
The {0} ‘{1}’ contains an invalid {4}. The {2} element is not allowed if {3} is omitted.
Flags the inclusion of an element when a required accompanying element is omitted.
The {0} ‘{1}’ has an invalid {2} ‘{3}‘. The scope cannot be a grouping that has a domain scope defined.
A component references a scope that is defined across multiple domains or contexts, which is not allowed for certain operations.
The {0} ‘{1}’ has an invalid {2} “{3}”. The scope cannot be a detail grouping scope. To use a detail grouping scope, do not specify a {2}.
A detail-level scope (that is one without grouping) is being used where a named scope is required.
The {2} expression for the {0} ‘{1}’ is invalid (it is an empty string).
This specifies that an expression for a report component is not valid because it results in an empty string.
The {2} for the {0} ‘{1}’ is invalid. Details: {3}
An expression is invalid due to a specific issue, which is detailed in the accompanying message.
The {2} expression for the {0} ‘{1}’ specifies a scope that is not valid for a nested aggregate. The scope must be the same name of the scope specified by the outer aggregate or the name of a group or data region that is contained in the scope specified by the outer aggregate.
Highlights that a nested aggregate expression has an incorrect scope that does not match the requirements for proper scoping.
Specify the valid scope in an expression parameter of the nested aggregate function.
The {2} expression for the {0} ‘{1}’ has a nested aggregate that specifies a dataset scope. Inner aggregates cannot specify a dataset scope.
A nested operation references a dataset-level scope, which is not allowed.
Remove the data set name specified in the expression parameter of the nested aggregate function.
The {2} expression for the {0} ‘{1}’ has an inner aggregate that specifies the recursive flag. Nested aggregates cannot specify the recursive flag.
A nested operation includes a recursive flag, which is not supported in this context.
Remove the recursive parameter specified in the expression argument of the nested aggregate function.
The {2} expression for the {0} ‘{1}’ uses an aggregate expression with the recursive/simple flag. The recursive/simple flag is not allowed for First, Last, Previous, RowNumber, RunningValue and Aggregate.
Highlights inaccuracies with the use of specific function flags within aggregate expressions.
Remove the First, Last, Previous, RowNumber, RunningValue, or Aggregate functions specified in the recursive function.
The {2} expression for the {0} ‘{1}’ includes an aggregate function in the argument to another aggregate function. Nested aggregates are not allowed inside filter expressions.
This error highlights an issue with a nested aggregate present within a filter expression, which is not allowed.
Remove the nested aggregate function specified in the Filter expression value.
The {2} value expression for the {0} ‘{1}’ uses an aggregate function in the argument to another aggregate function. Nested aggregates are not allowed inside group variable expressions.
Points out the invalid use of a nested aggregate function inside a group variable expression.
Remove the nested aggregate function specified in the Group.Variables expression value.
The {2} expression for the {0} ‘{1}’ uses an aggregate function in the argument to another aggregate function. Nested aggregates are not allowed in the page header or footer.
Occurs when a nested aggregate is incorrectly used in a header or footer expression.
Remove the nested aggregate function specified in the report page header or page footer expression parameter.
The {2} expression for the {0} ‘{1}’ contains a nested aggregate that does not specify a scope. In a tablix cell that belongs to both row and column groups, or on a data point that belongs to both series and category groups, when the outer aggregate specifies a group scope, nested aggregates must specify a scope.
Indicates that a nested aggregate lacks the required scope specification in complex report items like tablix cells.
Specify the scope parameter for the aggregate function. Aggregate functions in an expression must contain a scope parameter.
The {2} expression for the {0} ‘{1}’ uses both row and column scopes or scopes from two different data axes in the same aggregate expression. All nested aggregate functions must specify a named scope along the same data axis as the scope of the containing aggregate.
Flags improper utilization of mixed or incorrect scope in nested aggregate functions.
Specify the unique scope for the nested aggregate expression. The scope of an aggregate and axis, row group, or column group must be same.
The {2} expression for the {0} ‘{1}’ uses an outer aggregate that specifies a Lookup expression that uses an aggregate. Nested aggregates cannot be specified in a Lookup expression.
This error warns against employing nested aggregates within Lookup expressions, which is not supported.
Remove the nested aggregate function in a Lookup, LookupSet, MultiLookup source parameter expression, in which a miscellaneous function exists inside the aggregate function.
The {2} expression for the {0} ‘{1}’ uses the Aggregate Function in an argument to another aggregate function. The Aggregate Function cannot be specified as a parameter in an aggregate function.
The expression for the specified item uses an aggregate function within another aggregate function. This nesting is not allowed.
Remove the nested aggregate function in an expression parameter of another aggregate function.
The {2} expression for the {0} ‘{1}’ contains a Lookup or LookupSet function in the argument to another Lookup or LookupSet function. Lookup functions cannot be nested inside other lookup functions.
The expression for the specified item contains a Lookup or LookupSet function within another Lookup or LookupSet function. Nesting lookup functions is not allowed.
Remove the multiple specified look-up functions. Look-up functions should not contain another look-up function (Lookup, LookupSet, MultiLookup).
The item in the Lookups collection was not found. References to the Lookups collection in an expression are not supported.
An item in the Lookups collection was not found. References to the Lookups collection in expressions are not supported.
A {2} for the {0} ‘{1}’ uses the aggregate function Previous. Previous cannot be used in filters.
The expression for the specified filter uses the Previous aggregate function, which is not allowed in filters.
Remove or modify the Filter.FilterExpression element value expression that refers to the Previous aggregate function. Filter expressions must not contain the Previous aggregate function.
A group expression for the {0} ‘{1}’ includes the aggregate function Previous. Previous cannot be used in group expressions.
The group expression for the specified item includes the Previous aggregate function, which is not allowed in group expressions.
Remove or modify the Group.GroupExpressions that refers to the Previous aggregate function. Group expressions must not contain the Previous aggregate function.
The {2} expression for the {0} ‘{1}’ includes the aggregate function Previous. Previous cannot be used in page headers or footers.
The expression for the specified item includes the Previous aggregate function, which is not allowed in page headers or footers.
Remove or modify the Previous aggregate expression in PageHeaderFooter. Reports’ page header and footer must not contain the Previous function.
The expression used for the parameter ‘{1}’ in the dataset ‘{3}’ uses the aggregate function Previous. Previous cannot be used in query parameter expressions.
The expression for the specified query parameter uses the Previous aggregate function, which is not allowed in query parameter expressions.
Remove or modify the QueryParameter value expression that refers to the Previous aggregate function. Query parameter expressions must not contain the Previous function.
The expression used for the language of ‘{1}’ uses the aggregate function Previous. Previous cannot be used in report language expressions.
The expression for the report language uses the Previous aggregate function, which is not allowed in report language expressions.
Remove or modify the Report.Language value expression that refers to the Previous aggregate function. Report language expressions must not contain the Previous function.
A {2} expression used for the report parameter ‘{1}’ uses the aggregate function Previous. Previous cannot be used in report parameter expressions.
The expression for the specified report parameter uses the Previous aggregate function, which is not allowed in report parameter expressions.
Remove or modify the expression that refers to the Previous aggregate function within the ReportParameter element. Previous functions cannot be used in report parameter expressions.
A sort expression for the {0} ‘{1}’ uses the aggregate function Previous. Previous cannot be used in sort expressions.
The sort expression for the specified item uses the Previous aggregate function, which is not allowed in sort expressions.
Remove or modify the expression that refers to the Previous aggregate function within the UserSort.SortExpression or SortExpression.Value element.
The {2} value expression for the {0} ‘{1}’ uses the aggregate function Previous. Previous cannot be used in variable value expressions.
The value expression for the specified variable uses the Previous aggregate function, which is not allowed in variable value expressions.
Remove or modify the expression that refers to the Previous aggregate function within the Variable.Value element.
The {2} expression for the {0} ‘{1}’ uses a Previous function in an outer aggregate. Previous functions cannot be specified as nested aggregates.
The expression for the specified item uses a Previous function within another aggregate function, which is not allowed.
Remove or modify the expression that contains a nested Previous aggregate function.
The {2} expression for the {0} ‘{1}’ contains the Previous function in the Expression argument of a Previous function. The Previous function cannot be used in the Expression parameter of the Previous function.
The expression for the specified item contains the Previous function within the argument of another Previous function, which is not allowed.
Remove or modify the expression that contains multiple Previous functions in the expression parameter of another Previous aggregate function.
A {2} for the {0} ‘{1}’ uses the function RowNumber. RowNumber cannot be used in filters.
The expression for the specified filter uses the RowNumber function, which is not allowed in filters.
Remove or modify the Filter.FilterExpression element value expression that refers to the RowNumber aggregate function. Filter expressions must not contain the RowNumber aggregate function.
The {2} expression for the {0} ‘{1}’ contains the RowNumber function in an argument to a Lookup or LookupSet function. The RowNumber function cannot be used for the destination or result Expression parameter of a lookup function.
The expression for the specified item contains the RowNumber function within a Lookup or LookupSet function, which is not allowed.
Remove or modify the destination or result parameter of look-up functions that refer to the RowNumber aggregate function. Look-up functions must not contain the RowNumber aggregate function.
The {2} expression for the {0} ‘{1}’ uses the function RowNumber. RowNumber cannot be used in page headers or footers.
The expression for the specified item uses the RowNumber function, which is not allowed in page headers or footers.
Remove or modify the RowNumber aggregate expression in PageHeaderFooter. Report page header or footer must not contain RowNumber function.
The {2} expression for the {0} ‘{1}’ contains the RowNumber function in the Expression argument of a Previous function. The RowNumber function cannot be used in the Expression parameter of the Previous function.
The expression for the specified item contains the RowNumber function within the argument of a Previous function, which is not allowed.
Remove or modify the expression parameter of the Previous aggregate function. Previous aggregate functions must not contain the RowNumber function.
The expression used for the parameter ‘{1}’ in the dataset ‘{3}’ includes the function RowNumber. RowNumber cannot be used in query parameter expressions.
The expression for the specified query parameter uses the RowNumber function, which is not allowed in query parameter expressions.
Remove or modify the QueryParameter value expression that refers to the RowNumber aggregate function. Query parameter expressions must not contain RowNumber functions.
The expression used for the language of ‘{1}’ uses the function RowNumber. RowNumber cannot be used in report language expressions.
The expression for the report language uses the RowNumber function, which is not allowed in report language expressions.
Remove or modify the Report.Language value expression that refers to the RowNumber aggregate function. Report language expressions must not contain RowNumber functions.
A report parameter expression for the {0} ‘{1}’ uses the function RowNumber. RowNumber cannot be used in report parameter expressions.
The expression for the specified report parameter uses the RowNumber function, which is not allowed in report parameter expressions.
Remove or modify the expression that refers to the RowNumber aggregate function within the ReportParameter element. RowNumber functions cannot be used in report parameter expressions.
A sort expression for the {0} ‘{1}’ uses the function RowNumber. RowNumber cannot be used in sort expressions.
The sort expression for the specified item uses the RowNumber function, which is not allowed in sort expressions.
Remove or modify the expression that refers to the RowNumber aggregate function within the UserSort.SortExpression or SortExpression.Value element.
The {2} value expression for the {0} ‘{1}’ uses the function RowNumber. RowNumber cannot be used in variable value expressions.
The value expression for the specified item uses the RowNumber function, which is not allowed in variable value expressions.
Remove or modify the expression that refers to the RowNumber aggregate function within the Variable.Value element.
The {2} expression for the {0} ‘{1}’ uses a RunningValue function in an outer aggregateRunningValue functions cannot be specified as nested aggregates.
The expression for the specified item uses a RunningValue function within another aggregate function. RunningValue functions cannot be nested within other aggregates.
Remove or modify the expression that contains a nested RunningValue aggregate function.
A group expression for the {0} ‘{1}’ includes the aggregate function RunningValue. RunningValue cannot be used in group expressions.
The group expression for the specified item includes the RunningValue function, which is not allowed in group expressions.
Remove or modify the Group.GroupExpressions that refers to the RunningValue aggregate function. Group expressions must not contain the RunningValue aggregate function.
The {2} expression for the {0} ‘{1}’ includes the aggregate function RunningValue. RunningValue cannot be used in page headers or footers.
The expression for the specified item includes the RunningValue function, which is not allowed in page headers or footers.
Remove or modify the RunningValue aggregate expression in PageHeaderFooter. Report page headers and footers must not contain the RunningValue function.
The {2} expression for the {0} ‘{1}’ contains the RunningValue function in the Expression argument of a Previous function. The RunningValue function cannot be used in the Expression parameter of the Previous function.
The expression for the specified item contains the RunningValue function within the argument of a Previous function. The RunningValue function cannot be used in the Expression parameter of the Previous function.
Remove or modify the expression parameter of the Previous aggregate function. The Previous aggregate function must not contain the RunningValue function.
The expression used for the parameter ‘{1}’ in the dataset ‘{3}’ uses the aggregate function RunningValue. RunningValue cannot be used in query parameter expressions.
The expression for the specified query parameter uses the RunningValue function, which is not allowed in query parameter expressions.
Remove or modify the QueryParameter value expression that refers to the RunningValue aggregate function. Query parameter expressions must not contain the RunningValue function.
The expression used for the language of ‘{1}’ uses the aggregate function RunningValue. RunningValue cannot be used in report language expressions.
The expression for the report language uses the RunningValue function, which is not allowed in report language expressions.
Remove or modify the Report.Language value expression that refers to the RunningValue aggregate function. Report language expressions must not contain the RunningValue function.
A {2} expression used for the report parameter ‘{1}’ uses the aggregate function RunningValue. RunningValue cannot be used in report parameter expressions.
The expression for the specified report parameter uses the RunningValue function, which is not allowed in report parameter expressions.
Remove or modify the expression that refers to the RunningValue aggregate function within the ReportParameter element. RunningValue functions cannot be used in report parameter expressions.
A sort expression for the {0} ‘{1}’ uses the aggregate function RunningValue. RunningValue cannot be used in sort expressions.
The sort expression for the specified item uses the RunningValue function, which is not allowed in sort expressions.
Remove or modify the expression that refers to the RunningValue aggregate function within the UserSort.SortExpression or SortExpression.Value element.
The {2} value expression for the {0} ‘{1}’ uses the aggregate function RunningValue. RunningValue cannot be used in variable value expressions.
The value expression for the specified item uses the RunningValue function, which is not allowed in variable value expressions.
Remove or modify the expression that refers to the RunningValue aggregate function within the Variable.Value element.
The {0} ‘{1}’ contains at least one PlotType setting, which is different from the default setting ‘Auto’. The PlotType will be ignored, because the chart subtype is different from HybridLine.
The specified item contains at least one PlotType setting that is different from the default setting ‘Auto’. The PlotType will be ignored because the chart subtype is different from HybridLine.
Specify the chart subtype as Line to plot the series as a line. The default value is Auto.
More than one {2} in the {0} ‘{1}’ has the name ‘{3}’. {2} names must be unique within a chart area.
More than one specified element in the specified item has the same name. Element names must be unique within a chart area.
Provide unique Name attributes for ChartAxis elements. Ensure that the Name properties of two or more chart axes are different within the same chart area.
More than one chart column in the chart ‘{1}’ has the name ‘{3}’. Chart column names must be unique within a chart.
More than one chart column in the specified chart has the same name. Chart column names must be unique within a chart.
Provide unique Name attributes for chart columns. Ensure that the Name properties of two or more columns are different within the same Chart element.
More than one {2} in the {0} ‘{1}’ has the name ‘{3}’. {2} names must be unique within a derived series.
More than one specified element in the specified item has the same name. Element names must be unique within a derived series.
Provide a unique Name attribute for the ChartFormulaParameters.ChartFormulaParameter element. Ensure that the Name properties of two or more formula parameters are different within the same ChartFormulaParameters collection.
More than one {2} in the {0} ‘{1}’ has the name ‘{3}’. {2} names must be unique within a legend custom item.
More than one specified element in the specified item has the same name. Element names must be unique within a legend custom item.
Provide a unique Name attribute for the ChartLegendCustomItemCell element. Ensure that the Name properties of two or more legend custom cell elements are different within the same ChartLegendCustomItemCells collection.
More than one {2} in the {0} ‘{1}’ has the name ‘{3}’. {2} names must be unique within a legend.
More than one specified element in the specified item has the same name. Element names must be unique within a legend.
Provide a unique Name attribute for the ChartLegendCustomItem element. Ensure that the Name properties of two or more legend custom elements are different within the same ChartLegendCustomItems collection.
An error has occurred during rendering of chart {0}.
An error occurred during the rendering of the specified chart.
The definition of the chart {0} is not valid.
The definition of the specified chart is not valid.
Provide the valid report definition of the Chart report item element based on respective schema versions.
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 specified item contains an invalid name. The name must be greater than 0 and less than or equal to 256 characters.
Provide a valid chart axis name. The name should not be empty or longer than 256 characters.
The {0} ‘{1}’ contains an invalid {2} Name, ‘{3}‘. The name must be CLS-Compliant.
The specified item contains an invalid name. The name must be CLS-compliant.
Specify the chart axis name with the valid format. The name should not contain spaces and it must begin with a letter followed by letters, numbers, or the underscore character.
A chart column in the chart ‘{1}’ has the name ‘{3}’. Chart column names must be greater than 0 and less than or equal to {4} characters.
A chart column in the specified chart has a name that must be greater than 0 and less than or equal to 256 characters.
Provide a valid chart column name. The name should not be empty or longer than 256 characters.
A chart column in the chart ‘{1}’ has the name ‘{3}’. Chart column names must be CLS-compliant identifiers.
A chart column in the specified chart has a name that must be CLS-compliant.
Specify the chart column name with a valid format. The name should not contain spaces and it must begin with a letter followed by letters, numbers, or the underscore character.
The DataPoints in the {0} ‘{1}’ has an invalid set of {2} items. {2} names must be unique within the {2} collection for the DataPoint, and for this Chart’s type, all of the following must be specified in the DataPoints {2} collection: {3}.
The DataPoints in the specified item have an invalid set of names. Names must be unique within the collection for the DataPoint, and for this chart type, all specified items must be included in the DataPoints collection.
Provide a unique Name attribute for the DataPoint element in the ChartDataPoints collection. Ensure that the Name properties of two or more DataPoint elements ar different within the same DataPoints collection.
The {0} ‘{1}’ has a {2} at index {4} with an invalid {3} at index {5}. The name of the {3} must be a Constant.
The specified item has an element at a certain index with an invalid name. The name must be a constant.
The DataPoint {2} in the {0} ‘{1}’ has the name “{3}”. DataValue names cannot be null and must be unique within the DataValues collection for the DataPoint.
The DataPoint in the specified item has a name that cannot be null and must be unique within the DataValues collection for the DataPoint.
Provide a unique Name attribute for the ChartDataValue element. Ensure that the Name properties of two or more ChartDataValue elements are different within the same ChartDataValues collection.
The {0} ‘{1}’ has both StaticCategories and StaticSeries. A pie or doughnut chart can have StaticCategories or StaticSeries, but not both.
The specified item has both StaticCategories and StaticSeries. A pie or doughnut chart can have StaticCategories or StaticSeries, but not both.
Remove or modify the Series or Category elements of pie or doughnut-type charts. Pie and Doughnut charts must not contain both SeriesGrouping.StaticSeries and CategoryGrouping.StaticCategories
The {0} ‘{1}’ has an invalid {2} level at level {3}. Levels within a {2} can only have one ChartMember, unless each member at that level is static (that is no Group specified), and static ChartMembers cannot have child ChartMembers.
The specified item has an invalid level. Levels within a specified element can only have one ChartMember, unless each member at that level is static (that is no Group specified), and static ChartMembers cannot have child ChartMembers.
Remove or modify the Series or Category ChartMember element. Static chart members must not contain child members.
The {0} ‘{1}’ has an invalid {2}. The {2} has an invalid {3}, ‘{4}‘. Child {2} elements of Static {2} elements must be Dynamic {3} (that is It must have a {3}, which must contain {5}).
The specified item has an invalid element. The element has an invalid child element. Child elements of static 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 specified item has an invalid element. Non-static elements must contain at least one group expression.
Specify at least one group expression for the nonstatic ChartMember element.
The {0} ‘{1}’ has a SeriesGrouping with both or neither of the following: DynamicSeries and StaticSeries. A SeriesGrouping must have exactly one of these elements.
The specified item has a SeriesGrouping with both or neither of the following: DynamicSeries and StaticSeries. A SeriesGrouping must have exactly one of these elements.
Remove or modify the SeriesGrouping element that contains both StaticSeries and DynamicSeries.
The ChartDerivedSeries in the {0} ‘{1}’ has an invalid {2} ‘{3}‘.
The ChartDerivedSeries in the specified item has an invalid element.
The sorting applied to the {2} of the {0} ‘{1}’ is different from the grouping expression. Since the chart type is a line chart, depending on the data values this might result in a scattered line chart.
The sorting applied to the specified element is different from the grouping expression. Since the chart type is a line chart, this might result in a scattered line chart depending on the data values.
The scalar values property for the {2} of the {0} ‘{1}’ is set to true. Scalar cannot be true if the dynamic grouping has more than one group expression.
The scalar values property for the specified element is set to true. Scalar cannot be true if the dynamic grouping has more than one group expression.
The scalar values property for the {2} of the {0} ‘{1}’ is set to true. Scalar cannot be true if the axis has more than one grouping.
The scalar values property for the specified element is set to true. Scalar cannot be true if the axis has more than one grouping.
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.
The specified group is marked to create a page break for each group. Page breaks are not supported for the specified element in charts.
The DataPoint {0} ‘{1}’ references an {2} Name, {3}, for a non-Value Axis for this chart.
The DataPoint references an invalid name for a non-Value Axis for this chart.
The scalar values property for the {2} of the {0} ‘{1}’ is set to true. This is not supported for a static grouping.
The scalar values property for the specified element is set to true. This is not supported for a static grouping.
The {0} ‘{1}’ has a ChartData element that contains a collection of {3} DataPoint element(s), which is different from the number of expected data points ({4}). The expected number of data points in the definition is (Max(number of static categories, 1) * Max (number of static series, 1)).
The specified item has a ChartData element that contains a collection of DataPoint elements, which is different from the number of expected data points. The expected number of data points is the maximum of the number of static categories and static series.
The {0} ‘{1}’ contains a different number of DataPoints per ChartSeries element than the number of StaticCategory elements. If the {0} contains no StaticCategory, it must contain one DataPoint per ChartSeries.
The specified item contains a different number of DataPoints per ChartSeries element than the number of StaticCategory elements. If there are no StaticCategory elements, there must be one DataPoint per ChartSeries.
The {0} ‘{1}’ contains a different number of ChartSeries elements than the number of StaticSeries elements. If the {0} contains no StaticSeries, it must contain one ChartSeries.
The specified item contains a different number of ChartSeries elements than the number of StaticSeries elements. If there are no StaticSeries elements, there must be one ChartSeries.
The {0} ‘{1}’ has an invalid subtype. The subtype ‘{4}’ is not allowed for a chart of type ‘{3}’.
The specified item has an invalid subtype. The specified subtype is not allowed for the chart type.
The {0} ‘{1}’ has multiple {2} elements. A chart may have at most one {2} element.
The specified item has multiple elements. A chart may have at most one of the specified element.
The sort expressions for the {2} ‘{3}’ of the {0} ‘{1}’ are different from the group expressions. In area charts with scalar X axis, the category sort expressions must be identical to the category group expressions.
The sort expressions for the specified element are different from the group expressions. In area charts with a scalar X axis, the category sort expressions must be identical to the category group expressions.
The DataPoint in {0} ‘{1}’ references a {2} Name, ‘{3}’, that does not exist in this chart.
The DataPoint in the specified item references a name that does not exist in this chart.
The {0} ‘{1}’ uses a chart type that requires {4} DataValues for every DataPoint specified. At least one DataPoint has an invalid number of DataValues ({3}).
The specified item uses a chart type that requires a specific number of DataValues for every DataPoint. At least one DataPoint has an invalid number of DataValues.
The {2} element for the {0} ‘{1}’ can not contain a CustomReportItem element.
The specified element cannot contain a CustomReportItem element.
AltCustomReportItem must be specified once in a CustomReportItem, which will render if CustomReportItem is not supported by the renderer. AltCustomReportItem must be a single ReportItem element, not a CustomReportItem.
The ‘{2}’ extension failed to load the extension assembly. The {0} ‘{1}’ will render the AltReportItem or preserve the white space if no AltReportItem is explicitly defined.
The specified extension failed to load the extension assembly. The item will render the AltReportItem or preserve the white space if no AltReportItem is explicitly defined.
The ‘{2}’ extension is not present in the configuration file. Therefore, the {0} ‘{1}’ shows empty space.
The specified extension is not present in the configuration file. Therefore, the item shows empty space.
The {0} ‘{1}’ is in the page header or footer. Custom reportitems cannot be used in page headers or footers.
The specified item is in the page header or footer. Custom report items cannot be used in page headers or footers.
The {0} ‘{1}’ contains a {2} grouping level with both of the following: static and non-static groups. Multiple groups on the same level have to be all static.
The specified item contains a grouping level with both static and non-static groups. Multiple groups on the same level must be all static.
The {0} ‘{1}’ has multiple static {2} groups at different grouping levels. A {0} may have at most one level of static groups.
The specified item has multiple static groups at different grouping levels. A report item may have at most one level of static groups.
An error has occurred during processing of the CustomReportItem ‘{0}’ with the ‘{1}’ extension.
An error occurred during processing of the CustomReportItem with the specified extension.
The {0} ‘{1}’ has multiple instances at runtime. All generated RenderItems must be not null. The {2} extension returned an empty RenderItem.
The specified item has multiple instances at runtime. All generated RenderItems must be not null. The extension returned an empty RenderItem.
The CustomReportItem ‘{3}’ has multiple instances at runtime. All RenderItem instances of a particular CustomReportItem must have identical report item definition names. The expected name is ‘{4}’. The {2} extension returned a RenderItem instance with a different definition name ‘{1}’.
The CustomReportItem has multiple instances at runtime. All RenderItem instances of a particular CustomReportItem must have identical report item definition names. The extension returned a RenderItem instance with a different definition name.
The {2} extension for CustomReportItem ‘{3}’ created an {0} ‘{1}’ with a shared and a non-shared {4} style property. Style properties can be either shared or non-shared, but not both.
The extension for CustomReportItem created an item with both shared and non-shared style properties. Style properties can be either shared or non-shared, but not both.
The CustomReportItem ‘{3}’ has multiple instances at runtime. All RenderItem instances of a particular CustomReportItem must have identical report item types. The expected type is {4}. The {2} extension returned a RenderItem instance of type {0}.
The CustomReportItem has multiple instances at runtime. All RenderItem instances of a particular CustomReportItem must have identical report item types. The extension returned a RenderItem instance of a different type.
The CustomReportItem ‘{3}’ has multiple instances at runtime. The {2} extension created an invalid RenderItem instance for {0} ‘{1}’. All style properties must be defined for the first instance and can be omitted for additional instances. The {4} style property is not defined on the first instance.
The CustomReportItem has multiple instances at runtime. The extension created an invalid RenderItem instance. All style properties must be defined for the first instance and can be omitted for additional instances. The specified style property is not defined on the first instance.
The CustomReportItem ‘{3}’ has multiple instances at runtime. The {2} extension created an invalid RenderItem instance for {0} ‘{1}’. The {4} style cannot be shared for the first instance and non-shared for other instances.
The CustomReportItem has multiple instances at runtime. The extension created an invalid RenderItem instance. The specified style cannot be shared for the first instance and non-shared for other instances.
The ‘{2}’ extension returned an empty RenderItem for {0} ‘{1}’. RenderItems must be not null.
The extension returned an empty RenderItem for the specified item. RenderItems must be not null.
The CustomReportItem ‘{3}’ has multiple instances at runtime. All RenderItem instances of a CustomReportItem must have the same number of {4}. The expected number of {4} is {5}. The {2} extension returned a RenderItem instance with {6} {4}.
The CustomReportItem has multiple instances at runtime. All RenderItem instances of a CustomReportItem must have the same number of specified elements. The extension returned a RenderItem instance with a different number of elements.
The {0} ‘{1}’ has at least one static {2} group with a subgrouping. A static group cannot have subgroupings.
The specified item has at least one static group with a subgrouping. A static group cannot have subgroupings.
The {0} ‘{1}’ contains a {2} group with subtotal = true. Automatic subtotal calculation is not supported.
The specified item contains a group with subtotal set to true. Automatic subtotal calculation is not supported.
The {2} element for the {0} ‘{1}’ can only contain exactly one report item.
The specified element can only contain exactly one report item. Solution: Ensure that the element contains only one report item.
The expression used for the calculated field ‘{1}’ includes an aggregate, RowNumber, RunningValue, Previous or lookup function. Aggregate, RowNumber, RunningValue, Previous and lookup functions cannot be used in calculated field expressions.
The expression used for the calculated field includes an aggregate, RowNumber, RunningValue, Previous, or lookup function. These functions cannot be used in calculated field expressions.
Remove or modify the expression of Field element that refers to any of the aggregate functions or Lookup, LookupSet, or MultiLookup functions. Any element inside Field collection must not contain aggregate functions.
A sort expression for the {0} ‘{1}’ includes an aggregate function. Aggregate functions cannot be used in data row sort expressions.
A sort expression for the specified item includes an aggregate function. Aggregate functions cannot be used in data row sort expressions.
Remove or modify the expression Chart.SortExpressions, GaugePanel.SortExpressions, or Tablix.SortExpressions that refers to an aggregate function. SortExpressions must not contain aggregate functions.
A group expression for the {0} ‘{1}’ includes an aggregate function. Aggregate functions cannot be used in group expressions.
A group expression for the specified item includes an aggregate function. Aggregate functions cannot be used in group expressions.
Remove or modify the expression Group.GroupExpressions element that refers to any aggregate function. GroupExpressions must not contain aggregate functions.
The {2} expression for the {0} ‘{1}’ contains an aggregate function in an argument to a Lookup or LookupSet function. Aggregate functions cannot be used for the destination or result Expression parameter of a lookup function.
The expression for the specified item contains an aggregate function in an argument to a Lookup or LookupSet function. Aggregate functions cannot be used for the destination or result expression parameter of a lookup function.
Remove or modify the lookup function result expression that refers to an aggregate function. Lookup function result parameter expressions must not contain aggregate functions.
The {2} expression for the {0} ‘{1}’ contains the Aggregate function in the Expression argument of a Previous function. The Aggregate function cannot be used in the Expression parameter of the Previous function.
The expression for the specified item contains the Aggregate function in the Expression argument of a Previous function. The Aggregate function cannot be used in the Expression parameter of the Previous function.
Remove or modify the Previous aggregate expression that refers to an aggregate expression. Previous functions must not contain aggregate functions.
The expression used for the parameter ‘{1}’ in the dataset ‘{3}’ includes an aggregate or lookup function. Aggregate and lookup functions cannot be used in query parameter expressions.
The expression used for the parameter in the dataset includes an aggregate or lookup function. Aggregate and lookup functions cannot be used in query parameter expressions.
Remove or modify the QueryParameter value expression that refers to the aggregate function. Query parameter expressions must not contain aggregate functions or look-up functions.
The expression used for the language of ‘{1}’ includes an aggregate or lookup function. Aggregate and lookup functions cannot be used in report language expressions.
The expression used for the report language includes an aggregate or lookup function. Aggregate and lookup functions cannot be used in report language expressions.
Remove or modify the Report.Language value expression that refers to the aggregate function. Report language expressions must not contain aggregate functions.
A {2} expression used for the report parameter ‘{1}’ includes an aggregate or lookup function. Aggregate and lookup functions cannot be used in report parameter expressions.
The expression used for the report parameter includes an aggregate or lookup function. Aggregate and lookup functions cannot be used in report parameter expressions.
Remove or modify the expression that refers to an aggregate function within the ReportParameter element. Aggregate functions cannot be used in report parameter expressions.
The {2} expression for the {0} ‘{1}’ contains an aggregate function (or RunningValue or RowNumber functions) in the argument to another aggregate function (or RunningValue). Aggregate functions cannot be nested inside other aggregate functions.
The expression for the specified item contains an aggregate function (or RunningValue or RowNumber functions) in the argument to another aggregate function (or RunningValue). Aggregate functions cannot be nested inside other aggregate functions.
Remove or modify the aggregate expression that refers to another aggregate in the same expression. Aggregate functions cannot be placed inside another aggregate function.
The {2} expression for the {0} ‘{1}’ uses an aggregate function with an expression that returned a data type not valid for the aggregate function.
The expression for the specified item uses an aggregate function with an expression that returned a data type not valid for the aggregate function.
The {2} expression for the {0} ‘{1}’ uses an aggregate function on data of varying data types. Aggregate functions other than First, Last, Previous, Count, and CountDistinct can only aggregate data of a single data type.
The expression for the specified item uses an aggregate function on data of varying data types. Aggregate functions other than First, Last, Previous, Count, and CountDistinct can only aggregate data of a single data type.
The {2} expression for the {0} ‘{1}’ uses a numeric aggregate function on data that is not numeric. Numeric aggregate functions (Sum, Avg, StDev, Var, StDevP, and VarP) can only aggregate numeric data.
The expression for the specified item uses a numeric aggregate function on data that is not numeric. Numeric aggregate functions (Sum, Avg, StDev, Var, StDevP, and VarP) can only aggregate numeric data.
The {2} expression for the {0} ‘{1}’ contains a variable reference in the argument to an aggregate function (or RunningValue). Variable values cannot be used in aggregate functions.
The expression for the specified item contains a variable reference in the argument to an aggregate function (or RunningValue). Variable values cannot be used in aggregate functions.
The {2} expression for the {0} ‘{1}’ uses an aggregate function on a report item. Aggregate functions can be used only on report items contained in page headers and footers.
The expression for the specified item uses an aggregate function on a report item. Aggregate functions can be used only on report items contained in page headers and footers.
Remove or modify the aggregate expression that refers to the ReportItems global collection. Functions used must exist in a defined scope.
Filter, sort, and group expressions, and the set of lookup functions, do not support data type {2} in the {0} ‘{1}‘.
Filter, sort, and group expressions, and the set of lookup functions, do not support the specified data type in the specified item.
The {2} expression for the {0} {1} uses the aggregate function Aggregate. The aggregate function “Aggregate” cannot be used in a report that contains any filters.
The Aggregate function is designed to compute values across a dataset without considering filters. When filters are applied, the context changes, making the function invalid.
The {2} expression for the {0} {1} contains a direct or indirect reference to itself. Loops in expressions are not allowed.
The expression contains a direct or indirect reference to itself, creating a loop. Loops in expressions are not allowed.
The {2} expression for the {0} {1} contains a direct or indirect reference to itself. Loops in variable value expressions are not allowed.
The expression contains a direct or indirect reference to itself. Loops in variable value expressions are not allowed.
The {2} expression for the {0} contains a direct or indirect reference to itself. Loops in variable value expressions are not allowed.
The expression contains a direct or indirect reference to itself. Loops in variable value expressions are not allowed.
The {2} expression used in {0} {1} references a dataset field which contains an error: {3}
The expression references a dataset field that contains an error.
The {2} expression for the {0} ‘{1}’ specifies multiple incompatible scopes in the same aggregate expression. Nested aggregates cannot specify multiple peer groups and cannot specify both child groups and nested data regions. The scopes for all nested aggregates must be the same as, a parent of, or a child of the scopes all other nested aggregates in the same expression.
The expression specifies multiple incompatible scopes in the same aggregate expression. Nested aggregates must use compatible scopes.
The {2} expression {0} contains ‘{1}’ has a scope parameter that is not valid for an aggregate function. The scope parameter must be set to a string constant that is equal to either the name of a containing group, the name of a containing data region, or the name of a dataset.
The scope parameter in the aggregate function is not valid. It must be a string constant equal to a group, data region, or dataset name.
Remove or modify the scope parameter of an aggregate function. Specified scope is not valid. Scope should be the name of the group, data region, or data set.
The {2} expression used in {0} ‘{1}’ returned a data type that is not valid.
The expression returned a data type that is not valid.
The {0} ‘{1}’ has an invalid {2} “{3}”. The scope must be the current scope, or contained within the current scope.
The scope specified is invalid. It must be the current scope or contained within the current scope.
The {0} ‘{1}’ has an invalid {2} “{3}”. The {2} scope and the {4} scope must be contained in data regions sharing the same dataset.
The scope specified is invalid. Both scopes must be within data regions that share the same dataset.
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
The value provided for the ImageData property is not valid.
Provide the valid ImageData for the external image.
The {2} expression for the {0} ‘{1}’ has an aggregate function parameter that is not valid for the function RunningValue. The aggregate function parameter must be one of the following: First, Last, Sum, Avg, Max, Min, Count, CountDistinct, StDev, Var, StDevP, VarP.
The aggregate function parameter used in the RunningValue expression is not valid.
Remove or modify the function parameter of the RunningValue expression that refers to the Aggregate, Previous, or CountRows functions.
The {2} expression for the {0} ‘{1}’ contains an inner aggregate function with a scope argument that represents a scope that is not contained by or equal to the scope represented by the Previous function’s scope argument. The scope parameter of the inner aggregate must be contained by or equal to the scope represented by the Previous function’s scope argument.
The inner aggregate function’s scope is not contained by or equal to the scope used in the Previous function.
The {2} expression for the {0} ‘{1}’ has a scope parameter that is not valid for RunningValue, RowNumber or Previous. The scope parameter must be set to a string constant that is equal to the name of a containing group within the matrix ‘{3}’.
The scope parameter used in RunningValue, RowNumber, or Previous is not valid for the matrix.
The {2} expression for the {0} ‘{1}’ has a scope parameter that is not valid for RunningValue, RowNumber or Previous. The scope parameter must be set to a string constant that is equal to the name of a containing group within the Tablix ‘{3}’.
The scope parameter used in RunningValue, RowNumber, or Previous is not valid for the Tablix.
The {2} expression for the {0} ‘{1}’ refers to the {3} ‘{4}’. Expressions can only refer to a {3} declared within the same grouping scope, a containing grouping scope, or those declared on the report. Letters in the names of variables must use the correct case.
The expression refers to a variable outside its allowed scope. Variable names must also use correct casing.
A {2} for the {0} ‘{1}’ includes a Lookup function. Lookup functions cannot be used in expressions in a dataset filter.
A Lookup function is used in a dataset filter, which is not allowed.
The {2} expression for the {0} ‘{1}’ uses a lookup function with an expression that returned a data type that is not valid for the lookup function. The data type must be an RDL Variant type.
The Lookup function received a data type that is not valid. It must be an RDL Variant type.
The {2} expression for the {0} ‘{1}’ contains a variable reference in an argument to a Lookup or LookupSet function. Variable references cannot be used for the source, destination, or result Expression parameter of a lookup function.
A variable reference is used in a Lookup or LookupSet function argument, which is not allowed.
The {2} expression for the {0} ‘{1}’ uses an aggregate expression without a scope. A scope is required for all aggregates used outside of a data region unless the report contains exactly one dataset.
An aggregate expression is used without a scope. A scope is required unless the report contains exactly one dataset.
The {2} expression for the {0} ‘{1}’ references a field in an aggregate expression without a scope. A scope is required for all aggregates in the page header or footer which reference fields.
Aggregates in page headers or footers must specify a scope (like a dataset or group). Without it, the report engine doesn’t know where to pull the data from.
The chart ‘{1}’ has no data points. A chart requires at least one data point.
A chart must have at least one data point to render. This usually means the dataset is empty or the expression used to populate the chart is incorrect.
The {0} ‘{1}’ contains an invalid {2}. The {2}({3}) is missing a {4} element, which is mandatory.
A required element in a report definition (like a parameter or value) is missing, making the expression invalid.
The {2} expression for the {0} ‘{1}’ is missing.
A required expression (like a value or formula) is not provided.
Provide the value for the Variable.Value element in a report definition. The Variable.Value element must not be empty in the Variables collection.
The expression referenced a non-existing field in the fields collection.
The field name used in the expression doesn’t exist in the dataset.
The expression that references the field ‘{0}’ does not exist in the Fields collection. Expressions can only refer to fields within the current dataset scope or, if inside an aggregate, the specified dataset scope. Letters in the names of fields must use the correct case.
Field names are case-sensitive and must be within the current dataset scope.
The {2} expression for the {0} ‘{1}’ contains an error: {3}
A general error in the expression, such as syntax or logic issues.
An unexpected error occurred while compiling expressions. Native compiler return value: ‘{3}’.
A low-level error occurred during compilation, possibly due to malformed expressions.
An unexpected error occurred in Report Processing.
A generic error that may be caused by data issues, rendering problems, or configuration errors.
An unexpected error occurred while evaluating the {2} expression for the {0} ‘{1}’.
The expression failed during runtime evaluation.
The {2} expression for the {0} ‘{1}’ has an incorrect number of parameters for the function ‘{3}’.
Functions like Sum() or Avg() require specific parameters.
Specify the valid number of parameters to an aggregate expression. Functions used in an expression must contain required parameters. Example: =Sum()
Please validate the provided expression ‘{0}’ in the element is correct.
The expression may be syntactically or logically incorrect.
There is a syntax error in the {2} expression for the {0} ‘{1}’: ) expected.
A parenthesis is unmatched or misplaced.
Ensure the syntax of an expression is correct. An open parenthesis is not matched with a close parenthesis ).
The value expression refers to the field ‘{0}’. Report item expressions can only refer to fields within the current dataset scope or, if inside an aggregate, the specified dataset scope. Letters in the names of fields must use the correct case.
Fields must be referenced within the correct dataset or aggregate scope.
The {2} expression for the {0} ‘{1}’ refers directly to the field ‘{3}’ without specifying a dataset aggregate. When the report contains multiple datasets, field references outside of a data region must be contained within aggregate functions which specify a dataset scope.
In reports with multiple datasets, field references outside data regions must use aggregate functions with dataset scope.
The {2} expression for the {0} ‘{1}’ has a scope parameter that is not valid for a lookup function. The scope parameter must be set to a string constant that is the name of a dataset.
The scope must be a string constant matching a dataset name.
Remove or modify the Dataset parameter of a Lookup, LookupSet, or MultiLookup function in which the name of a data set does not exist in a report. Data set parameter values must exist in the ReportDatasets collection.
The {0} ‘{1}’ has a {2} using aggregates without explicit scopes and the {3} is omitted. Aggregates without an explicit scope are not allowed in the {2} if no {3} is specified.
Aggregates must have a defined scope if {3} (like a data region or group) is not specified.
The {0} ‘{1}’ is not contained in any data region or grouping and the {2} is omitted. The scope must be a peer scope which is a data region.
Scope must be defined for items outside data regions.
ReportSection.GetPageSections() was called for ReportSection {0} without calling ReportSection.SetPage(int, int). Call SetPage before calling GetPageSections.
The report engine requires SetPage() to be called before retrieving page sections.
The RichText {2} markup for the {0} ‘{1}’ failed to parse: {3}.
The markup used in a RichText expression is invalid.
Provide the valid markup text in an expression to render the value.
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid size. Valid sizes may not exceed 455 inches.
The specified size exceeds the maximum allowed (455 inches). This usually applies to dimensions like width, height, or margins.
The expression that references an item ‘{0}’ does not exist in the User collection. Letters in the names of User collection items must use the correct case.
The expression is trying to access a user property (like User!UserID) that is either misspelled or not available. User collection names are case-sensitive.
The {2} expression for the {0} ‘{1}’ contains an error: {3}
A general expression error, such as invalid syntax, unsupported functions, or incorrect references.
The {2} expression for the {0} ‘{1}’ contains the InScope or Level function in the Expression argument of a Previous function. The InScope and Level functions cannot be used in the Expression parameter of the Previous function.
InScope and Level functions are not allowed within the expression parameter of the Previous function.
Remove or modify the Previous aggregate expression in which the Expression parameter refers to an InScope or Level function. The Previous aggregate function must not contain InScope or Level functions.
The {2} expression for the {0} ‘{1}’ uses the function “Count(*, scope)”. This function is no longer supported - use “CountRows(scope)” instead.
The Count(*) syntax is no longer supported. Use CountRows(scope) instead.
The {2} expression for the {0} ‘{1}’ uses the function “RunningValue(*, Count, scope)”. This function is no longer supported - use “RowNumber(scope)” instead.
Replace with RowNumber(scope) for similar functionality.
More than one dataset, data region, or grouping in the report has the name ‘{3}’. Dataset, data region, and grouping names must be unique within a report.
All names must be unique within a report.
Provide unique names for Group elements, DataRegion elements, and data sets. Ensure that the name properties of two or more Group elements, DataRegion elements, or data sets are different within the same report.
An error has occurred during data evaluation of the GaugePanel ‘{0}‘.
A runtime error occurred while processing data for a gauge panel. Could be due to invalid expressions or data issues.
Minimum for Scale should be less than Maximum of GaugePanel ‘{0}‘.
The scale range is invalid.
Make sure the minimum scale value of the gauge panel is less than the maximum scale value.
StartValue for Range should be less than EndValue of GaugePanel ‘{0}‘.
The range values are reversed.
Make sure the start range value of the gauge panel is less than the end range value.
The {0} ‘{1}’ has an invalid {2}. The {2} contains a {3}, ‘{4}‘. Row {2} must be static.
A row in a gauge must be static and cannot contain dynamic elements like groups.
The {0} ‘{1}’ has an invalid {2}. Row GaugeMember cannot contain child members.
Gauge rows must not have nested members.
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.
Page breaks are not allowed in gauge elements.
GaugePanel has been initialized
Informational message indicating the gauge panel setup has started.
The {0} ‘{1}’ has an invalid {2}. Column GaugeMember cannot contain multiple child members.
Gauge columns must have only one child member.
Cannot automatically calculate the value for either the minimum or maximum of the state indicator ‘{3}’ in {0} ‘{1}‘.
The system cannot infer the range. You must manually specify it.
Minimum should be less than Maximum for state indicator ‘{1}’ in gauge panel ‘{0}‘.
The range is invalid.
Make sure the minimum value of the state indicator gauge panel is less than the maximum scale value.
{2} for state indicator ‘{3}’ in {0} ‘{1}’ must be specified.
A required property (like StartValue, EndValue, or Color) is missing.
The {2} ‘{3}’ for {0} ‘{1}’ does not exist.
A referenced item (like a dataset, field, or group) is missing or misspelled.
The {0} ‘{1}’ has an invalid {2}. The {2} contains a {3}, ‘{4}‘. Row {2} must be static.
A row in a gauge must be static and cannot contain dynamic elements like groups.
The {0} ‘{1}’ has an invalid {2}. Row MapMember cannot contain child members.
In map controls, row members must be static. Nested or dynamic members are not allowed.
Cannot load shapefile ‘{2}’ for the {0} ‘{1}’. If you are connected to a report server, check the log files for more information.
The shapefile could not be loaded. This could be due to a missing file, incorrect path, or server access issues. Check report server logs for more details.
The expression that specifies the binding field ‘{3}’ for layer ‘{2}’ in the {0} ‘{1}’ is not valid. The data type does not match the map matching field data type.
The data type of the binding field must match the data type of the spatial field in the shapefile or spatial dataset.
The layer ‘{2}’ in the {0} ‘{1}’ has a field name ‘{3}’ that is not valid.
The field name does not exist or is misspelled. Field names are case-sensitive.
The shapefile url ‘{2}’ for the {0} ‘{1}’ is not valid. Details: {3}
The URL is incorrect or inaccessible. Details in {3} may provide more context (For Example: 404 error, permission denied).
The spatial data for layer ‘{2}’ in the {0} ‘{1}’ is not valid. Specify spatial data that is data type SqlGeometry or SqlGeography.
The spatial data must be of type SqlGeometry or SqlGeography.
The layer ‘{2}’ in the {0} ‘{1}’ is not valid. Specify a valid value for the {3} property.
A required property (like BindingField, ColorRule, etc.) is missing or incorrectly set.
The number of spatial elements for {0} ‘{1}’ exceeds the maximum limit for the map. The remaining spatial data does not appear in the map.
The map has a rendering limit. Extra spatial elements will not be displayed.
The number of map point elements for {0} ‘{1}’ exceeds the maximum limit for the map. The remaining points do not appear in the map.
Too many point elements (like markers) were added to the map, exceeding its display limit. Extra points are ignored to maintain performance.
The {2} was already defined for {0} ‘{1}’.
Duplicate property or element name. All names must be unique within the report.
Cannot load shapefile ‘{3}’ into layer ‘{2}’ for the {0} ‘{1}’. Spatial element type does not match the layer type.
The spatial element type in the shapefile does not match the expected type for the layer (For Example: polygon vs. point).
The binding or the grouping for layer ‘{2}’ in the {0} ‘{1}’ is not valid. A spatial element cannot have more than one matching group instance.
A spatial element is matched to more than one group instance, which is not allowed.
The type of the value field ‘{3}’ for layer ‘{2}’ in the {0} ‘{1}’ is not supported.
The field used for color rules, size rules, or labels must be of a supported data type (For Example: numeric or string).
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.
Page breaks are not allowed in map elements.
The {0} ‘{1}’ has an invalid {2}. Column MapMember cannot contain multiple child members.
Map columns must have only one child member.
The {2} expression for the {0} ‘{1}’ uses the Union aggregate function on data of varying data types. The Union function aggregates data of a single data type only.
The Union aggregate function can only be used on spatial data of the same type.
The {2} expression for the {0} ‘{1}’ uses the Union aggregate function on data that is not spatial. The Union function aggregates SQLSpatial or SQLGeometry data types only.
The Union aggregate function can only be used on spatial data of the same type.
The group ‘{3}’ in the {0} ‘{1}’ is marked to create page break for each group. Page breaks are not supported for column groupings in matrixes.
Page breaks are not allowed in matrix column groups.
The matrix ‘{1}’ has a MatrixRow that contains a different number of MatrixCell elements than the number of StaticColumn elements in the matrix. If the matrix contains no StaticColumns, each MatrixRow must contain one MatrixCell.
Each row must align with the number of static columns. If no static columns exist, each row must have exactly one cell.
The matrix ‘{1}’ contains a different number of MatrixColumn elements than the number of StaticColumn elements. If the matrix contains no StaticColumns, it must contain one MatrixColumn.
The matrix structure is inconsistent. If no static columns are defined, only one MatrixColumn is allowed.
The matrix ‘{1}’ contains a different number of MatrixRow elements than the number of StaticRow elements. If the matrix contains no StaticRows, it must contain one MatrixRow.
The matrix structure is inconsistent. If no static rows are defined, the matrix must contain exactly one MatrixRow.
A {2} in the matrix ‘{1}’ contains more than one report item. Each section in a matrix can contain at most one report item.
Each matrix cell or section can only contain one report item (For Example a textbox or image).
The {2} has an invalid number of number of {3}. {2} is limited to one {3}.
The element {2} is limited to only one {3} (For Example: a matrix column group can only have one dynamic group).
The {2} expression for the {0} ‘{1}’ uses an aggregate expression with an invalid recursive/simple flag. The valid values for this flag are ‘Recursive’ and ‘Simple’.
The flag must be either Recursive or Simple when using aggregate functions like Sum.
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
These errors indicate that the value assigned to a property (like size, color, format, etc.) is not acceptable. The property name and value must match expected formats or types.
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
These errors indicate that the value assigned to a property (like size, color, format, etc.) is not acceptable. The property name and value must match expected formats or types.
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
These errors indicate that the value assigned to a property (like size, color, format, etc.) is not acceptable. The property name and value must match expected formats or types.
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
These errors indicate that the value assigned to a property (like size, color, format, etc.) is not acceptable. The property name and value must match expected formats or types.
The {2} expression for the {0} ‘{1}’ has the value “{3}”, which is not a valid Boolean value.
These errors indicate that the value assigned to a property (like size, color, format, etc.) is not acceptable. The property name and value must match expected formats or types.
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
These errors indicate that the value assigned to a property (like size, color, format, etc.) is not acceptable. The property name and value must match expected formats or types.
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
These errors indicate that the value assigned to a property (like size, color, format, etc.) is not acceptable. The property name and value must match expected formats or types.
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2} for language ‘{4}’.
The value provided is not valid in the context of the specified language or locale.
The {0} ‘{1}’ has a CategoryGrouping with both or neither of the following: DynamicCategories and StaticCategories. CategoryGrouping must have exactly one of these elements.
A CategoryGrouping must have exactly one of these elements, not both or none.
The {2} expression for the {0} ‘{1}’ contains a colon or a line terminator. Colons and line terminators are not valid in expressions.
Colons (:) and line breaks are not allowed in expressions.
Remove or modify the expression that contains a line terminator or colons.
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
Similar to RE0385–RE0391, this indicates an invalid property value.
The {2} expression for the {0} ‘{1}’ uses the function Aggregate with an invalid expression parameter. The expression parameter must be a simple field reference.
The expression must be a simple field reference (For Example: =Fields!Sales.Value).
The {2} expression for the {0} ‘{1}’ uses the function Aggregate with an invalid scope parameter. The scope parameter must be the name of a scope where all containing grouping scopes have group expressions that are simple field references or constants.
The scope must be a valid grouping or dataset name where all group expressions are simple field references or constants.
A custom property in the {0} ‘{1}’ has the name “{2}”. Custom property names cannot be null and must be unique within the custom properties collection.
Custom property names must be unique and not null.
Provide a unique name attribute in the CustomReportItem. Ensure that the name properties of two or more custom report items are different within the same report.
The {2} expression for the {0} ‘{1}’ did not evaluate to an image.
The expression must return a valid image (For Example a byte array or image URL).
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
Another instance of an invalid property value. Ensure the value matches the expected type and format.
The {3} property for the {0} ‘{1}’ contains ‘{4}’. Field names must be greater than 0 and less than or equal to {5} characters.
The specified field name is either too short or too long. Field names must contain at least one character and must not exceed the maximum allowed length (defined by the system). Ensure the field name length is within the valid range.
The {3} property for the {0} ‘{1}’ contains ‘{4}’, which is not a CLS-compliant identifier.
The identifier used is not CLS-compliant. CLS (Common Language Specification) compliance ensures that identifiers are usable across all .NET languages. Avoid using special characters or reserved keywords.
The {2} expression for the {0} ‘{1}’ has the value “{3}”, which is not a valid DateTime value.
The expression provided does not evaluate to a valid DateTime value. Ensure the format matches the expected date and time format (For Example: yyyy-MM-dd HH:mm:ss).
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
The value assigned to the property is not valid for its expected data type. Check the expected format or type and correct the value accordingly.
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
The value assigned to the property is not valid for its expected data type. Check the expected format or type and correct the value accordingly.
The {2} expression for the {0} ‘{1}’ has the value “{3}”, which is not a valid Float value.
The expression does not evaluate to a valid floating-point number. Ensure the value is numeric and formatted correctly (For Example: 123.45).
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
The value provided is not valid for the expected property type. Double-check the data type and format required for the property.
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
The value provided is not valid for the expected property type. Double-check the data type and format required for the property.
The {2} value for the {0} ‘{1}’ is not valid. {3}
The value provided is not valid for the specified context. The error message includes additional details to help identify the issue. Review the context and correct the value accordingly.
The {2} expression for the {0} ‘{1}’ has the value “{3}”, which is not a valid integer value.
The expression does not evaluate to a valid integer. Ensure the value is a whole number without decimals or invalid characters.
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
The value assigned to the property is not valid. Check the expected data type and constraints for the property.
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
The value assigned to the property is not valid. Check the expected data type and constraints for the property.
The {2} property of the {0} ‘{1}’ uses the unit name “{3}”, which is not valid. Valid unit names include mm, cm, in, pt, and pc.
The unit name used is not recognized. Valid unit names include mm, cm, in, pt, and pc. Use one of these standard units.
The {2} expression for the {0} ‘{1}’ contains ‘Me.Value’. ‘Me.Value’ is not valid in the context of a {0}.
The expression contains Me.Value, which is not valid in the current context. Avoid using Me.Value in expressions where it is not supported.
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
The value provided is not valid for the specified property. Ensure the value adheres to the expected format and constraints.
{1}’ is not a valid {0} name. Names of objects must be greater than 0 and less than or equal to {3} characters.
The object name is either too short or too long. Object names must contain at least one character and must not exceed the maximum allowed length.
‘{1}’ is not a valid {0} name. Names of objects must be CLS-compliant identifiers.
The object name is not CLS-compliant. Use only valid characters and avoid reserved keywords to ensure compatibility across .NET languages.
The filter for {0} ‘{1}’ has an incorrect number of filter values for the operator. The operator ‘{3}’ requires exactly {4} filter value(s).
The filter operator used requires a specific number of filter values, but the provided number is incorrect. Adjust the number of filter values to match the operator’s requirements.
Remove or modify the filter value based on the filter operator. Example: Equal to operator must evaluate with one FilterValues.FilterValue
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
The value assigned to the property is not valid. Check the expected format or type and correct the value accordingly.
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2} for language ‘{4}’.
The value provided is not valid for the specified property in the context of the given language. Ensure the value is appropriate for the language setting.
The {2} in the {0} ‘{1}’ has the name ‘{3}’, which is not a CLS-compliant identifier.
The specified name is not CLS-compliant. CLS (Common Language Specification) identifiers must begin with a letter and contain only alphanumeric characters and underscores. Avoid using special characters or reserved keywords.
The {2} in the {0} ‘{1}’ has the name ‘{3}‘. {2} names cannot be null and must be unique within the {2} collection for the {0}.
The name of the element is either missing or not unique within its collection. Each element in a collection must have a non-null, unique name to avoid conflicts and ensure proper referencing.
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
The value assigned to the property is invalid. Ensure the value matches the expected data type and format for the property.
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
The value assigned to the property is invalid. Ensure the value matches the expected data type and format for the property.
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
The value assigned to the property is invalid. Ensure the value matches the expected data type and format for the property.
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
The value assigned to the property is invalid. Ensure the value matches the expected data type and format for the property.
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
The value assigned to the property is invalid. Ensure the value matches the expected data type and format for the property.
The {0} ‘{1}’ has expression-based {2}. The sizes of the value and the label (multi-value) arrays have to be identical.
The expression-based property uses arrays for values and labels, but their lengths do not match. Both arrays must have the same number of elements to ensure correct mapping.
The {0} ‘{1}’ has an invalid {2} element. The {2} element must contain at least one Variable.
The specified element must contain at least one variable. An empty element is not valid and must be populated with at least one defined variable.
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
The value provided is not valid for the property. Check the expected format and correct the value accordingly.
The element {3} named ‘{2}’ is not valid for {0} ‘{1}‘. The Writable flag can only be specified for the {3} collection on the Report.
The Writable flag is used incorrectly. It can only be applied to elements within the Writable collection of a Report. Remove or relocate the flag as needed.
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
The value assigned to the property is not valid. Ensure it matches the expected format and type.
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’ or ‘Auto’.
The specified value is not valid for the property. It must be an integer between -90 and 90, or one of the special values: RightAngle or Auto.
Specify a valid URL. Report URLs may use only http://, https://, ftp://, file:, mailto:, or news:.
The URL provided is not valid. Only the following protocols are supported: http://, https://, ftp://, file:, mailto:, and news:. Ensure the URL uses one of these schemes.
The {2} is missing for the {0} ‘{1}’.
A required property is missing. Ensure that all mandatory properties are defined for the specified element.
The {0} ‘{1}’ has an invalid {2} “{3}”. The scope does not exist in the current report.
The specified scope does not exist in the current report. Verify that the scope name is correct and that it has been defined earlier in the report.
Near character position {4} in the input string, the value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
The value is invalid and the error occurs near the specified character position in the input string. Review the string for formatting or syntax issues at or near the indicated position.
Near character position {4} in the input string, the value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid size. Valid sizes may not exceed 455 inches.
The size value is invalid and exceeds the maximum allowed size of 455 inches. Check the input string near the specified character position for errors.
Near character position {4} in the input string, The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
The value is not valid for the property, and the issue occurs near the specified character position in the input string. Review the value and correct any formatting or syntax issues.
The {2} expression for the {0} ‘{1}’ contains the Previous function in an argument to a Lookup or LookupSet function. The Previous function cannot be used for the destination or result Expression parameter of a lookup function.
The Previous function is used incorrectly within a Lookup or LookupSet function. Previous cannot be used in the destination or result expression of a lookup function. Remove or replace it with a valid expression.
You have attempted to use a rendering extension that is either not registered for this report server or it is not supported in this edition of Reporting Services.
The report server does not recognize or support the rendering format specified.
The subreport ‘{3}’ could not be processed. Parent report ‘{4}’ failed to automatically republish, or it contains a Reporting Services 2005-style CustomReportItem, and is therefore incompatible with the subreport. To correct this error, please attempt to republish the parent report manually. If it contains a CustomReportItem, please upgrade the report to the latest version.
The parent report may contain outdated elements like CustomReportItems from SSRS 2005 or failed to republish.
The subreport ‘{3}’ could not be processed within parent report ‘{4}’ due to a mismatch in execution engines. Either the subreport failed to automatically republish, or the subreport contains a Reporting Services 2005-style CustomReportItem. To correct this error, please attempt to republish the subreport manually. If it contains a CustomReportItem, please upgrade the report to the latest version.
This can occur due to outdated subreport elements or failed republishing.
An error occurred while executing the subreport ‘{1}’ (Instance: {2}): {3}
A runtime error occurred while executing the subreport.
The subreport ‘{0}’ could not be found at the specified location {1}. Please verify that the subreport has been published and that the name is correct.
The subreport is missing or the path is incorrect.
Provide the valid subreport report name or make sure that the provided subreport exists in the mentioned location.
Error: Subreport could not be shown.
A generic error indicating the subreport failed to render.
Data could not be retrieved for the subreport, ‘{0}’, located at: {1}. Data is only retrieved during the initial request or during snapshot creation.
Data is only fetched during the initial request or snapshot creation.
Data retrieval failed for the subreport, ‘{0}’, located at: {1}. Please check the log files for more information.
The subreport failed to fetch data.
One or more parameters were not specified for the subreport, ‘{0}’, located at: {1}.
Required parameters were not provided.
Warnings occurred while executing the subreport ‘{1}’.
The subreport executed with warnings.
The {0} ‘{1}’ has a detail member with inner members. Detail members can only contain static inner members.
Detail members can only contain static inner members.
Remove or modify the detail group of the data region item. Detail members can only contain the static inner members.
The {0} ‘{1}’ includes a group header with {2} set to true. This is not allowed on group headers or footers.
Group headers/footers cannot have this property enabled.
The {0} ‘{1}’ has an invalid {2}. The CellContents for this {2} must be omitted because it is covered by a span from another {2}.
A cell is incorrectly defined due to a span conflict.
The {0} ‘{1}’ has an invalid {2}. The CellContents for this {2} is required if not covered by a span from another {2}.
A cell is missing content and not covered by another span.
The {0} ‘{1}’ is in a list that has no group expressions defined for it. To use a data region in a list, the list must have group expressions.
Lists must have group expressions to contain data regions.
The {0} ‘{1}’ is in the page header or footer. Data regions and subreports cannot be used in page headers or footers.
Data regions and subreports are not allowed in headers/footers.
Remove or modify the Tablix, Chart, GaugePanel, or SubReport element within either a Page.PageHeader element or a Page.PageFooter element.
The {0} ‘{1}’ is contained inside a table detail row. Data regions are not allowed inside a table detail row.
Data regions are not allowed in table detail rows.
The {0} ‘{1}’ is in the report body but the report has no dataset. Data regions are not allowed in reports without datasets.
Data regions require a dataset.
Remove or modify the Tablix, GaugePanel, Chart, or SubReport instance within a report that does not have an associated data set.
A {2} within the grouping ‘{4}’ in the {0} ‘{1}’ has a duplicate name, ‘{3}‘. {2} names must be unique within the report.
Names must be unique within the report.
The {0} ‘{1}’ has a {2} that contains hidden content. Either the ColSpan or RowSpan is set to 0.
A cell is hidden due to invalid span settings.
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.
Each row in a Tablix must have the same number of cells. A mismatch causes rendering issues.
The {0} ‘{1}’ contains a set of TablixMembers with FixedData set to true in the TablixColumnHierarchy which is incompatible with the cells in the TablixRow at index {2}. The cells corresponding to the fixed columns must begin and end inside the range of fixed columns.
Fixed columns must align with the corresponding cells in the row.
The {0} ‘{1}’ has an incorrectly set {2} property. {2} is not allowed to be set on the first column TablixMember when Tablix.GroupBeforeRowHeaders is set to true.
This property is not allowed when Tablix.GroupBeforeRowHeaders is true.
The {0} ‘{1}’ has an incorrectly set {2} property within the {3}. Only the outermost TablixMembers in a hierarchy can have FixedData set to true.
FixedData is incorrectly applied to an inner member.
The {0} ‘{1}’ has an incorrectly set {2} properties within the {3}. All TablixMembers with FixedData set to true must be contiguous.
Non-contiguous FixedData members cause layout issues.
The {0} ‘{1}’ has an incorrectly set {2} property. {2} is not allowed to be set on row TablixMember, unless it is also set on the first row TablixMember.
FixedData must be set on the first row if used on any row.
The {0} ‘{1}’ has an incorrectly set {2} property on the opposite hierarchy, based on the property {3} of {0}.
A property is misaligned with the hierarchy it’s intended for.
The {0} ‘{1}’ includes improperly placed columns with {2} set to true. These columns must be side-by-side, must start with either the left-most or right-most table column, and cannot be applied to all columns on the table.
Fixed columns must be adjacent and start from the edge.
The {0} ‘{1}’ has an invalid TablixMember. The child TablixMember with Group name ‘{2}’ is not a dynamic TablixMember and one of its ancestors is a detail TablixMember. All descendants of a static or detail TablixMember must also be a static or detail TablixMember.
All descendants of a static or detail member must also be static or detail.
A group expression for the {0} ‘{1}’ uses the RowNumber function with a scope parameter that is not valid. When used in a group expression, the value of the scope parameter of RowNumber must equal the name of the group directly containing the current group.
The scope must match the immediate parent group.
The {0} ‘{1}’ contains a non-static {2} group without grouping expression. Detail groups are not supported.
Detail groups are not supported without a grouping expression.
The grouping ‘{3}’ in the {0} ‘{1}’ has invalid {2} name ‘{4}‘.
The name used is not valid for the specified grouping.
The grouping ‘{3}’ in the {0} ‘{1}’ has DataSet ‘{4}’ as its domain scope. Only DataRegions and Grouping are allowed for {2}.
Only DataRegions and Groupings can be used as domain scopes.
The map grouping ‘{3}’ in the {0} ‘{1}’ has {2} ‘{4}‘. Domain scope will be ignored for map report item.
Map items do not support domain scope.
The grouping ‘{3}’ in the {0} ‘{1}’ has invalid {2} ‘{4}‘. Domain Scope is allowed only if it is an ancestor scope.
The specified scope is not an ancestor of the grouping.
The non leaf grouping ‘{3}’ in the {0} ‘{1}’ has {2} ‘{4}‘. Domain scope is only allowed for leaf grouping.
Non-leaf groupings cannot have domain scope.
The grouping ‘{3}’ in the {0} ‘{1}’ has {2} ‘{4}’ with Parent defined. Grouping with parent defined cannot be a domain scope target.
Domain scope is not valid when a parent is defined.
The detail grouping ‘{3}’ in the {0} ‘{1}’ has {2} ‘{4}‘. Domain scope is only allowed for non detail groups.
Detail groups cannot be used as domain scope targets.
The grouping ‘{3}’ in the {0} ‘{1}’ has {2} ‘{4}’ and Parent defined. Domain scope is only allowed if Parent is not defined.
A group with a parent cannot be a domain scope.
A grouping in the {0} ‘{1}’ has the name ‘{3}’. Grouping names must be greater than 0 and less than or equal to {3} characters.
Grouping names must be between 1 and {3} characters.
Provide a valid grouping name. The name should not be empty or longer than 256 characters.
A grouping in the {0} ‘{1}’ has the name ‘{3}’. Grouping names must be CLS-compliant identifiers.
Grouping names must follow Common Language Specification (CLS) rules.
Specify the grouping name with a valid format. The name should not contain spaces and it must begin with a letter followed by letters, numbers, or the underscore character _.
A grouping in the {0} ‘{1}’ has Parent and more than one group expressions. Parent is only allowed if the grouping has exactly one group expression.
A grouping can only have a Parent if it has exactly one group expression.
A {2} within the grouping ‘{4}’ in the {0} ‘{1}’ has an invalid name, ‘{3}‘. {2} names must be greater than 0 and less than or equal to {5} characters.
The name is either empty or exceeds the maximum allowed length.
Provide avalid grouping variable name. The name should not be empty or longer than 256 characters.
A {2} within the grouping ‘{4}’ in the {0} ‘{1}’ has an invalid name, ‘{3}‘. {2} names must be CLS-compliant identifiers.
The name is not CLS-compliant.
Specify the grouping variable name with a valid format. The name should not contain spaces and it must begin with a letter followed by letters, numbers, or the underscore character _.
The value ‘{3}’ of the {2} property of the {0} ‘{1}’ is invalid. This value is the name of a group or dataset over which to apply the hiding: it should either be the name of a group containing the current group or, to hide duplicates over the entire dataset, the name of the current dataset.
The value must be a group containing the current group or the dataset name.
The {0} ‘{1}’ contains an invalid {2} (Expected: {3}; Actual {4}). The {2} of inner or nested DataRegions must be the same as the {2} of the outer DataRegion.
Inner DataRegions must match the outer DataRegion’s {2} property.
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 dynamic {2}. (Expected Value: ‘{4}’; Actual Value: ‘{5}‘)
All dynamic elements must have the same {3} property value.
The {0} ‘{1}’ has an invalid {2}. All {2} elements in a TablixColumnHierarchy must have the {3} property set to ‘{4}‘.
All TablixMembers must have the {3} property set to ‘{4}‘.
Provide the TablixMember instance within the Tablix.TablixColumnHierarchy with a TablixMember.KeepWithGroup set to a value other than None.
The {0} ‘{1}’ has an invalid {2}. A {2} that is dynamic (For Example has a Group specified) or has dynamic descendants must have the {3} property set to ‘{4}‘.
Required property is missing for dynamic elements.
A {2} in the matrix ‘{1}’ contains an invalid report item. Each subtotal in a matrix can contain at most one text box.
Each subtotal cell can only contain one text box.
The use of a Previous aggregate function in a matrix cell within matrix ‘{3}’ is not supported.
This function cannot be used in matrix cells.
The use of a Previous aggregate function in a TablixCell within Tablix ‘{3}’ is not supported.
This function is not allowed in Tablix cells.
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 dynamic {2}. (Expected Value: ‘{4}’; Actual Value: ‘{5}‘)
All dynamic elements must have the same {3} property value.
The {0} ‘{1}’ has an invalid {2}. All {2} elements in a TablixColumnHierarchy must have the {3} property set to false.
A {2} has an incorrect value for the {3} property.
Provide the TablixMember instance within the Tablix.TablixColumnHierarchy with a TablixMember.KeepWithGroup set to a value other than false.
The {0} ‘{1}’ has a RepeatWith property. Data regions, subreports, and rectangles that contain a data region or subreport cannot have a RepeatWith.
Data regions, subreports, or rectangles containing them cannot use RepeatWith.
The {0} ‘{1}’ has a RowGrouping with both or neither of the following: DynamicRows and StaticRows. RowGrouping must have exactly one of these elements.
Only one of these elements is allowed.
The {2} of the {0} ‘{1}’ has an invalid value. The {2} must be 0, if the TablixCell has no CellContents; or greater than 0, if TablixCell has CellContents.
If CellContents is missing, {2} must be 0; otherwise, it must be greater than 0.
The {0} ‘{1}’ has an invalid TablixCell. The {2} of the TablixCell is invalid. The TablixCell cannot span columns under TablixMembers in the TablixColumnHierarchy that are not static siblings, and the spanned cells must all exist under the same dynamic TablixMember in the TablixColumnHierarchy, if one exists.
Cells cannot span across non-static siblings or unrelated dynamic members.
The {0} ‘{1}’ has an invalid set of TablixCells. The combined value of the ColSpan properties of the TablixCells within a TablixRow does not equal the number of leaf TablixMembers (TablixMembers with no submembers) in the TablixColumnHierarchy.
The total ColSpan must equal the number of leaf columns.
The {0} ‘{1}’ has an invalid TablixCell. The {2} of the TablixCell is invalid. The TablixCell can only span one row.
TablixCells can only span a single row.