Error codes in report parsing and processing
This section provides a detailed explanation and solution to the respective problems in the Report Viewer for parsing and processing the report.
RV0001
The source of the report definition has not been specified.
Description
The Report Viewer will not render the report when either the report path or stream is not set, or the given path is incorrect.
Solution
- Make sure that the report path is specified and ensure whether the name or report path is correct.
- Check whether the report exists in the specified directory or not and also it should be accessible.
RV0009
Provide Report Server information to get shared data source information.
Description
Report with a shared data source must contain the Report Server information and credentials that are provided to render in the Report Viewer.
Solution
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");RV0010
An error occurred while sending a request to the reporting service.
Description
Report will not be rendered when there is a problem while connecting or retrieving the data from the provided reporting service’s URL.
Solution
- Make sure that you are connected to the internet.
- Ensure that the specified reporting service URL is valid.
- whether the reporting service is running or not.
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)
RV0013
The report definition has an invalid schema version.
Description
Report definition should contain the supported schema version (for example, 2008) to render the report in the Report Viewer.
Solution
Make sure that the provided schema in your report definition is supported in the Report Viewer. Supported versions are 2008, 2010, and 2016.
RV0014
The requested file or assembly was not found. It may have either moved or renamed.
Description
Any of the assembly related to the report platform is missing at the installation location.
Solution
- If you are previewing the report from the Report Designer, check whether any assembly is missing at the installed location
(C:\Program Files (x86)\Bold Reports\Report Designer)or reinstall the Report Designer application. - If you are loading the report from SDK sample, check whether any assembly is missing at the installed location
(C:\Program Files (x86)\Bold Reports\Embedded Reporting\Assemblies)or reinstall the Report Platform SDK application. - If you are loading the report from the Report Server, check whether any assembly is missing at the installed location
(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.
RV0023
Expressions are not used within the scope.
Description
Report Viewer encounters an error when an expression must be used outside the scope.
Solution
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.
RV0024
An error occurred during the local report processing. There is an error that occurred while rendering the custom code.
Description
Report Viewer encounters an error when compiling the custom code used in the report.
Solution
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.
RV0034
The Value property of an image report item contains an invalid value.
Description
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.
Solution
Ensure that the value provided to the image report item is specified properly, and make sure that the image is available.
- Embedded: Image data should be available in a report definition.
- External: External images can be obtained by specifying a URL and make sure that credentials are sufficient to access the image.
- Database: Images can be referred from the dataset, and make sure that credentials are sufficient to access the database.
RV0051
The data source used in a report does not exist or not accessible.
Description
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.
Solution
Ensure whether the data source in a report exists in the referred location.
- For embedded data source, the data source is referred in the local machine.
- For shared data source, the data source exists on the server and used on the local machine. Make sure that the authentication is sufficient to access the data source.
RV0062
Fields cannot be used in report parameter expressions.
Description
Report Viewer does not render the report when the parameter contains field expressions and fields cannot be used in report parameter expressions.
Solution
Remove the field expressions used in parameter expressions.
RV0072
Forward dependencies are not valid.
Description
Report will not be rendered when there is an existence of forward dependencies between parameters.
Solution
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.
RV0073
Please select a value for the report parameter.
Description
Report parameters must be supplied with values if it is non-nullable while trying to preview the report in the Report Viewer.
Solution
Enter the value of the parameter in a parameter block when it is non-nullable or allow blank.
RV0075
The expression that references the parameter is not valid and does not exist in the parameter collection or forward dependencies.
Description
Report Viewer throws errors when you try to use a non-existing report parameter or with forward dependencies.
Solution
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.
RV0083
The value provided for the report parameter is not valid for its type.
Description
The report will not be rendered by the Report Viewer when the specified value for the report parameter is irrespective of its type.
Solution
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.
RV0084
Report item refers to an invalid DataSetName.
Description
Report will not be rendered in the Report Viewer when a non-existing dataset is used in the report.
Solution
- Embedded: Make sure that the report item referred dataset exists in the report definition.
- Shared: Make sure that the referred dataset exists on the server and accessible.
RV0089
Collection class or data table input is needed.
Description
To render the RDLC report in the Report Viewer, the report must have a collection class or data table input to rendering the report.
Solution
Make sure to provide dataset collection to render the report. Supported collections are IEnumerable, System.Data.DataTable, and System.Data.Dataset.
RV0152
Report variable or group variable reference cannot be used in report parameter expressions.
Description
Report Viewer does not render the report when the parameter contains group or report variables. Variable values cannot be used in report parameter expressions.
Solution
Remove the variable reference used in the parameter expressions.
RV0156
An invalid operator is used in expression.
Description
Report Viewer encounters an error if it contains an invalid operator in an expression.
Solution
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.
RV0164
Data region items are not allowed in reports without datasets to render in the Report Viewer.
Description
Report Viewer will not render the report when the data region items does not refer to the dataset.
Solution
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..).
RV0167
Toggle items must be text boxes that share the same scope, and they are not allowed in page headers or footers.
Description
In our Report Viewer, toggle items must be shared within the same scope, and they are not allowed in page headers and page footers.
Solution
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.
RV0175
A ReportName cannot be an empty string or just white space.
Description
In SubReport item, the ReportName property value cannot be an empty or just white space.
Solution
Make sure that the ReportName property value for the subreport item is not empty.
RV0293
Aggregate and lookup functions cannot be used in report parameter expressions.
Description
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.
Solution
Remove Aggregate and Lookup functions in your report parameter expressions.
RV0331
Lookup function has an incorrect number of parameters.
Description
Provided lookup function has an incorrect number of parameters in report definition.
Solution
Provide the correct number of arguments for lookup expressions in respective report item expressions and refer to the syntax of the lookup expressions.
RV0334
ReportItem expressions can be referred only to fields within the current dataset.
Description
ReportItem expressions can be referred only to fields within the current dataset. Make sure that the field expression is referred to the current dataset.
Solution
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")
RV0347
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.
Description
Report item referred dataset, data region, and grouping names must be unique within a report.
Solution
Provide a unique dataset, data region, and grouping name for their report item in your report definition.
- Incorrect: Dataset name: Item 1, Tablix name: Item 1
- Correct: Dataset name: Item 1, Tablix name: Item 1
RV0362
An error has occurred on the Report Server.
Description
Specified reporting service encounters an error while rendering the report in the Report Viewer.
Solution
- Check the error log file(s) generated in the below mentioned location.
(C:\Program Files\Bold Reports\Enterprise Reporting\idp\web\Logs) - For more information about the types of status code, refer to the available status code in online.
RV0394
The value expression for the TextRun contains a colon or a line terminator.
Description
The Textbox report item value expression contains a colon or a line terminator. Colons and line terminators are not valid in expressions.
Solution
Remove colons and line terminator used in the specified report item expression.
RV0444
Cannot load sub report.
Description
Sub report cannot be loaded with an invalid name or report path.
Solution
- Make sure that the sub report path is specified and ensure whether the name or path is correct.
- Check whether the report exists in the specified directory or not, and also it should be accessible.
RV0445
The subreport cannot be found at the specified location.
Description
Report will not be rendered in the Report Viewer when the report does not exist in the specified location.
Solution
Make sure that the report name or path is correct, and the report exists in the specified directory.
RV0446
Subreport cannot be shown.
Description
Report Viewer will not render the sub report without the ReportPath or ReportServerUrl.
Solution
Provide a subreport ReportPath or ReportServerUrl in your report.
RV0451
The tablix has a detail member with inner members. Detail members contain only static inner members.
Description
In the tablix report item, detail members contain only static inner members.
Solution
In the tablix report item, provide static inner members for their detail members.
RV0488
The tablix report item has an invalid Tablix member in the column hierarchy, and the KeepTogether property is not set to None.
Description
All tablix member elements in a TablixColumnHierarchy must have the KeepWithGroup property as None.
Solution
Set KeepWithGroup property as None in a TablixColumnHierarchy for all Tablix members in the tablix report item.
RV0534
Report Deserialization failed.
Description
An error occurred during the deserialization of the report definition.
Solution
- XML deserialization is failed due to incorrect item tags or missed elements. Report item elements should have its required attributes.
- Note: Detailed description with line number and position is mentioned in the Report Viewer instance error dialog.
RV0535
Provide Report Server information to get shared dataset information.
Description
Report with shared datasets must contain the Report Server information and credentials to render in the Report Viewer.
Solution
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");
RV0537
The ReportServerUrl or ReportServerCredential is missing.
Description
Server report or server referred items used in the report will not be rendered in the Report Viewer without ReportServerUrl and ReportServerCredential.
Solution
Make sure that the ReportServerUrl and ReportServerCredential are not empty and provided with proper data and are accessible.
RV0538
The value for the DataSetName property is missing.
Description
Data region items are not allowed in reports without datasets to render in the Viewer.
Solution
Make sure to provide a dataset name property value in your report definition and ensure that the property value is not empty.
RV0539
Provide dataset inputs for the report.
Description
To render the RDLC report, you must add the data source collection in the Report Viewer if any dataset is used in the report.
Solution
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.
RV0540
Invalid Expression
Description
Report Viewer does not render the report when an invalid expression is used.
Solution
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.
RV0542
Unsupported Expression
Description
Provided expression does not support in the Report Viewer. Object expressions do not have complete support.
Solution
Please use supported expressions in the Report Viewer to render the report.
RV0543
The DateAdd function should have arguments.
Description
Report Viewer encounters an error if DateAdd function does not contain any arguments.
Solution
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)
RV0544
The DateDiff function should contain arguments.
Description
Report Viewer encounters an error if DateDiff function does not contain arguments in an expression.
Solution
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")
RV0546
PaymentPeriod must be between 1 and numberOfPayments.
Description
Report Viewer encounters an error if the payment period does not fall within the range.
Solution
Provide payment period value between 1 and numberOfPayments.
RV0547
This implementation does not handle zero interest rate.
Description
Report is not rendered in the Report Viewer when it holds the zero interest rate.
Solution
Provide greater than 0 or less than 0 interest rate. Does not provide 0 value for their interest rate.
RV0548
Invalid Expression
Description
The expression used in the report is incorrect scope, syntax, or unsupported.
Solution
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.
RV0549
Method name is not a member in custom code.
Description
Evaluated method name is not a member in your custom code.
Solution
Provide a valid method name. Make sure that the provided method name is present in your custom code.
RV0552
Parameter is missing a value.
Description
Report Viewer will not render the report when the hidden parameter does not contain a value that is non-nullable.
Solution
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.
RE0001
The report path value cannot be null or empty.
Description
This error occurs when the ReportPath property of the Report Viewer is not assigned a valid report definition path.
Solution
Provide the valid relative or absolute path location of the report in the ReportPath property. Example: reportViewer.ReportPath = ../ReportTemplate.rdl;
RE0002
The path {0} specified for the report is not valid or not found.
Description
This error indicates that the path assigned to ReportPath either points to a non-existent report or is incorrectly formatted.
Solution
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.
RE0003
The {0} file input stream is null.
Description
This error is thrown when attempting to load a report using a stream, but the stream provided is null.
Solution
Make sure that the provided file input stream is not empty/null.
Example: reportViewer.LoadReport(reportStream);
RE0004
The stream input is not available for the report subreport {0}.
Description
This occurs when a subreport is expected, but the stream for the subreport is missing or not supplied.
Solution
To load a subreport, make sure to set the stream input in the LoadSubreport definition.
Example: reportViewer.LoadSubreport(subReportName, subReportStream);
RE0005
The report server URL specified is invalid.
Description
This error occurs when the ReportServerUrl provided to the viewer is incorrect or unreachable.
Solution
Provide the valid report server URL of a report in the ReportServerUrl property to load the server report.
Example: reportViewer.ReportServerUrl = @'http://localhost/reportserver';
RE0006
The credentials required to access the report server are not supplied.
Description
This error occurs when the ReportServerUrl provided to the viewer is incorrect or unreachable.
Solution
Specify report server credentials in the report viewer to access the report server.
Example: reportViewer.ReportServerCredential = new NetworkCredential('userName', 'password');
RE0007
The server report details have been given and the processing mode set to local incorrectly.
Description
This occurs when the processing mode is set to Local but server-related settings like ReportServerUrl are also specified, which causes a conflict.
Solution
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.
RE0008
The provided credentials are invalid to access the report server. Login failed for user ‘{0}‘.
Description
This error indicates that the authentication credentials supplied to the report server are incorrect.
Solution
Make sure that the provided credentials are valid to access the report server.
Example: reportViewer.ReportServerCredential = new NetworkCredential('userName', 'password');
RE0009
Failed to retrieve the {0} ‘{1}’ stream from the provided server details ‘{2}’
Description
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.
Solution
Provide the valid report server information (ReportServerURL, ReportServerCredential, ReportPath) to retrieve the report stream from server.
RE0010
An error occurred in communicating to the reporting service.
Description
This error is thrown when there is a network or configuration issue preventing the Report Viewer from connecting to the report server.
Solution
Verify that the report server is reachable and that correct details are provided. Also, ensure that firewalls or proxies are not blocking communication.
RE0011
The report definition is not valid.
Description
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.
Solution
Ensure that the provided report has a valid report definition. Example : Report element missing in .rdl file.
RE0012
An unexpected error occurred in Report Processing during serialization: {0}.
Description
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.
Solution
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.
RE0013
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}
Description
This error occurs when the report uses an unsupported ReportDefinition schema version or contains elements not recognized by the current Report Viewer.
Solution
Make sure that the provided schema in your report definition is supported in report viewer. Supported versions are 2008, 2010, and 2016.
RE0014
The dependent assembly was not found. It may have been either moved or renamed.
Description
The dependent assembly was not found. It may have been either moved or renamed.
Solution
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)
RE0015
The expression used for the language of ‘{1}’ refers to a field. Fields cannot be used in report language expressions.
Description
This error occurs when a field expression is incorrectly used in the reports Language property.
Solution
Make sure to avoid the usage of field expressions in report language expressions.
RE0016
The number of columns specified for the report body is not valid. The number of columns must be between 1 and 100.
Description
This error is thrown when the column count defined in the report body layout is outside the valid range.
Solution
Ensure that the number of columns in the rdl/rdlc report are in the range from 1 to 100.
RE0017
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.
Description
This error occurs when unsupported items (like a tablix or chart) are placed inside page headers or footers.
Solution
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.
RE0018
The {0} ‘{1}’ contains a {2} with a duplicate name, ‘{3}‘. {2} names must be unique within the report.
Description
This error is thrown when two or more report items share the same identifier, which must be unique.
Solution
Ensure that the report contains a unique report item or group name.
RE0019
A {2} in the {0} ‘{1}’ has an invalid {2} name, ‘{3}‘. {2} names must be CLS-compliant identifiers.
Description
This error occurs when a name assigned to a report item or variable violates Common Language Specification (CLS) naming rules.
Solution
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.
RE0020
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.
Description
This error is caused when the name of a report element (like a variable or group) is either empty or exceeds the allowed length.
Solution
Provide a valid variable name: the name should not be empty or longer than 256 characters.
RE0021
The {2} expression for the {0} ‘{1}’ refers to the global variable Aggregates, which is not defined.
Description
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.
Solution
Ensure that the expression contains valid global collection variant types.
RE0022
The First, Last aggregate functions cannot be specified as nested aggregates.
Description
This error occurs when First() or Last() functions are used inside other aggregate functions (like Sum(First(...))), which is not supported.
Solution
Remove the First, Last aggregate functions used in nested expressions.
RE0023
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.
Description
This error is triggered when a report expression refers to a variable that hasn’t been defined in the scope or has incorrect casing.
Solution
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.
RE0024
There is an error on line {4} of custom code: {3}
Description
This error occurs when the custom embedded code in the report fails to compile due to a syntax or runtime error.
Solution
Make sure that the provided custom code is compiled successfully without an error.
RE0025
More than one class instance in the report has the name ‘{1}‘. Class instance names must be unique within a report.
Description
This error occurs when multiple code class instances in the report share the same name.
Solution
Provide a unique class instance name and ensure that the InstanceNames of a two or more classes are different in a report.
RE0026
Error in class instance declaration for class {1}: {3}
Description
This error indicates a problem in the class instance declaration, such as incorrect syntax, invalid reference, or missing class in custom code.
Solution
Modify the class instance declaration and ensure there is no compile error.
RE0027
Failed to load assembly. Details: {3}
Description
This error is triggered when a required assembly (DLL) referenced in the report cannot be found or loaded.
Solution
Add the assemblies to the Assemblies API in the Report Viewer.
RE0028
Error while loading code module: ‘{3}‘. Details: {4}
Description
This error occurs when a report references a code module that is either missing, corrupted, or improperly referenced.
Solution
Ensure that elements of Report.CodeModule exist in a report to use in the expression.
RE0029
The report references the code module {3}, which is not a trusted assembly.
Description
This error indicates that the report tries to use a code module that is not whitelisted or trusted in the current environment.
Solution
Add the trusted assembly references in the code module.
RE0030
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.
Description
This error occurs when the name assigned to an embedded image is missing or exceeds the allowed length.
Solution
Provide the valid name in the Name property of EmbeddedImage; name length must be greater than zero and fewer than 256 characters.
RE0031
More than one embedded image in the report has the name {1}. Embedded image names must be unique within a report.
Description
This error occurs when multiple embedded images share the same name, which must be unique within a report definition.
Solution
Provide a unique name in EmbeddedImage and ensure that the name properties of two or more EmbeddedImages are different within the same report.
RE0032
The report contains an embedded image with an invalid name {1}. Embedded image names must be CLS-compliant identifiers.
Description
This error is thrown when the image name does not follow Common Language Specification (CLS) rules.
Solution
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.
RE0033
The embedded image {1} contains invalid data. Embedded image data must be a base 64 encoded string.
Description
This error indicates that the image data stored in the embedded image node is not valid Base64-encoded data.
Solution
Make sure that the embedded image data is in the proper format.
RE0034
The value of the {2} property for the {0} {1} is “{3}”, which is not a valid {2}.
Description
This error occurs when a report property (like MIMEType or Source) is assigned an invalid or unsupported value.
Solution
Use the existing embedded image within a report, ensure that the provided image exists in the Report.EmbeddedImages element in an RDL file.
RE0035
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.
Description
This error occurs when the Name property of a DataSource is missing or exceeds the allowed length.
Solution
Provide the valid name in the ‘Name’ property of DataSource. Name length must be greater than zero and fewer than 256 characters.
RE0036
The report contains an invalid data source with the name {1}. Data source names must be CLS-compliant identifiers.
Description
This error occurs when the data source name includes invalid characters or formatting that violates CLS (Common Language Specification) naming rules.
Solution
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.
RE0037
The data source {1} has both or neither of the following: DataSourceReference and ConnectionProperties. The data source must have exactly one of these elements.
Description
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.
Solution
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.
RE0038
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.
Description
This error occurs when an expression refers to a non-existent or incorrectly cased data source name.
Solution
Use the existing data source name within a report, ensure that the provided data source exists in the DataSource element in a RDL file.
RE0039
The type of the data source has not been specified.
Description
This error occurs when the report’s data source type is empty.
Solution
Data source type must not be empty, type must be Shared or Embedded.
RE0040
The data set {1} refers to the data source “{3}”, which does not exist.
Description
This error occurs when a dataset references a data source that is not defined in the report.
Solution
Use the existing data source name within a report, ensure that the provided data source exists in the DataSource element in a RDL file.
RE0041
More than one data source in the report has the name {1}. Data source names must be unique within a report.
Description
This error occurs when duplicate names are used for different data sources in the same report.
Solution
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.
RE0042
One or more data source credentials required to run the report have not been specified.
Description
This error appears when secure data sources require authentication, but credentials are missing.
Solution
Specify the credentials to preview the report.
RE0043
Error during processing of the ConnectString expression of data source {0}.
Description
This error occurs when the ConnectString expression for a data source is incorrect or invalid.
Solution
Specify the valid connection string for the data source element in a report definition.
RE0044
Enter a user name and password to access the data source:
Description
This prompt is shown when the data source is protected and requires user credentials, but none were supplied.
Solution
Provide the user name and password to access and retrieve the data from the data source.
RE0045
Data cannot be retrieved for ‘{1}’ dataset, Error Detail: ‘{4}’
Description
This error occurs when the report viewer fails to retrieve data for the specified dataset due to permission issues or connectivity problems.
Solution
Ensure that permission is granted to create/access the data source.
RE0046
Cannot impersonate user for data source ‘{0}‘.
Description
This error occurs when impersonation is attempted with invalid or missing credentials, or the hosting environment doesn’t support impersonation.
RE0047
Cannot create command for data source ‘{0}‘.
Description
This error occurs when a command object cannot be created for the given data source.
RE0048
Failed to commit transaction for data source ‘{0}‘.
Description
This error occurs when the report’s attempt to commit a database transaction fails, possibly due to a connection error or database issue.
RE0049
Failed to roll back transaction for data source ‘{0}‘.
Description
This error occurs when a transaction rollback operation fails, typically due to connection loss or internal server/database failure.
RE0050
Failed to close connection for data source ‘{0}‘.
Description
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.
RE0051
The data source ‘{0}’ uses a custom data processing extension that cannot be accessed.
Description
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.
Solution
Make sure that the custom data extension used in a data source exists and is accessible.
RE0052
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.
Description
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.
Solution
Use the existing data source within a report and ensure that the provided data source exists in the DataSources global collection.
RE0053
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.
Description
This error occurs when a dataset query parameter improperly attempts to access or evaluate a data source object.
Solution
Modify the expression in the query parameter value that references the data source global collection in a report.
RE0054
The expression used for the language of ‘{1}’ refers to a data source. Data sources cannot be used in report language expressions.
Description
This error occurs when the Language property of the report attempts to derive its value from a data source, which is not allowed.
Solution
Modify the expression in the Report.Language property that references the data source global collection in a report.
RE0055
A {2} expression used for the report parameter {1} refers to a data source. Data sources cannot be used in report parameter expressions.
Description
This error occurs when a report parameter expression attempts to use the data source collection, which is not valid in that context.
Solution
Modify the expression in the ReportParameter RDL element if it references the data source global collection in a report.
RE0056
The {2} expression for the {0} {1} refers to a data source. Data sources cannot be used in page headers or footers.
Description
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.
Solution
Modify the expression in the PageHeader and PageFooter RDL elements if it references the data source global collection in a report.
RE0057
More than one report parameter in the report has the name {1}. Report parameter names must be unique within a report.
Description
This error occurs when two or more report parameters share the same name, causing conflicts in reference and evaluation.
Solution
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.
RE0058
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.
Description
Even though parameter names may technically differ by case, case-insensitive environments can lead to ambiguity or runtime conflicts.
Solution
Provide a unique ReportParameter name. Ensure that the parameter name is different, including case.
RE0059
{1} is not a valid {0} name. Parameter names must be greater than 0 and less than or equal to {3} characters.
Description
This error occurs when the parameter name is either empty or exceeds the maximum allowed length (typically 256 characters).
Solution
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.
RE0060
A parameter in the {0} {1} has the name {3}. Parameter names must be CLS-compliant identifiers.
Description
This error indicates that a parameter name contains invalid characters or formatting. It must follow CLS (Common Language Specification) naming rules.
Solution
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.
RE0061
More than one parameter in the {0} {1} has the name {3}. Parameter names must be unique within a {0}.
Description
This error occurs when duplicate parameter names exist within the same context (Example: multiple parameters with the same name in the ReportParameters collection).
Solution
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.
RE0062
A {2} expression used for the report parameter {1} refers to a field. Fields cannot be used in report parameter expressions.
Description
This error occurs when a report parameter expression references a Fields! collection, which is not accessible outside of a data region.
Solution
Modify the expression in the ReportParameter RDL element if it references Field from the Fields global collection in a report.
RE0063
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.
Description
This occurs when the default value is incorrectly configured—either both a static value and dataset reference are provided, or neither is provided.
Solution
Specify the default value of a ReportParameter as one of the following: None, specific value, data set value. None is the default value.
RE0064
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.
Description
This warning/error appears when multiple default values are set for a parameter that only accepts a single value.
Solution
Provide the single default specific value for ReportParameter when the parameter is Single-Values (Multivalue is set to false).
RE0065
The report parameter {1} is a multiple value parameter and accepts a null value. This is not allowed.
Description
Multi-value parameters cannot accept null values because null cannot be included in a selection of multiple values.
Solution
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.
RE0066
The report parameter {1} has multiple default values and is not a multiple value parameter.
Description
This error occurs when more than one default value is assigned to a parameter that is configured as single-valued.
Solution
ReportParameter contains multiple default values but Multivalue is not enabled. Set the Multivalue property value to true to use multiple default values.
RE0067
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.
Description
This occurs when valid values are improperly defined using both static entries (ParameterValues) and a dataset (DataSetReference) or none at all.
Solution
Specify the valid value of a ReportParameter as one of the following: None, specific value, data set value. None is the default value.
RE0068
The report parameter {1} valid values refers to a data set “{3}”, that does not exist.
Description
This error occurs when the DataSetReference for valid values points to a dataset that isn’t defined in the report.
Solution
Provide the valid data set name in the DataSetReference element when ValidValue for ReportParameter is specified from a data set.
RE0069
The parameter {1} has no default. A default is required for all non-nullable parameters that are defined as read-only.
Description
A read-only parameter that doesn’t allow null values must have a default value set, since the user cannot provide input.
Solution
Provide a default value for all non-nullable parameters.
RE0070
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.
Description
Non-nullable parameters that don’t prompt the user must be assigned a default value. Otherwise, the report cannot resolve the parameter value.
Solution
Specify a default value for all non-nullable parameters or ensure that valid value contains a ‘Null’ value.
RE0071
The report parameter {1} default value refers to a data set “{3}”, which does not exist.
Description
This error occurs when a report parameter’s default value references a dataset name that is not defined in the report.
Solution
Provide the valid data set name in the DataSetReference element when a default value for ReportParameter is specified from a data set.
RE0072
The report parameter {1} has a DefaultValue or a ValidValue that depends on the report parameter “{3}”. Forward dependencies are not valid.
Description
A forward dependency occurs when one report parameter depends on the value of another parameter that appears later in the evaluation order.
Solution
Remove the forward dependency of ReportParameter. Make sure that the dependent order of a parameter is correct.
RE0073
The value of parameter ‘{0}’ is not valid or null.
Description
The parameter has either not been provided a value or was given an invalid/null value that is not acceptable due to its constraints.
Solution
Add the valid value to ReportParameter
RE0074
A {2} expression used for the report parameter {1} refers to a parameter. Parameters cannot be used in report parameter expressions.
Description
This error occurs when a report parameter expression references another parameter, which is not supported in certain expression contexts.
Solution
RE0075
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.
Description
An expression references a report parameter that does not exist in the report definition, or the name is misspelled or has incorrect casing.
Solution
Modify the non-existing ReportParameter expression in the subreport or Drillthrough Parameters collection in a report with a valid parameter.
RE0076
One or more parameters required to run the report have not been specified.
Description
Required parameters were not supplied when attempting to render or preview the report.
Solution
Provide the valid value to ReportParameter while previewing the parent/child report.
RE0077
The {2} property of {0} {1} is false. However, the ‘{3}’ property contains a value that violates the {2} property condition.
Description
This error occurs when a parameter property setting (Example: AllowBlank=false) is violated by the provided value (Example: an empty string).
Solution
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.
RE0078
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}
Description
An error occurred while evaluating a parameter value that references a field in a dataset. The underlying dataset or field contains an error.
Solution
RE0079
Error during processing of {0} report parameter.
Description
A generic error occurred while processing the report parameter, typically due to an invalid expression, data type mismatch, or missing data.
Solution
RE0080
The property {2} of {0} {1} doesn’t have the expected type.
Description
The value assigned to a parameter or its property (Example: default value) does not match the expected data type defined in the report.
Solution
Specify the valid value or default value of ReportParameter with respect to its data type.
RE0081
Parameter validation failed. It is not possible to provide valid values for all parameters.
Description
Report parameter validation failed because not all parameters were supplied with valid or non-null values, making it impossible to execute the report.
RE0082
The value ‘{0}’ is invalid. Valid values are between ‘{1}’ and ‘{2}‘.
Description
The input value provided is outside the valid range defined for the parameter.
RE0083
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.
Description
An expression resulted in a numeric value that is too large to be represented as an Int32 data type.
Solution
Specify the value to report parameter with the correct format or else change the parameter type to Text to avoid casting errors.
RE0084
The {0} {1} refers to an invalid {2} {3}.
Description
A reference in the report points to an invalid or non-existent element such as a DataSet, ReportItem, or Parameter.
Solution
Specify the valid DataSetName property of an element, ensure that the data set name exists in the DataSets global collection.
RE0085
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.
Description
A field name in the dataset exceeds the allowed length or is missing.
Solution
Provide the valid name in ‘Name’ property of Field element, name length must be greater than zero or less than 256 characters.
RE0086
A field in the data set {4} has the name {3}. Field names must be CLS-compliant identifiers.
Description
The field name in the dataset is not a CLS-compliant identifier.
Solution
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.
RE0087
The data input collection null or empty for the data set : ‘{0}’ is used in the report.
Description
The dataset used in the report has no input data or is null.
Solution
Provide data set inputs to preview the report in ReportViewer.
RE0088
The data value input is not supplied for the data set ‘{0}‘.
Description
No value was supplied for a dataset required by the report.
Solution
Provide data set values to the DataSet element to preview the report in ReportViewer.
RE0089
The value input is not a supported data type for the data set ‘{0}‘.
Description
The input data type for the dataset is unsupported.
Solution
Reporting controls support the following types, so provide input in any one of the following formats:
IEnumerable
System.Data.DataTable
System.Data.Dataset
RE0090
The {0} {1} must define either a Query or a SharedDataSetReference, but not both.
Description
A dataset cannot define both a Query and a SharedDataSetReference.
Solution
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.
RE0091
The report parameter {1} uses the field {3} in a data set reference, but the data set {4} does not contain that field.
Description
A report parameter references a field in a dataset, but the field does not exist in that dataset.
Solution
Use the existing data set reference ‘Field’ in ReportParameter.
RE0092
The data set {0} refers to a shared data set “{1}”, which is not available.
Description
The dataset refers to a shared dataset that is not available or not published on the report server.
Solution
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.
RE0093
The shared data set definition is not valid. Details: {3}
Description
The shared dataset definition is invalid due to an internal error.
Solution
Provide the valid data set definition, make sure that SharedDataSet is accessible.
RE0094
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.
Description
An expression references a dataset that does not exist or has a case-sensitive mismatch.
Solution
Use the existing data source name within a report, ensure that the provided data source exists in the DataSource element in a RDL file.
RE0095
The shared data set definition is not valid.
Description
The shared dataset definition is not valid due to incorrect syntax or schema violation.
Solution
SharedDataset definition is not valid, provide the definition as per schema standards.
RE0096
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.
Description
The dataset references a shared data source that is not yet published on the server.
Solution
Publish the data source to ReportServer to set as DataSourceReference in DataSource element.
RE0097
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.
Description
An expression refers to a dataset that does not exist in the report.
Solution
Use the existing data set within a report, ensure that the provided data set exists in the DataSets global collection.
RE0098
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.
Description
The report references a shared dataset that is not published.
Solution
Publish the data set to ReportServer to make the set a SharedDataSetReference in the DataSet element.
RE0099
The {0} ‘{1}’ specifies zero fields.
Description
The dataset defines no fields, making it unusable in the report.
Solution
Add the fields to the DataSet element in a report definition.
RE0100
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.
Description
A field in the dataset is defined with both DataField and Value properties, or neither, which is invalid.
Solution
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.
RE0101
More than one field in the data set {4} has the name {3}. Field names must be unique within a data set.
Description
This occurs when two or more fields in a dataset are assigned the same name, which causes ambiguity during report processing.
Solution
Ensure that the Field element contains a unique name attribute in Dataset. Modify the data set fields with unique names.
RE0102
The {0} ‘{1}’ contains a definition for the {2} ‘{3}’. This field is missing from the returned result set from the data source.
Description
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.
Solution
Add the missing field in the Dataset element. Example: Field name used in a report is missing Stored Procedure.
RE0103
The {0} ‘{1}’ specifies a database collation name that is not valid: {3}.
Description
The collation name provided in the dataset or data source is not recognized by the database engine.
Solution
Provide the valid database collation name.
RE0104
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}.
Description
The data extension (For example: SQL, Oracle) returned a collation culture name that is not valid or supported.
Solution
Provide the valid database collation culture name.
RE0105
Error during processing of the CommandText expression of data set ‘{0}’.
Description
The SQL query or expression used in the dataset’s CommandText is invalid or improperly formatted.
Solution
Provide the valid command text expression in the Dataset element of the report definition.
RE0106
Query execution failed for data set ‘{0}‘.
Description
The dataset query could not be executed, possibly due to permission issues, syntax errors, or connection problems.
Solution
Ensure that permission is granted to execute or retrieve the values of a data set.
RE0107
The query returned no rows for the data set. The expression therefore evaluates to null.
Description
The dataset query executed successfully but returned no data, causing expressions to evaluate to null.
Solution
Make sure that values used in expression are not null. Also ensure that rows of data are returned from the data set.
RE0108
The expression used for the parameter ‘{1}’ in the data set ‘{3}’ refers to a field. Fields cannot be used in query parameter expressions.
Description
A query parameter is incorrectly referencing a field from the dataset, which is not allowed.
Solution
Modify the value expression of a query parameter that references data set fields in a report.
RE0109
One or more parameters required to run the shared data set have not been specified.
Description
One or more parameters needed to execute the shared dataset were not provided.
Solution
Specify the value to the query parameter while executing the shared data set query.
RE0110
Cannot create a data reader for dataset ‘{0}‘.
Description
The system failed to initialize a data reader, possibly due to connection or configuration issues.
RE0111
Cannot create query parameter for dataset ‘{0}‘.
Description
The system encountered an error while creating a query parameter, possibly due to invalid definitions.
RE0112
Cannot read a data field for the dataset {0}.
Description
A field expected in the dataset could not be read, possibly due to schema mismatch or missing data.
RE0113
The {0} ‘{1}’ contains a definition for the {2} ‘{3}’. The data extension returned an error during reading the field. {4}
Description
The data extension encountered an error while reading a specific field.
RE0114
The {0} ‘{1}’ contains a definition for the {2} ‘{3}({4})’. The data extension returned an error during reading the field property. {5}
Description
The data extension failed to read a property (For Example: data type, size) of a field.
RE0115
Cannot read the next data row for the dataset {0}.
Description
An error occurred while attempting to read the next row of data from the dataset.
RE0116
Cannot set the command text for dataset ‘{0}‘.
Description
The system was unable to assign the SQL command text to the dataset.
RE0117
Cannot set the command type for dataset ‘{0}‘.
Description
The dataset command type (For Example: Text, StoredProcedure) could not be set.
RE0118
Cannot set the query timeout for dataset ‘{0}‘.
Description
The system failed to apply the specified timeout setting for the dataset query.
RE0119
Cannot set the transaction for dataset ‘{0}‘.
Description
The dataset could not be associated with a transaction, possibly due to configuration issues.
RE0120
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.
Description
An aggregate function that specifies a dataset scope contains another aggregate, which is not permitted.
RE0121
Cannot read IsAggregationField for a data field for the dataset {0}.
Description
The system failed to determine whether a field is used in an aggregation, possibly due to a corrupted or incomplete dataset definition.
RE0122
The {0} ‘{1}’ contains a definition for the {2} ‘{3}’. The data type for this field is not supported.
Description
A field in the dataset uses a data type that is not supported by the reporting engine or data extension.
RE0123
The {2} expression for the {0} ‘{1}’ refers to a dataset. Datasets cannot be used in page headers or footers.
Description
Expressions in page headers or footers cannot reference datasets because these sections are processed before data is retrieved.
RE0124
The expression used for the parameter ‘{1}’ in the dataset ‘{3}’ refers to a dataset. Datasets cannot be used in query parameter expressions.
Description
Query parameters cannot reference datasets, as datasets are not yet available when parameters are evaluated.
RE0125
The expression used for the language of ‘{1}’ refers to a dataset. Datasets cannot be used in report language expressions.
Description
The report language setting cannot be dynamically set using dataset fields or expressions.
RE0126
A {2} expression used for the report parameter ‘{1}’ refers to a dataset. Datasets cannot be used in report parameter expressions.
Description
Report parameters cannot reference datasets, as parameters are evaluated before datasets are processed.
RE0127
The {2} expression for the {0} ‘{1}’ refers to the global variable RenderFormat, which is not valid for this type of report item expression.
Description
The RenderFormat global variable is used in an expression where it is not supported, such as in certain report items.
RE0128
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.
Description
Expressions in headers or footers can only reference a single report item to avoid ambiguity during rendering.
RE0129
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.
Description
The expression references a non-existent or incorrectly cased item in the Globals collection.
Solution
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.
RE0130
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.
Description
The expression references a parameter that does not exist or is incorrectly cased in the Parameters collection.
Solution
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.
RE0131
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.
Description
The expression references a report item that does not exist, is misspelled, or is outside the current grouping scope.
Solution
Specify the valid variables in the expression in the report definition. The names must match items, groups, or data sets in the report.
RE0132
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.
Description
These global variables are only valid in page headers or footers and cannot be used in the report body.
Solution
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.
RE0133
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.
Description
These global variables cannot be used within aggregate functions that specify a dataset scope in headers or footers.
Solution
Remove or modify the expression in the PageSection or PageHeaderFooter. It contains the OverallPageNumber or OverallTotalPages global collection as scope aggregate.
RE0134
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.
Description
These global variables are only valid in page headers or footers and cannot be used in the report body.
Solution
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.
RE0135
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.
Description
These global variables cannot be used within dataset-scoped aggregates in headers or footers.
Solution
Remove or modify the expression that exists in the PageSection or PageHeaderFooter and contains the PageNumber or TotalPages global collection as scope aggregate.
RE0136
A group expression for the {0} ‘{1}’ refers to a report item. Report items cannot be used in group expressions.
Description
Group expressions must be based on fields or parameters, not report items.
Solution
Remove or modify the group expression (Group.GroupExpressions) that references the ReportItems global collection.
RE0137
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.
Description
Report items cannot be used as arguments in Lookup or LookupSet functions for destination or result expressions.
Solution
Remove or modify the Lookup or LookupSet expression that references the ReportItems global collection in the resultant argument.
RE0138
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.
Description
Query parameters cannot reference report items, as report items are not available at query execution time.
Solution
Remove or modify the QueryParameter value expression that references the ReportItems global collection.
RE0139
The expression used for the language of ‘{1}’ refers to a report item. Report items cannot be used in report language expressions.
Description
The report language setting cannot be dynamically set using report items.
Solution
Remove or modify the Report.Language value expression that references the ReportItems global collection.
RE0140
A {2} expression used for the report parameter ‘{1}’ refers to a report item. Report items cannot be used in report parameter expressions.
Description
Report parameters cannot reference report items, as parameters are evaluated before report items are processed.
Solution
Remove or modify the expression that references the ReportItems global collection within the ReportParameter element.
RE0141
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.
Description
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.
Solution
Remove or modify the expression in the PageSection or PageHeaderFooter that contains the ReportItems global collection as scope aggregate.
RE0142
A sort expression for the {0} ‘{1}’ refers to a report item. Report items cannot be used in sort expressions.
Description
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.
Solution
Remove or modify the expression that references the ReportItems global collection within the UserSort.SortExpression or SortExpression.Value element.
RE0143
The {2} value expression used for the language of ‘{1}’ refers to a report item. Variable values cannot be used in report language expressions.
Description
The language of a report cannot be dynamically set using report items, as these are not available at the time the language is evaluated.
Solution
Remove or modify the expression that refers to the report item via the ReportItems global collection within the Variable.Value element.
RE0144
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.
Description
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.
Solution
Use the existing report item in an expression that is referenced through the ReportItems global collection.
RE0145
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.
Description
Expressions in page headers or footers can only reference report items that exist within the same ReportSection.
Solution
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.
RE0146
The expression used for the calculated field ‘{1}’ includes a variable reference. Variable values cannot be used in calculated field expressions.
Description
Variables cannot be used in calculated field expressions because fields are evaluated in a different context than variables.
Solution
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.
RE0147
A sort expression for the {0} ‘{1}’ includes a variable reference. Variable values cannot be used in data row sort expressions.
Description
Variables cannot be used in sort expressions for data regions like Tablix, Chart, or GaugePanel, as sorting is evaluated before variables are processed.
Solution
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.
RE0148
A group expression for the {0} ‘{1}’ includes a variable reference. Variable values cannot be used in group expressions.
Description
Group expressions must be based on fields or parameters. Variables are not allowed because they are not evaluated in the grouping context.
Solution
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.
RE0149
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.
Description
The Previous function cannot use variables in its expression argument, as it relies on row context which variables do not support.
Solution
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.
RE0150
The expression used for the parameter ‘{1}’ in the dataset ‘{3}’ includes a variable reference. Variable values cannot be used in query parameter expressions.
Description
Variables cannot be used in query parameter expressions because parameters are evaluated before variables are initialized.
Solution
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.
RE0151
The expression used for the language of ‘{1}’ includes a variable reference. Variable values cannot be used in report language expressions.
Description
This error indicates that a report language setting is incorrectly using a variable. Language expressions must be static and cannot depend on runtime variables.
Solution
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.
RE0152
The {2} expression used for the report parameter ‘{1}’ includes a variable reference. Variable values cannot be used in report parameter expressions.
Description
A report parameter expression incorrectly references a variable. Such expressions should not include variable dependencies.
Solution
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.
RE0153
The {2} expression for the {0} ‘{1}’ refers to a field. Fields cannot be used in page headers or footers.
Description
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.
Solution
Remove or modify the field expression in PageSection or PageHeaderFooter that refers to Field via the Fields global collection.
RE0154
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.
Description
An aggregate function with a scope parameter is used in a header or footer, which is not permitted.
Solution
Remove or modify the expression in PageHeaderFooter that refers to the aggregate function as scope.
RE0155
A {2} for the {0} ‘{1}’ uses the aggregate function RunningValue. RunningValue cannot be used in filters.
Description
The RunningValue function is used in a filter, which is invalid. RunningValue is not supported in filter expressions.
Solution
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.
RE0156
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}.
Description
A filter value uses an unsupported data type for a specified operator.
Solution
Specify the valid data type for the filter value expression. Supported data types are: Text, Integer, Date Time, Boolean, Float.
RE0157
A {2} for the {0} ‘{1}’ includes an aggregate function. Aggregate functions cannot be used in dataset filters or data region filters.
Description
An aggregate function is incorrectly used in a dataset or data region filter.
Solution
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.
RE0158
Failed to evaluate the {2} of the {0} ‘{1}
Description
Evaluation of a component (For example: expression or filter) failed, but further details are unspecified.
RE0159
Failed to evaluate the {2} of the {0} ‘{1}’. It references a dataset field which has an error: {3}
Description
Evaluation failed due to an error in a referenced dataset field.
RE0160
A {2} for the {0} ‘{1}’ refers to a report item. Report items cannot be used in filters.
Description
A report item is referenced in a filter, which is not allowed.
Solution
Remove or modify the expression that refers to report items via the ReportItems global collection within the Filter.FilterExpression or Filter.FilterValues element.
RE0161
A filter expression for the {0} ‘{1}’ includes a variable reference. Variable values cannot be used in {0} filter expressions.
Description
This error occurs when a filter expression includes a variable reference from the Variables global collection, which is not allowed in report filter expressions.
Solution
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.
RE0162
The dependent assembly ‘{0}’ is missing to export the report into required format.
Description
This error is raised when a required dependent assembly is missing for exporting the report into the specified format.
RE0163
More than one report item in the report has the name ‘{1}’. Report item names must be unique within a report.
Description
This error indicates that multiple report items in a report have the same name, which must be unique.
Solution
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.
RE0164
The {0} ‘{1}’ is invalid. The value for the {2} property is missing.
Description
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.
Solution
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.
RE0165
More than one {2} in the {0} ‘{1}’ has the name ‘{3}’. {2} names must be unique within a {0}.
Description
This error arises when multiple items within a container, like a report or group, share the same name which should be unique.
Solution
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.
RE0166
The value of the {2} property for the {0} ‘{1}’ is negative. Negative sizes are not allowed.
Description
This occurs when a size-related property in a report item is specified as a negative value, which is not allowed.
Solution
Specify a non-negative value in the Size element in the report definition.
RE0167
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.
Description
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.
Solution
Provide the Visibility ToggleItem element within the same scope in a report definition.
RE0168
The {0} ‘{1}’ contains CustomProperties. The CustomProperty({3}) is missing a {2} element, which is mandatory.
Description
This error is reported when a required element for a custom property is missing, making it incomplete.
Solution
Specify a name attribute of CustomProperty. Custom property names are mandatory and the attribute should not be empty.
RE0169
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.
Description
This indicates unsupported bookmarks used in page headers or footers that certain renderers do not handle.
Solution
Remove the Bookmark property specified in a PageSection or PageHeaderFooter element.
RE0170
The object ‘{0}’ does not exist in the collection.
Description
This error is triggered when an object does not exist in the specified collection.
RE0171
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.
Description
This error happens when a text box in a header or footer incorrectly uses an element that is not supported in those sections.
Solution
Specify the UserSort Textbox element within the scope.
RE0172
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.
Description
This is triggered when an action in a report item is configured with multiple elements like Hyperlink, BookmarkLink, or Drillthrough rather than just one.
Solution
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.
RE0173
The {0} ‘{1}’ has multiple actions. Action label property is required.
Description
This error indicates that an action label property is missing for report items that have multiple actions.
Solution
Remove the multiple action or specify the label for each action and provide valid action label.
RE0174
The {2} expression for the {0} ‘{1}’ includes the function CountRows. CountRows cannot be used in page headers or footers.
Description
This error is raised by using the CountRows function in page headers or footers, where it is not permitted.
RE0175
The {2} for the {0} ‘{1}’ is not valid. A {2} can not be an empty string or just white space.
Description
This arises when a property is an empty string or just whitespace, which is not valid for certain report elements.
Solution
Provide a value for the ReportName property of a Subreport or Drillthrough element. It should not be empty.
RE0176
The {2} for the {0} ‘{1}’ is not valid. Item names cannot contain the following reserved characters {3}.
Description
This warns against invalid characters in report item names which should not include reserved characters.
Solution
Remove the invalid or special character(s) in a name of a report.
RE0177
The {2} for the {0} ‘{1}’ is not valid.
Description
This error signifies that a report item contains invalid or special characters that are not supported in its name.
Solution
Remove the invalid or special character(s) for URI in name of report.
RE0178
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:
Description
This occurs when a URL in a report uses a schema that is not among the supported ones like http, https, ftp, etc.
Solution
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.
RE0179
The {0} ‘{1}’ has the URL “{3}” as one of its properties. URLs in reports must begin with one of the following prefixes: {4}.
Description
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.
Solution
Specify the valid URL in an Image.Value element. URL must begin with http://, https://, ftp://,mailto:, or news:.
RE0180
The URL {0} has an invalid schema. URLs in reports may only use http://, https://, ftp://, file:, mailto: or news:
Description
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
Solution
Specify the valid and supported URL in the report. URL must begin with http://, https://, ftp://,mailto:, or news:.
RE0181
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.
Description
This error indicates that the endpoint calculations for line items result in a negative value, which is not permissible.
Solution
Specify non-negative values for the Left and Width elements of a line report item in a report definition.
RE0182
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.
Description
This signals a negative endpoint value for top plus height calculations of a line item.
Solution
Specify non-negative values for the Top and Height elements of a line report item in a report definition.
RE0183
The {0} ‘{1}’ has a Toggle. Toggle is not allowed in page headers or footers.
Description
This error arises when a toggle function is improperly placed in page headers or footers.
RE0184
The SortItemId is invalid. It must be a positive integer and has to be existing.
Description
This points to an invalid SortItemId, which must be existing and a positive integer.
RE0185
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.
Description
Indicates an invalid scope for a report element, requiring it be a current, peer, or ancestor scope.
RE0186
The {0} ‘{1}’ contains an invalid {4}. The {2} element is not allowed if {3} is omitted.
Description
Flags the inclusion of an element when a required accompanying element is omitted.
RE0187
The {0} ‘{1}’ has an invalid {2} ‘{3}‘. The scope cannot be a grouping that has a domain scope defined.
Description
A component references a scope that is defined across multiple domains or contexts, which is not allowed for certain operations.
RE0188
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}.
Description
A detail-level scope (that is one without grouping) is being used where a named scope is required.
RE0189
The {2} expression for the {0} ‘{1}’ is invalid (it is an empty string).
Description
This specifies that an expression for a report component is not valid because it results in an empty string.
RE0190
The {2} for the {0} ‘{1}’ is invalid. Details: {3}
Description
An expression is invalid due to a specific issue, which is detailed in the accompanying message.
RE0191
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.
Description
Highlights that a nested aggregate expression has an incorrect scope that does not match the requirements for proper scoping.
Solution
Specify the valid scope in an expression parameter of the nested aggregate function.
RE0192
The {2} expression for the {0} ‘{1}’ has a nested aggregate that specifies a dataset scope. Inner aggregates cannot specify a dataset scope.
Description
A nested operation references a dataset-level scope, which is not allowed.
Solution
Remove the data set name specified in the expression parameter of the nested aggregate function.
RE0193
The {2} expression for the {0} ‘{1}’ has an inner aggregate that specifies the recursive flag. Nested aggregates cannot specify the recursive flag.
Description
A nested operation includes a recursive flag, which is not supported in this context.
Solution
Remove the recursive parameter specified in the expression argument of the nested aggregate function.
RE0194
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.
Description
Highlights inaccuracies with the use of specific function flags within aggregate expressions.
Solution
Remove the First, Last, Previous, RowNumber, RunningValue, or Aggregate functions specified in the recursive function.
RE0195
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.
Description
This error highlights an issue with a nested aggregate present within a filter expression, which is not allowed.
Solution
Remove the nested aggregate function specified in the Filter expression value.
RE0196
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.
Description
Points out the invalid use of a nested aggregate function inside a group variable expression.
Solution
Remove the nested aggregate function specified in the Group.Variables expression value.
RE0197
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.
Description
Occurs when a nested aggregate is incorrectly used in a header or footer expression.
Solution
Remove the nested aggregate function specified in the report page header or page footer expression parameter.
RE0198
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.
Description
Indicates that a nested aggregate lacks the required scope specification in complex report items like tablix cells.
Solution
Specify the scope parameter for the aggregate function. Aggregate functions in an expression must contain a scope parameter.
RE0199
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.
Description
Flags improper utilization of mixed or incorrect scope in nested aggregate functions.
Solution
Specify the unique scope for the nested aggregate expression. The scope of an aggregate and axis, row group, or column group must be same.
RE0200
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.
Description
This error warns against employing nested aggregates within Lookup expressions, which is not supported.
Solution
Remove the nested aggregate function in a Lookup, LookupSet, MultiLookup source parameter expression, in which a miscellaneous function exists inside the aggregate function.
RE0201
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.
Description
The expression for the specified item uses an aggregate function within another aggregate function. This nesting is not allowed.
Solution
Remove the nested aggregate function in an expression parameter of another aggregate function.
RE0202
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.
Description
The expression for the specified item contains a Lookup or LookupSet function within another Lookup or LookupSet function. Nesting lookup functions is not allowed.
Solution
Remove the multiple specified look-up functions. Look-up functions should not contain another look-up function (Lookup, LookupSet, MultiLookup).
RE0203
The item in the Lookups collection was not found. References to the Lookups collection in an expression are not supported.
Description
An item in the Lookups collection was not found. References to the Lookups collection in expressions are not supported.
RE0204
A {2} for the {0} ‘{1}’ uses the aggregate function Previous. Previous cannot be used in filters.
Description
The expression for the specified filter uses the Previous aggregate function, which is not allowed in filters.
Solution
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.
RE0205
A group expression for the {0} ‘{1}’ includes the aggregate function Previous. Previous cannot be used in group expressions.
Description
The group expression for the specified item includes the Previous aggregate function, which is not allowed in group expressions.
Solution
Remove or modify the Group.GroupExpressions that refers to the Previous aggregate function. Group expressions must not contain the Previous aggregate function.
RE0206
The {2} expression for the {0} ‘{1}’ includes the aggregate function Previous. Previous cannot be used in page headers or footers.
Description
The expression for the specified item includes the Previous aggregate function, which is not allowed in page headers or footers.
Solution
Remove or modify the Previous aggregate expression in PageHeaderFooter. Reports’ page header and footer must not contain the Previous function.
RE0207
The expression used for the parameter ‘{1}’ in the dataset ‘{3}’ uses the aggregate function Previous. Previous cannot be used in query parameter expressions.
Description
The expression for the specified query parameter uses the Previous aggregate function, which is not allowed in query parameter expressions.
Solution
Remove or modify the QueryParameter value expression that refers to the Previous aggregate function. Query parameter expressions must not contain the Previous function.
RE0208
The expression used for the language of ‘{1}’ uses the aggregate function Previous. Previous cannot be used in report language expressions.
Description
The expression for the report language uses the Previous aggregate function, which is not allowed in report language expressions.
Solution
Remove or modify the Report.Language value expression that refers to the Previous aggregate function. Report language expressions must not contain the Previous function.
RE0209
A {2} expression used for the report parameter ‘{1}’ uses the aggregate function Previous. Previous cannot be used in report parameter expressions.
Description
The expression for the specified report parameter uses the Previous aggregate function, which is not allowed in report parameter expressions.
Solution
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.
RE0210
A sort expression for the {0} ‘{1}’ uses the aggregate function Previous. Previous cannot be used in sort expressions.
Description
The sort expression for the specified item uses the Previous aggregate function, which is not allowed in sort expressions.
Solution
Remove or modify the expression that refers to the Previous aggregate function within the UserSort.SortExpression or SortExpression.Value element.
RE0211
The {2} value expression for the {0} ‘{1}’ uses the aggregate function Previous. Previous cannot be used in variable value expressions.
Description
The value expression for the specified variable uses the Previous aggregate function, which is not allowed in variable value expressions.
Solution
Remove or modify the expression that refers to the Previous aggregate function within the Variable.Value element.
RE0212
The {2} expression for the {0} ‘{1}’ uses a Previous function in an outer aggregate. Previous functions cannot be specified as nested aggregates.
Description
The expression for the specified item uses a Previous function within another aggregate function, which is not allowed.
Solution
Remove or modify the expression that contains a nested Previous aggregate function.
RE0213
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.
Description
The expression for the specified item contains the Previous function within the argument of another Previous function, which is not allowed.
Solution
Remove or modify the expression that contains multiple Previous functions in the expression parameter of another Previous aggregate function.
RE0214
A {2} for the {0} ‘{1}’ uses the function RowNumber. RowNumber cannot be used in filters.
Description
The expression for the specified filter uses the RowNumber function, which is not allowed in filters.
Solution
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.
RE0215
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.
Description
The expression for the specified item contains the RowNumber function within a Lookup or LookupSet function, which is not allowed.
Solution
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.
RE0216
The {2} expression for the {0} ‘{1}’ uses the function RowNumber. RowNumber cannot be used in page headers or footers.
Description
The expression for the specified item uses the RowNumber function, which is not allowed in page headers or footers.
Solution
Remove or modify the RowNumber aggregate expression in PageHeaderFooter. Report page header or footer must not contain RowNumber function.
RE0217
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.
Description
The expression for the specified item contains the RowNumber function within the argument of a Previous function, which is not allowed.
Solution
Remove or modify the expression parameter of the Previous aggregate function. Previous aggregate functions must not contain the RowNumber function.
RE0218
The expression used for the parameter ‘{1}’ in the dataset ‘{3}’ includes the function RowNumber. RowNumber cannot be used in query parameter expressions.
Description
The expression for the specified query parameter uses the RowNumber function, which is not allowed in query parameter expressions.
Solution
Remove or modify the QueryParameter value expression that refers to the RowNumber aggregate function. Query parameter expressions must not contain RowNumber functions.
RE0219
The expression used for the language of ‘{1}’ uses the function RowNumber. RowNumber cannot be used in report language expressions.
Description
The expression for the report language uses the RowNumber function, which is not allowed in report language expressions.
Solution
Remove or modify the Report.Language value expression that refers to the RowNumber aggregate function. Report language expressions must not contain RowNumber functions.
RE0220
A report parameter expression for the {0} ‘{1}’ uses the function RowNumber. RowNumber cannot be used in report parameter expressions.
Description
The expression for the specified report parameter uses the RowNumber function, which is not allowed in report parameter expressions.
Solution
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.
RE0221
A sort expression for the {0} ‘{1}’ uses the function RowNumber. RowNumber cannot be used in sort expressions.
Description
The sort expression for the specified item uses the RowNumber function, which is not allowed in sort expressions.
Solution
Remove or modify the expression that refers to the RowNumber aggregate function within the UserSort.SortExpression or SortExpression.Value element.
RE0222
The {2} value expression for the {0} ‘{1}’ uses the function RowNumber. RowNumber cannot be used in variable value expressions.
Description
The value expression for the specified item uses the RowNumber function, which is not allowed in variable value expressions.
Solution
Remove or modify the expression that refers to the RowNumber aggregate function within the Variable.Value element.
RE0223
The {2} expression for the {0} ‘{1}’ uses a RunningValue function in an outer aggregateRunningValue functions cannot be specified as nested aggregates.
Description
The expression for the specified item uses a RunningValue function within another aggregate function. RunningValue functions cannot be nested within other aggregates.
Solution
Remove or modify the expression that contains a nested RunningValue aggregate function.
RE0224
A group expression for the {0} ‘{1}’ includes the aggregate function RunningValue. RunningValue cannot be used in group expressions.
Description
The group expression for the specified item includes the RunningValue function, which is not allowed in group expressions.
Solution
Remove or modify the Group.GroupExpressions that refers to the RunningValue aggregate function. Group expressions must not contain the RunningValue aggregate function.
RE0225
The {2} expression for the {0} ‘{1}’ includes the aggregate function RunningValue. RunningValue cannot be used in page headers or footers.
Description
The expression for the specified item includes the RunningValue function, which is not allowed in page headers or footers.
Solution
Remove or modify the RunningValue aggregate expression in PageHeaderFooter. Report page headers and footers must not contain the RunningValue function.
RE0226
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.
Description
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.
Solution
Remove or modify the expression parameter of the Previous aggregate function. The Previous aggregate function must not contain the RunningValue function.
RE0227
The expression used for the parameter ‘{1}’ in the dataset ‘{3}’ uses the aggregate function RunningValue. RunningValue cannot be used in query parameter expressions.
Description
The expression for the specified query parameter uses the RunningValue function, which is not allowed in query parameter expressions.
Solution
Remove or modify the QueryParameter value expression that refers to the RunningValue aggregate function. Query parameter expressions must not contain the RunningValue function.
RE0228
The expression used for the language of ‘{1}’ uses the aggregate function RunningValue. RunningValue cannot be used in report language expressions.
Description
The expression for the report language uses the RunningValue function, which is not allowed in report language expressions.
Solution
Remove or modify the Report.Language value expression that refers to the RunningValue aggregate function. Report language expressions must not contain the RunningValue function.
RE0229
A {2} expression used for the report parameter ‘{1}’ uses the aggregate function RunningValue. RunningValue cannot be used in report parameter expressions.
Description
The expression for the specified report parameter uses the RunningValue function, which is not allowed in report parameter expressions.
Solution
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.
RE0230
A sort expression for the {0} ‘{1}’ uses the aggregate function RunningValue. RunningValue cannot be used in sort expressions.
Description
The sort expression for the specified item uses the RunningValue function, which is not allowed in sort expressions.
Solution
Remove or modify the expression that refers to the RunningValue aggregate function within the UserSort.SortExpression or SortExpression.Value element.
RE0231
The {2} value expression for the {0} ‘{1}’ uses the aggregate function RunningValue. RunningValue cannot be used in variable value expressions.
Description
The value expression for the specified item uses the RunningValue function, which is not allowed in variable value expressions.
Solution
Remove or modify the expression that refers to the RunningValue aggregate function within the Variable.Value element.
RE0232
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.
Description
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.
Solution
Specify the chart subtype as Line to plot the series as a line. The default value is Auto.
RE0233
More than one {2} in the {0} ‘{1}’ has the name ‘{3}’. {2} names must be unique within a chart area.
Description
More than one specified element in the specified item has the same name. Element names must be unique within a chart area.
Solution
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.
RE0234
More than one chart column in the chart ‘{1}’ has the name ‘{3}’. Chart column names must be unique within a chart.
Description
More than one chart column in the specified chart has the same name. Chart column names must be unique within a chart.
Solution
Provide unique Name attributes for chart columns. Ensure that the Name properties of two or more columns are different within the same Chart element.
RE0235
More than one {2} in the {0} ‘{1}’ has the name ‘{3}’. {2} names must be unique within a derived series.
Description
More than one specified element in the specified item has the same name. Element names must be unique within a derived series.
Solution
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.
RE0236
More than one {2} in the {0} ‘{1}’ has the name ‘{3}’. {2} names must be unique within a legend custom item.
Description
More than one specified element in the specified item has the same name. Element names must be unique within a legend custom item.
Solution
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.
RE0237
More than one {2} in the {0} ‘{1}’ has the name ‘{3}’. {2} names must be unique within a legend.
Description
More than one specified element in the specified item has the same name. Element names must be unique within a legend.
Solution
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.
RE0238
An error has occurred during rendering of chart {0}.
Description
An error occurred during the rendering of the specified chart.
RE0239
The definition of the chart {0} is not valid.
Description
The definition of the specified chart is not valid.
Solution
Provide the valid report definition of the Chart report item element based on respective schema versions.
RE0240
The {0} ‘{1}’ contains an invalid {2} Name, ‘{3}‘. The name must be greater than 0 and less than or equal to {4} characters.
Description
The specified item contains an invalid name. The name must be greater than 0 and less than or equal to 256 characters.
Solution
Provide a valid chart axis name. The name should not be empty or longer than 256 characters.
RE0241
The {0} ‘{1}’ contains an invalid {2} Name, ‘{3}‘. The name must be CLS-Compliant.
Description
The specified item contains an invalid name. The name must be CLS-compliant.
Solution
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.
RE0242
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.
Description
A chart column in the specified chart has a name that must be greater than 0 and less than or equal to 256 characters.
Solution
Provide a valid chart column name. The name should not be empty or longer than 256 characters.
RE0243
A chart column in the chart ‘{1}’ has the name ‘{3}’. Chart column names must be CLS-compliant identifiers.
Description
A chart column in the specified chart has a name that must be CLS-compliant.
Solution
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.
RE0244
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}.
Description
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.
Solution
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.
RE0245
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.
Description
The specified item has an element at a certain index with an invalid name. The name must be a constant.
RE0246
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.
Description
The DataPoint in the specified item has a name that cannot be null and must be unique within the DataValues collection for the DataPoint.
Solution
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.
RE0247
The {0} ‘{1}’ has both StaticCategories and StaticSeries. A pie or doughnut chart can have StaticCategories or StaticSeries, but not both.
Description
The specified item has both StaticCategories and StaticSeries. A pie or doughnut chart can have StaticCategories or StaticSeries, but not both.
Solution
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
RE0248
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.
Description
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.
Solution
Remove or modify the Series or Category ChartMember element. Static chart members must not contain child members.
RE0249
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}).
Description
The specified item has an invalid element. The element has an invalid child element. Child elements of static elements must be dynamic.
RE0250
The {0} ‘{1}’ has an invalid {2}. The {2} has an invalid {3}, ‘{4}‘. Non-Static {3} elements must contain at least 1 {5}.
Description
The specified item has an invalid element. Non-static elements must contain at least one group expression.
Solution
Specify at least one group expression for the nonstatic ChartMember element.
RE0251
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.
Description
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.
Solution
Remove or modify the SeriesGrouping element that contains both StaticSeries and DynamicSeries.
RE0252
The ChartDerivedSeries in the {0} ‘{1}’ has an invalid {2} ‘{3}‘.
Description
The ChartDerivedSeries in the specified item has an invalid element.
RE0253
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.
Description
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.
RE0254
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.
Description
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.
RE0255
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.
Description
The scalar values property for the specified element is set to true. Scalar cannot be true if the axis has more than one grouping.
RE0256
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.
Description
The specified group is marked to create a page break for each group. Page breaks are not supported for the specified element in charts.
RE0257
The DataPoint {0} ‘{1}’ references an {2} Name, {3}, for a non-Value Axis for this chart.
Description
The DataPoint references an invalid name for a non-Value Axis for this chart.
RE0258
The scalar values property for the {2} of the {0} ‘{1}’ is set to true. This is not supported for a static grouping.
Description
The scalar values property for the specified element is set to true. This is not supported for a static grouping.
RE0259
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)).
Description
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.
RE0260
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.
Description
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.
RE0261
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.
Description
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.
RE0262
The {0} ‘{1}’ has an invalid subtype. The subtype ‘{4}’ is not allowed for a chart of type ‘{3}’.
Description
The specified item has an invalid subtype. The specified subtype is not allowed for the chart type.
RE0263
The {0} ‘{1}’ has multiple {2} elements. A chart may have at most one {2} element.
Description
The specified item has multiple elements. A chart may have at most one of the specified element.
RE0265
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.
Description
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.
RE0266
The DataPoint in {0} ‘{1}’ references a {2} Name, ‘{3}’, that does not exist in this chart.
Description
The DataPoint in the specified item references a name that does not exist in this chart.
RE0267
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}).
Description
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.
RE0268
The {2} element for the {0} ‘{1}’ can not contain a CustomReportItem element.
Description
The specified element cannot contain a CustomReportItem element.
Solution
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.
RE0269
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.
Description
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.
RE0270
The ‘{2}’ extension is not present in the configuration file. Therefore, the {0} ‘{1}’ shows empty space.
Description
The specified extension is not present in the configuration file. Therefore, the item shows empty space.
RE0271
The {0} ‘{1}’ is in the page header or footer. Custom reportitems cannot be used in page headers or footers.
Description
The specified item is in the page header or footer. Custom report items cannot be used in page headers or footers.
RE0272
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.
Description
The specified item contains a grouping level with both static and non-static groups. Multiple groups on the same level must be all static.
RE0273
The {0} ‘{1}’ has multiple static {2} groups at different grouping levels. A {0} may have at most one level of static groups.
Description
The specified item has multiple static groups at different grouping levels. A report item may have at most one level of static groups.
RE0274
An error has occurred during processing of the CustomReportItem ‘{0}’ with the ‘{1}’ extension.
Description
An error occurred during processing of the CustomReportItem with the specified extension.
RE0275
The {0} ‘{1}’ has multiple instances at runtime. All generated RenderItems must be not null. The {2} extension returned an empty RenderItem.
Description
The specified item has multiple instances at runtime. All generated RenderItems must be not null. The extension returned an empty RenderItem.
RE0276
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}’.
Description
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.
RE0277
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.
Description
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.
RE0278
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}.
Description
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.
RE0279
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.
Description
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.
RE0280
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.
Description
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.
RE0281
The ‘{2}’ extension returned an empty RenderItem for {0} ‘{1}’. RenderItems must be not null.
Description
The extension returned an empty RenderItem for the specified item. RenderItems must be not null.
RE0282
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}.
Description
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.
RE0283
The {0} ‘{1}’ has at least one static {2} group with a subgrouping. A static group cannot have subgroupings.
Description
The specified item has at least one static group with a subgrouping. A static group cannot have subgroupings.
RE0284
The {0} ‘{1}’ contains a {2} group with subtotal = true. Automatic subtotal calculation is not supported.
Description
The specified item contains a group with subtotal set to true. Automatic subtotal calculation is not supported.
RE0285
The {2} element for the {0} ‘{1}’ can only contain exactly one report item.
Description
The specified element can only contain exactly one report item. Solution: Ensure that the element contains only one report item.
RE0286
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.
Description
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.
Solution
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.
RE0287
A sort expression for the {0} ‘{1}’ includes an aggregate function. Aggregate functions cannot be used in data row sort expressions.
Description
A sort expression for the specified item includes an aggregate function. Aggregate functions cannot be used in data row sort expressions.
Solution
Remove or modify the expression Chart.SortExpressions, GaugePanel.SortExpressions, or Tablix.SortExpressions that refers to an aggregate function. SortExpressions must not contain aggregate functions.
RE0288
A group expression for the {0} ‘{1}’ includes an aggregate function. Aggregate functions cannot be used in group expressions.
Description
A group expression for the specified item includes an aggregate function. Aggregate functions cannot be used in group expressions.
Solution
Remove or modify the expression Group.GroupExpressions element that refers to any aggregate function. GroupExpressions must not contain aggregate functions.
RE0289
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.
Description
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.
Solution
Remove or modify the lookup function result expression that refers to an aggregate function. Lookup function result parameter expressions must not contain aggregate functions.
RE0290
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.
Description
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.
Solution
Remove or modify the Previous aggregate expression that refers to an aggregate expression. Previous functions must not contain aggregate functions.
RE0291
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.
Description
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.
Solution
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.
RE0292
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.
Description
The expression used for the report language includes an aggregate or lookup function. Aggregate and lookup functions cannot be used in report language expressions.
Solution
Remove or modify the Report.Language value expression that refers to the aggregate function. Report language expressions must not contain aggregate functions.
RE0293
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.
Description
The expression used for the report parameter includes an aggregate or lookup function. Aggregate and lookup functions cannot be used in report parameter expressions.
Solution
Remove or modify the expression that refers to an aggregate function within the ReportParameter element. Aggregate functions cannot be used in report parameter expressions.
RE0294
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.
Description
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.
Solution
Remove or modify the aggregate expression that refers to another aggregate in the same expression. Aggregate functions cannot be placed inside another aggregate function.
RE0295
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.
Description
The expression for the specified item uses an aggregate function with an expression that returned a data type not valid for the aggregate function.
RE0296
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.
Description
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.
RE0297
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.
Description
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.
RE0298
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.
Description
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.
RE0299
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.
Description
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.
Solution
Remove or modify the aggregate expression that refers to the ReportItems global collection. Functions used must exist in a defined scope.
RE0300
Filter, sort, and group expressions, and the set of lookup functions, do not support data type {2} in the {0} ‘{1}‘.
Description
Filter, sort, and group expressions, and the set of lookup functions, do not support the specified data type in the specified item.
RE0301
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.
Description
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.
RE0302
The {2} expression for the {0} {1} contains a direct or indirect reference to itself. Loops in expressions are not allowed.
Description
The expression contains a direct or indirect reference to itself, creating a loop. Loops in expressions are not allowed.
RE0303
The {2} expression for the {0} {1} contains a direct or indirect reference to itself. Loops in variable value expressions are not allowed.
Description
The expression contains a direct or indirect reference to itself. Loops in variable value expressions are not allowed.
RE0304
The {2} expression for the {0} contains a direct or indirect reference to itself. Loops in variable value expressions are not allowed.
Description
The expression contains a direct or indirect reference to itself. Loops in variable value expressions are not allowed.
RE0305
The {2} expression used in {0} {1} references a dataset field which contains an error: {3}
Description
The expression references a dataset field that contains an error.
RE0306
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.
Description
The expression specifies multiple incompatible scopes in the same aggregate expression. Nested aggregates must use compatible scopes.
RE0307
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.
Description
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.
Solution
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.
RE0308
The {2} expression used in {0} ‘{1}’ returned a data type that is not valid.
Description
The expression returned a data type that is not valid.
RE0309
The {0} ‘{1}’ has an invalid {2} “{3}”. The scope must be the current scope, or contained within the current scope.
Description
The scope specified is invalid. It must be the current scope or contained within the current scope.
RE0310
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.
Description
The scope specified is invalid. Both scopes must be within data regions that share the same dataset.
RE0311
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
Description
The value provided for the ImageData property is not valid.
Solution
Provide the valid ImageData for the external image.
RE0312
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.
Description
The aggregate function parameter used in the RunningValue expression is not valid.
Solution
Remove or modify the function parameter of the RunningValue expression that refers to the Aggregate, Previous, or CountRows functions.
RE0313
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.
Description
The inner aggregate function’s scope is not contained by or equal to the scope used in the Previous function.
RE0314
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}’.
Description
The scope parameter used in RunningValue, RowNumber, or Previous is not valid for the matrix.
RE0315
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}’.
Description
The scope parameter used in RunningValue, RowNumber, or Previous is not valid for the Tablix.
RE0316
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.
Description
The expression refers to a variable outside its allowed scope. Variable names must also use correct casing.
RE0317
A {2} for the {0} ‘{1}’ includes a Lookup function. Lookup functions cannot be used in expressions in a dataset filter.
Description
A Lookup function is used in a dataset filter, which is not allowed.
RE0318
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.
Description
The Lookup function received a data type that is not valid. It must be an RDL Variant type.
RE0319
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.
Description
A variable reference is used in a Lookup or LookupSet function argument, which is not allowed.
RE0320
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.
Description
An aggregate expression is used without a scope. A scope is required unless the report contains exactly one dataset.
RE0321
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.
Description
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.
RE0322
The chart ‘{1}’ has no data points. A chart requires at least one data point.
Description
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.
RE0323
The {0} ‘{1}’ contains an invalid {2}. The {2}({3}) is missing a {4} element, which is mandatory.
Description
A required element in a report definition (like a parameter or value) is missing, making the expression invalid.
RE0324
The {2} expression for the {0} ‘{1}’ is missing.
Description
A required expression (like a value or formula) is not provided.
Solution
Provide the value for the Variable.Value element in a report definition. The Variable.Value element must not be empty in the Variables collection.
RE0325
The expression referenced a non-existing field in the fields collection.
Description
The field name used in the expression doesn’t exist in the dataset.
RE0326
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.
Description
Field names are case-sensitive and must be within the current dataset scope.
RE0327
The {2} expression for the {0} ‘{1}’ contains an error: {3}
Description
A general error in the expression, such as syntax or logic issues.
RE0328
An unexpected error occurred while compiling expressions. Native compiler return value: ‘{3}’.
Description
A low-level error occurred during compilation, possibly due to malformed expressions.
RE0329
An unexpected error occurred in Report Processing.
Description
A generic error that may be caused by data issues, rendering problems, or configuration errors.
RE0330
An unexpected error occurred while evaluating the {2} expression for the {0} ‘{1}’.
Description
The expression failed during runtime evaluation.
RE0331
The {2} expression for the {0} ‘{1}’ has an incorrect number of parameters for the function ‘{3}’.
Description
Functions like Sum() or Avg() require specific parameters.
Solution
Specify the valid number of parameters to an aggregate expression. Functions used in an expression must contain required parameters. Example: =Sum()
RE0332
Please validate the provided expression ‘{0}’ in the element is correct.
Description
The expression may be syntactically or logically incorrect.
RE0333
There is a syntax error in the {2} expression for the {0} ‘{1}’: ) expected.
Description
A parenthesis is unmatched or misplaced.
Solution
Ensure the syntax of an expression is correct. An open parenthesis is not matched with a close parenthesis ).
RE0334
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.
Description
Fields must be referenced within the correct dataset or aggregate scope.
RE0335
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.
Description
In reports with multiple datasets, field references outside data regions must use aggregate functions with dataset scope.
RE0336
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.
Description
The scope must be a string constant matching a dataset name.
Solution
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.
RE0337
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.
Description
Aggregates must have a defined scope if {3} (like a data region or group) is not specified.
RE0338
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.
Description
Scope must be defined for items outside data regions.
RE0339
ReportSection.GetPageSections() was called for ReportSection {0} without calling ReportSection.SetPage(int, int). Call SetPage before calling GetPageSections.
Description
The report engine requires SetPage() to be called before retrieving page sections.
RE0340
The RichText {2} markup for the {0} ‘{1}’ failed to parse: {3}.
Description
The markup used in a RichText expression is invalid.
Solution
Provide the valid markup text in an expression to render the value.
RE0341
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.
Description
The specified size exceeds the maximum allowed (455 inches). This usually applies to dimensions like width, height, or margins.
RE0342
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.
Description
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.
RE0343
The {2} expression for the {0} ‘{1}’ contains an error: {3}
Description
A general expression error, such as invalid syntax, unsupported functions, or incorrect references.
RE0344
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.
Description
InScope and Level functions are not allowed within the expression parameter of the Previous function.
Solution
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.
RE0345
The {2} expression for the {0} ‘{1}’ uses the function “Count(*, scope)”. This function is no longer supported - use “CountRows(scope)” instead.
Description
The Count(*) syntax is no longer supported. Use CountRows(scope) instead.
RE0346
The {2} expression for the {0} ‘{1}’ uses the function “RunningValue(*, Count, scope)”. This function is no longer supported - use “RowNumber(scope)” instead.
Description
Replace with RowNumber(scope) for similar functionality.
RE0347
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.
Description
All names must be unique within a report.
Solution
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.
RE0348
An error has occurred during data evaluation of the GaugePanel ‘{0}‘.
Description
A runtime error occurred while processing data for a gauge panel. Could be due to invalid expressions or data issues.
RE0349
Minimum for Scale should be less than Maximum of GaugePanel ‘{0}‘.
Description
The scale range is invalid.
Solution
Make sure the minimum scale value of the gauge panel is less than the maximum scale value.
RE0350
StartValue for Range should be less than EndValue of GaugePanel ‘{0}‘.
Description
The range values are reversed.
Solution
Make sure the start range value of the gauge panel is less than the end range value.
RE0351
The {0} ‘{1}’ has an invalid {2}. The {2} contains a {3}, ‘{4}‘. Row {2} must be static.
Description
A row in a gauge must be static and cannot contain dynamic elements like groups.
RE0352
The {0} ‘{1}’ has an invalid {2}. Row GaugeMember cannot contain child members.
Description
Gauge rows must not have nested members.
RE0353
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.
Description
Page breaks are not allowed in gauge elements.
RE0354
GaugePanel has been initialized
Description
Informational message indicating the gauge panel setup has started.
RE0355
The {0} ‘{1}’ has an invalid {2}. Column GaugeMember cannot contain multiple child members.
Description
Gauge columns must have only one child member.
RE0356
Cannot automatically calculate the value for either the minimum or maximum of the state indicator ‘{3}’ in {0} ‘{1}‘.
Description
The system cannot infer the range. You must manually specify it.
RE0357
Minimum should be less than Maximum for state indicator ‘{1}’ in gauge panel ‘{0}‘.
Description
The range is invalid.
Solution
Make sure the minimum value of the state indicator gauge panel is less than the maximum scale value.
RE0358
{2} for state indicator ‘{3}’ in {0} ‘{1}’ must be specified.
Description
A required property (like StartValue, EndValue, or Color) is missing.
RE0359
The {2} ‘{3}’ for {0} ‘{1}’ does not exist.
Description
A referenced item (like a dataset, field, or group) is missing or misspelled.
RE0360
The {0} ‘{1}’ has an invalid {2}. The {2} contains a {3}, ‘{4}‘. Row {2} must be static.
Description
A row in a gauge must be static and cannot contain dynamic elements like groups.
RE0361
The {0} ‘{1}’ has an invalid {2}. Row MapMember cannot contain child members.
Description
In map controls, row members must be static. Nested or dynamic members are not allowed.
RE0362
Cannot load shapefile ‘{2}’ for the {0} ‘{1}’. If you are connected to a report server, check the log files for more information.
Description
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.
RE0363
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.
Description
The data type of the binding field must match the data type of the spatial field in the shapefile or spatial dataset.
RE0364
The layer ‘{2}’ in the {0} ‘{1}’ has a field name ‘{3}’ that is not valid.
Description
The field name does not exist or is misspelled. Field names are case-sensitive.
RE0365
The shapefile url ‘{2}’ for the {0} ‘{1}’ is not valid. Details: {3}
Description
The URL is incorrect or inaccessible. Details in {3} may provide more context (For Example: 404 error, permission denied).
RE0366
The spatial data for layer ‘{2}’ in the {0} ‘{1}’ is not valid. Specify spatial data that is data type SqlGeometry or SqlGeography.
Description
The spatial data must be of type SqlGeometry or SqlGeography.
RE0367
The layer ‘{2}’ in the {0} ‘{1}’ is not valid. Specify a valid value for the {3} property.
Description
A required property (like BindingField, ColorRule, etc.) is missing or incorrectly set.
RE0368
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.
Description
The map has a rendering limit. Extra spatial elements will not be displayed.
RE0369
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.
Description
Too many point elements (like markers) were added to the map, exceeding its display limit. Extra points are ignored to maintain performance.
RE0370
The {2} was already defined for {0} ‘{1}’.
Description
Duplicate property or element name. All names must be unique within the report.
RE0371
Cannot load shapefile ‘{3}’ into layer ‘{2}’ for the {0} ‘{1}’. Spatial element type does not match the layer type.
Description
The spatial element type in the shapefile does not match the expected type for the layer (For Example: polygon vs. point).
RE0372
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.
Description
A spatial element is matched to more than one group instance, which is not allowed.
RE0373
The type of the value field ‘{3}’ for layer ‘{2}’ in the {0} ‘{1}’ is not supported.
Description
The field used for color rules, size rules, or labels must be of a supported data type (For Example: numeric or string).
RE0374
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.
Description
Page breaks are not allowed in map elements.
RE0375
The {0} ‘{1}’ has an invalid {2}. Column MapMember cannot contain multiple child members.
Description
Map columns must have only one child member.
RE0376
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.
Description
The Union aggregate function can only be used on spatial data of the same type.
RE0377
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.
Description
The Union aggregate function can only be used on spatial data of the same type.
RE0378
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.
Description
Page breaks are not allowed in matrix column groups.
RE0379
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.
Description
Each row must align with the number of static columns. If no static columns exist, each row must have exactly one cell.
RE0380
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.
Description
The matrix structure is inconsistent. If no static columns are defined, only one MatrixColumn is allowed.
RE0381
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.
Description
The matrix structure is inconsistent. If no static rows are defined, the matrix must contain exactly one MatrixRow.
RE0382
A {2} in the matrix ‘{1}’ contains more than one report item. Each section in a matrix can contain at most one report item.
Description
Each matrix cell or section can only contain one report item (For Example a textbox or image).
RE0383
The {2} has an invalid number of number of {3}. {2} is limited to one {3}.
Description
The element {2} is limited to only one {3} (For Example: a matrix column group can only have one dynamic group).
RE0384
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’.
Description
The flag must be either Recursive or Simple when using aggregate functions like Sum.
RE0385
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
Description
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.
RE0386
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
Description
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.
RE0387
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
Description
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.
RE0388
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
Description
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.
RE0389
The {2} expression for the {0} ‘{1}’ has the value “{3}”, which is not a valid Boolean value.
Description
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.
RE0390
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
Description
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.
RE0391
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
Description
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.
RE0392
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2} for language ‘{4}’.
Description
The value provided is not valid in the context of the specified language or locale.
RE0393
The {0} ‘{1}’ has a CategoryGrouping with both or neither of the following: DynamicCategories and StaticCategories. CategoryGrouping must have exactly one of these elements.
Description
A CategoryGrouping must have exactly one of these elements, not both or none.
RE0394
The {2} expression for the {0} ‘{1}’ contains a colon or a line terminator. Colons and line terminators are not valid in expressions.
Description
Colons (:) and line breaks are not allowed in expressions.
Solution
Remove or modify the expression that contains a line terminator or colons.
RE0395
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
Description
Similar to RE0385–RE0391, this indicates an invalid property value.
RE0396
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.
Description
The expression must be a simple field reference (For Example: =Fields!Sales.Value).
RE0397
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.
Description
The scope must be a valid grouping or dataset name where all group expressions are simple field references or constants.
RE0398
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.
Description
Custom property names must be unique and not null.
Solution
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.
RE0399
The {2} expression for the {0} ‘{1}’ did not evaluate to an image.
Description
The expression must return a valid image (For Example a byte array or image URL).
RE0400
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
Description
Another instance of an invalid property value. Ensure the value matches the expected type and format.
RE0401
The {3} property for the {0} ‘{1}’ contains ‘{4}’. Field names must be greater than 0 and less than or equal to {5} characters.
Description
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.
RE0402
The {3} property for the {0} ‘{1}’ contains ‘{4}’, which is not a CLS-compliant identifier.
Description
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.
RE0403
The {2} expression for the {0} ‘{1}’ has the value “{3}”, which is not a valid DateTime value.
Description
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).
RE0404
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
Description
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.
RE0405
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
Description
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.
RE0406
The {2} expression for the {0} ‘{1}’ has the value “{3}”, which is not a valid Float value.
Description
The expression does not evaluate to a valid floating-point number. Ensure the value is numeric and formatted correctly (For Example: 123.45).
RE0407
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
Description
The value provided is not valid for the expected property type. Double-check the data type and format required for the property.
RE0408
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
Description
The value provided is not valid for the expected property type. Double-check the data type and format required for the property.
RE0409
The {2} value for the {0} ‘{1}’ is not valid. {3}
Description
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.
RE0410
The {2} expression for the {0} ‘{1}’ has the value “{3}”, which is not a valid integer value.
Description
The expression does not evaluate to a valid integer. Ensure the value is a whole number without decimals or invalid characters.
RE0411
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
Description
The value assigned to the property is not valid. Check the expected data type and constraints for the property.
RE0412
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
Description
The value assigned to the property is not valid. Check the expected data type and constraints for the property.
RE0413
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.
Description
The unit name used is not recognized. Valid unit names include mm, cm, in, pt, and pc. Use one of these standard units.
RE0414
The {2} expression for the {0} ‘{1}’ contains ‘Me.Value’. ‘Me.Value’ is not valid in the context of a {0}.
Description
The expression contains Me.Value, which is not valid in the current context. Avoid using Me.Value in expressions where it is not supported.
RE0415
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
Description
The value provided is not valid for the specified property. Ensure the value adheres to the expected format and constraints.
RE0416
{1}’ is not a valid {0} name. Names of objects must be greater than 0 and less than or equal to {3} characters.
Description
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.
RE0417
‘{1}’ is not a valid {0} name. Names of objects must be CLS-compliant identifiers.
Description
The object name is not CLS-compliant. Use only valid characters and avoid reserved keywords to ensure compatibility across .NET languages.
RE0418
The filter for {0} ‘{1}’ has an incorrect number of filter values for the operator. The operator ‘{3}’ requires exactly {4} filter value(s).
Description
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.
Solution
Remove or modify the filter value based on the filter operator. Example: Equal to operator must evaluate with one FilterValues.FilterValue
RE0419
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
Description
The value assigned to the property is not valid. Check the expected format or type and correct the value accordingly.
RE0420
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2} for language ‘{4}’.
Description
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.
RE0421
The {2} in the {0} ‘{1}’ has the name ‘{3}’, which is not a CLS-compliant identifier.
Description
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.
RE0422
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}.
Description
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.
RE0423
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
Description
The value assigned to the property is invalid. Ensure the value matches the expected data type and format for the property.
RE0424
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
Description
The value assigned to the property is invalid. Ensure the value matches the expected data type and format for the property.
RE0425
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
Description
The value assigned to the property is invalid. Ensure the value matches the expected data type and format for the property.
RE0426
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
Description
The value assigned to the property is invalid. Ensure the value matches the expected data type and format for the property.
RE0427
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
Description
The value assigned to the property is invalid. Ensure the value matches the expected data type and format for the property.
RE0428
The {0} ‘{1}’ has expression-based {2}. The sizes of the value and the label (multi-value) arrays have to be identical.
Description
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.
RE0429
The {0} ‘{1}’ has an invalid {2} element. The {2} element must contain at least one Variable.
Description
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.
RE0430
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
Description
The value provided is not valid for the property. Check the expected format and correct the value accordingly.
RE0431
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.
Description
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.
RE0432
The value of the {2} property for the {0} ‘{1}’ is “{3}”, which is not a valid {2}.
Description
The value assigned to the property is not valid. Ensure it matches the expected format and type.
RE0433
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’.
Description
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.
RE0434
Specify a valid URL. Report URLs may use only http://, https://, ftp://, file:, mailto:, or news:.
Description
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.
RE0435
The {2} is missing for the {0} ‘{1}’.
Description
A required property is missing. Ensure that all mandatory properties are defined for the specified element.
RE0436
The {0} ‘{1}’ has an invalid {2} “{3}”. The scope does not exist in the current report.
Description
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.
RE0437
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}.
Description
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.
RE0438
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.
Description
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.
RE0439
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}.
Description
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.
RE0440
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.
Description
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.
RE0441
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.
Description
The report server does not recognize or support the rendering format specified.
RE0442
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.
Description
The parent report may contain outdated elements like CustomReportItems from SSRS 2005 or failed to republish.
RE0443
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.
Description
This can occur due to outdated subreport elements or failed republishing.
RE0444
An error occurred while executing the subreport ‘{1}’ (Instance: {2}): {3}
Description
A runtime error occurred while executing the subreport.
RE0445
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.
Description
The subreport is missing or the path is incorrect.
Solution
Provide the valid subreport report name or make sure that the provided subreport exists in the mentioned location.
RE0446
Error: Subreport could not be shown.
Description
A generic error indicating the subreport failed to render.
RE0447
Data could not be retrieved for the subreport, ‘{0}’, located at: {1}. Data is only retrieved during the initial request or during snapshot creation.
Description
Data is only fetched during the initial request or snapshot creation.
RE0448
Data retrieval failed for the subreport, ‘{0}’, located at: {1}. Please check the log files for more information.
Description
The subreport failed to fetch data.
RE0449
One or more parameters were not specified for the subreport, ‘{0}’, located at: {1}.
Description
Required parameters were not provided.
RE0450
Warnings occurred while executing the subreport ‘{1}’.
Description
The subreport executed with warnings.
RE0451
The {0} ‘{1}’ has a detail member with inner members. Detail members can only contain static inner members.
Description
Detail members can only contain static inner members.
Solution
Remove or modify the detail group of the data region item. Detail members can only contain the static inner members.
RE0452
The {0} ‘{1}’ includes a group header with {2} set to true. This is not allowed on group headers or footers.
Description
Group headers/footers cannot have this property enabled.
RE0453
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}.
Description
A cell is incorrectly defined due to a span conflict.
RE0454
The {0} ‘{1}’ has an invalid {2}. The CellContents for this {2} is required if not covered by a span from another {2}.
Description
A cell is missing content and not covered by another span.
RE0455
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.
Description
Lists must have group expressions to contain data regions.
RE0456
The {0} ‘{1}’ is in the page header or footer. Data regions and subreports cannot be used in page headers or footers.
Description
Data regions and subreports are not allowed in headers/footers.
Solution
Remove or modify the Tablix, Chart, GaugePanel, or SubReport element within either a Page.PageHeader element or a Page.PageFooter element.
RE0457
The {0} ‘{1}’ is contained inside a table detail row. Data regions are not allowed inside a table detail row.
Description
Data regions are not allowed in table detail rows.
RE0458
The {0} ‘{1}’ is in the report body but the report has no dataset. Data regions are not allowed in reports without datasets.
Description
Data regions require a dataset.
Solution
Remove or modify the Tablix, GaugePanel, Chart, or SubReport instance within a report that does not have an associated data set.
RE0459
A {2} within the grouping ‘{4}’ in the {0} ‘{1}’ has a duplicate name, ‘{3}‘. {2} names must be unique within the report.
Description
Names must be unique within the report.
RE0460
The {0} ‘{1}’ has a {2} that contains hidden content. Either the ColSpan or RowSpan is set to 0.
Description
A cell is hidden due to invalid span settings.
RE0461
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.
Description
Each row in a Tablix must have the same number of cells. A mismatch causes rendering issues.
RE0462
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.
Description
Fixed columns must align with the corresponding cells in the row.
RE0463
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.
Description
This property is not allowed when Tablix.GroupBeforeRowHeaders is true.
RE0464
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.
Description
FixedData is incorrectly applied to an inner member.
RE0465
The {0} ‘{1}’ has an incorrectly set {2} properties within the {3}. All TablixMembers with FixedData set to true must be contiguous.
Description
Non-contiguous FixedData members cause layout issues.
RE0466
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.
Description
FixedData must be set on the first row if used on any row.
RE0467
The {0} ‘{1}’ has an incorrectly set {2} property on the opposite hierarchy, based on the property {3} of {0}.
Description
A property is misaligned with the hierarchy it’s intended for.
RE0468
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.
Description
Fixed columns must be adjacent and start from the edge.
RE0469
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.
Description
All descendants of a static or detail member must also be static or detail.
RE0470
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.
Description
The scope must match the immediate parent group.
RE0471
The {0} ‘{1}’ contains a non-static {2} group without grouping expression. Detail groups are not supported.
Description
Detail groups are not supported without a grouping expression.
RE0472
The grouping ‘{3}’ in the {0} ‘{1}’ has invalid {2} name ‘{4}‘.
Description
The name used is not valid for the specified grouping.
RE0473
The grouping ‘{3}’ in the {0} ‘{1}’ has DataSet ‘{4}’ as its domain scope. Only DataRegions and Grouping are allowed for {2}.
Description
Only DataRegions and Groupings can be used as domain scopes.
RE0474
The map grouping ‘{3}’ in the {0} ‘{1}’ has {2} ‘{4}‘. Domain scope will be ignored for map report item.
Description
Map items do not support domain scope.
RE0475
The grouping ‘{3}’ in the {0} ‘{1}’ has invalid {2} ‘{4}‘. Domain Scope is allowed only if it is an ancestor scope.
Description
The specified scope is not an ancestor of the grouping.
RE0476
The non leaf grouping ‘{3}’ in the {0} ‘{1}’ has {2} ‘{4}‘. Domain scope is only allowed for leaf grouping.
Description
Non-leaf groupings cannot have domain scope.
RE0477
The grouping ‘{3}’ in the {0} ‘{1}’ has {2} ‘{4}’ with Parent defined. Grouping with parent defined cannot be a domain scope target.
Description
Domain scope is not valid when a parent is defined.
RE0478
The detail grouping ‘{3}’ in the {0} ‘{1}’ has {2} ‘{4}‘. Domain scope is only allowed for non detail groups.
Description
Detail groups cannot be used as domain scope targets.
RE0479
The grouping ‘{3}’ in the {0} ‘{1}’ has {2} ‘{4}’ and Parent defined. Domain scope is only allowed if Parent is not defined.
Description
A group with a parent cannot be a domain scope.
RE0480
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.
Description
Grouping names must be between 1 and {3} characters.
Solution
Provide a valid grouping name. The name should not be empty or longer than 256 characters.
RE0481
A grouping in the {0} ‘{1}’ has the name ‘{3}’. Grouping names must be CLS-compliant identifiers.
Description
Grouping names must follow Common Language Specification (CLS) rules.
Solution
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 _.
RE0482
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.
Description
A grouping can only have a Parent if it has exactly one group expression.
RE0483
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.
Description
The name is either empty or exceeds the maximum allowed length.
Solution
Provide avalid grouping variable name. The name should not be empty or longer than 256 characters.
RE0484
A {2} within the grouping ‘{4}’ in the {0} ‘{1}’ has an invalid name, ‘{3}‘. {2} names must be CLS-compliant identifiers.
Description
The name is not CLS-compliant.
Solution
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 _.
RE0485
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.
Description
The value must be a group containing the current group or the dataset name.
RE0486
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.
Description
Inner DataRegions must match the outer DataRegion’s {2} property.
RE0487
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}‘)
Description
All dynamic elements must have the same {3} property value.
RE0488
The {0} ‘{1}’ has an invalid {2}. All {2} elements in a TablixColumnHierarchy must have the {3} property set to ‘{4}‘.
Description
All TablixMembers must have the {3} property set to ‘{4}‘.
Solution
Provide the TablixMember instance within the Tablix.TablixColumnHierarchy with a TablixMember.KeepWithGroup set to a value other than None.
RE0489
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}‘.
Description
Required property is missing for dynamic elements.
RE0490
A {2} in the matrix ‘{1}’ contains an invalid report item. Each subtotal in a matrix can contain at most one text box.
Description
Each subtotal cell can only contain one text box.
RE0491
The use of a Previous aggregate function in a matrix cell within matrix ‘{3}’ is not supported.
Description
This function cannot be used in matrix cells.
RE0492
The use of a Previous aggregate function in a TablixCell within Tablix ‘{3}’ is not supported.
Description
This function is not allowed in Tablix cells.
RE0493
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}‘)
Description
All dynamic elements must have the same {3} property value.
RE0494
The {0} ‘{1}’ has an invalid {2}. All {2} elements in a TablixColumnHierarchy must have the {3} property set to false.
Description
A {2} has an incorrect value for the {3} property.
Solution
Provide the TablixMember instance within the Tablix.TablixColumnHierarchy with a TablixMember.KeepWithGroup set to a value other than false.
RE0495
The {0} ‘{1}’ has a RepeatWith property. Data regions, subreports, and rectangles that contain a data region or subreport cannot have a RepeatWith.
Description
Data regions, subreports, or rectangles containing them cannot use RepeatWith.
RE0496
The {0} ‘{1}’ has a RowGrouping with both or neither of the following: DynamicRows and StaticRows. RowGrouping must have exactly one of these elements.
Description
Only one of these elements is allowed.
RE0497
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.
Description
If CellContents is missing, {2} must be 0; otherwise, it must be greater than 0.
RE0498
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.
Description
Cells cannot span across non-static siblings or unrelated dynamic members.
RE0499
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.
Description
The total ColSpan must equal the number of leaf columns.
RE0500
The {0} ‘{1}’ has an invalid TablixCell. The {2} of the TablixCell is invalid. The TablixCell can only span one row.
Description
TablixCells can only span a single row.
RE0501
The {2} of the {0} {1} has an invalid value. The {2} must be 0, if the TablixCornerCell has no CellContents, or greater than 0, if TablixCell has CellContents.
Description
If CellContents is empty, span must be 0. If content exists, span must be greater than 0.
RE0502
The {0} {1} has an invalid TablixCorner. The combined CellSpans of the TablixCornerCells within a particular row, row at index {3}, does not equal the number of TablixHierarchyRows with TablixMembers containing TablixHeaders.
Description
The total CellSpan in a corner row must equal the number of row hierarchy levels with headers.
RE0503
The {0} {1} has an invalid TablixCorner. The combined RowSpans of the TablixCornerCells within the Column at index: {3} does not equal the number of TablixHierarchyColumns with TablixMembers containing TablixHeaders.
Description
The total RowSpan in a corner column must equal the number of column hierarchy levels with headers.
RE0504
The {0} ‘{1}’ has an invalid TablixHeader. The {2} of the TablixHeader is invalid. The TablixHeader can only span one column.
Description
A TablixHeader must span only one column to maintain layout integrity.
RE0505
The {0} ‘{1}’ has an invalid TablixHeader. The {2} of the TablixHeader is invalid. The TablixHeader can only span one row.
Description
A TablixHeader must span only one row to ensure proper rendering.
RE0506
The {0} ‘{1}’ contains an invalid {2}. There is a {3} with an invalid {4} at level {5}. If there is a {3} with a {4} in this set of {3} siblings, then at least one {3} per sibling or their descendants must have a {3} with a {4}.
Description
If one sibling has a property (For example visibility), all siblings or their descendants must have it for consistency.
RE0507
The {2} in {0} ‘{1}’ contains an inconsistent {3} in one or more of the TablixMembers that contain headers for {7} {4}. {7} {4} has an expected total header size of {5} and an actual total header size of {6}. The total header size for each {7} created by the {2} must be equal.
Description
All TablixMembers must produce headers of equal total size across the hierarchy.
RE0508
The {2} expression for the {0} ‘{1}’ references a field outside an aggregate function. Value expressions in matrix cells should be aggregates, to allow for subtotaling.
Description
Expressions must use aggregate functions to support subtotaling.
RE0509
The {2} expression for the {0} ‘{1}’ references a field outside an aggregate function. Value expressions in Tablix cells should be aggregates, to allow for subtotaling.
Description
Value expressions must be aggregates to allow for subtotal calculations.
RE0510
The table ‘{1}’ has rows that contain a different number of cells than the number of the columns in the table (including cells that span more than one column).
Description
Each row must have the same number of cells as the table’s column count, accounting for spans.
RE0511
The {0} ‘{1}’ has an incorrect number of TablixCells. The number of TablixCells in a TablixRow must equal the number of innermost TablixMembers (TablixMembers with no submembers) in the TablixColumnHierarchy.
Description
Each TablixRow must contain cells equal to the number of innermost column hierarchy members.
RE0512
The {0} ‘{1}’ has an incorrect number of {2}. The number of {2} must equal the number of innermost TablixMembers (TablixMembers with no submembers) in the TablixColumnHierarchy.
Description
The number of specified elements must match the number of innermost column hierarchy members.
RE0513
The {0} ‘{1}’ has an incorrect number of {2}. The number of {2} within TablixCornerRow at index: {3} must equal the number of levels in the TablixRowHierarchy containing TablixHeaders.
Description
The number of cells must equal the number of row hierarchy levels with headers.
RE0514
The {0} ‘{1}’ has an incorrect number of {2}. The number of {2} must equal the number of levels in the TablixColumnHierarchy containing TablixHeaders.
Description
The number of cells must equal the number of column hierarchy levels with headers.
RE0515
The {0} ‘{1}’ has an incorrect number of TablixRows. The number of TablixRows must equal the number of innermost TablixMembers (TablixMembers with no submembers) in the TablixRowHierarchy.
Description
The number of rows must match the number of innermost row hierarchy members.
RE0516
The {0} ‘{1}’ includes a table header or column with {2} set to true. This is not allowed on data regions inside other data regions.
Description
RepeatOnNewPage is not allowed in data regions nested within other data regions.
RE0517
The {0} ‘{1}’ has a ColumnGrouping with both or neither of the following: DynamicColumns and StaticColumns. ColumnGrouping must have exactly one of these elements.
Description
Must contain either DynamicColumns or StaticColumns, not both or neither.
RE0518
The {0} ‘{1}’ has an invalid {2}. Group expressions are not allowed if Static = true.
Description
Group expressions are not allowed when Static = true.
RE0519
The {0} ‘{1}’ has no data cells. A {0} requires at least one {2} element.
Description
A Tablix must contain at least one data cell element.
RE0520
The {0} ‘{1}’ contains DataCells but no {2}. This is required when DataCells are present.
Description
When DataCells exist, corresponding structural elements (For example headers) must also be defined.
RE0521
The {0} ‘{1}’ has missing data groupings. A {0} requires at least one {2} element.
Description
A required data grouping is missing. You need at least one grouping to organize the data.
RE0522
A cell in the table ‘{1}’ contains more than one report item. Each cell in a table can contain at most one report item.
Description
A table cell has more than one item. Each cell should contain only one report item.
RE0523
The {0} ‘{1}’ has multiple {2} elements. A matrix may have at most one {2} element.
Description
Too many grouping elements in a matrix. Only one is allowed.
RE0524
The {2} expression for the {0} ‘{1}’ uses a First, Last or Previous aggregate in an outer aggregate. These aggregate functions cannot be specified as nested aggregates.
Description
You used First, Last, or Previous inside another aggregate. That’s not allowed.
RE0525
A grouping filter expression for the {0} ‘{1}’ uses aggregate function First, Last or Previous. These aggregate functions cannot be used in grouping filters.
Description
Grouping filters can’t use First, Last, or Previous functions.
Solution
Remove or modify a First, Last, or Previous aggregate function present within a grouping filter expression.
RE0526
A sort expression for the {0} ‘{1}’ uses aggregate function First, Last or Previous. These aggregate functions cannot be used in sort expressions.
Description
Sort expressions can’t use First, Last, or Previous functions.
Solution
Remove or modify an expression within a PageSection or PageHeaderFooter containing an aggregate function that does not have its Scope parameter specified.
RE0527
The {2} value expression for the {0} ‘{1}’ uses aggregate function First, Last or Previous. These aggregate functions cannot be used in variable value expressions.
Description
Variable expressions can’t use First, Last, or Previous functions.
Solution
Remove or modify a First, Last, or Previous aggregate function present within a variable value expression.
RE0528
The {0} ‘{1}’ contains a wrong number of DataCells per DataRow element. {2} DataCells per DataRow element are expected, because there must be as many DataCell elements as there are leaf-node DataGroupings (that is DataGrouping without sub-groupings).
Description
The number of data cells in a row doesn’t match the expected count based on groupings.
RE0529
The {0} ‘{1}’ contains a wrong number of DataRow elements. {2} DataRow elements are expected, because there must be as many DataRow elements as there are leaf-node DataGroupings (that is DataGrouping without sub-groupings).
Description
The number of data rows doesn’t match the expected count based on groupings.
RE0530
RunningValue or RowNumber functions used in the cells of the {0} ‘{1}’ refer to grouping scopes in both the columns and rows of the {0}. The scope parameters of all RunningValue and RowNumber functions within a {0} can refer to row grouping or column groupings, but not both.
Description
RunningValue or RowNumber functions refer to both row and column groupings. You must choose one.
RE0531
Previous, RunningValue or RowNumber aggregate functions used in the data cells of the {0} ‘{1}’ refer to grouping scopes in both the columns and rows of the {0}. The scope parameters of all Previous, RunningValue and RowNumber aggregate functions within a {0} can refer to row groupings or data column groupings, but not both.
Description
Previous, RunningValue, or RowNumber functions refer to both row and column scopes. Only one is allowed.
RE0532
The {0} ‘{1}’ is defined at the scope “{3}”, which is identical to the scope used as {2}. This interactive sort has no effect at runtime, since it sorts only the particular instance itself.
Description
Sorting is set on the same scope as the item itself. It won’t have any effect.
RE0533
The value of the {2} property for the {0} ‘{1}’ is ‘{3}’, which is not a valid {2}.
Description
An invalid value was set for a property. Check and correct it.
RE0534
An unexpected error occurred in Report Processing during deserialization: {0}.
Description
An unexpected error occurred while loading the report.
RE0535
Provide ReportServer information to get shared Datasource information
Description
Missing server info needed to access shared data sources.
RE0536
Provide ReportServer information to get shared Dataset information
Description
Missing server info needed to access shared datasets.
RE0537
The ReportServerUrl/ReportServerCredential is missing
Description
Server URL or login details are missing.
RE0538
The value for the DataSetName property is missing.
Description
Dataset name is not provided.
RE0539
Data regions are not allowed in reports without datasets.
Description
You can’t use data regions without a dataset.
RE0540
The report item has invalid expression : {0}
Description
An expression in the report is invalid and needs fixing.
RE0541
Provide ReportService information to retrieve the Report from server
Description
You need to provide ReportService details to access the report.
RE0542
Unsupported Expression: object expressions do not have complete support : ‘{0}’
Description
Some object expressions are not fully supported.
RE0543
DateAdd function should contain arguments
Description
You must provide all arguments for DateAdd to work.
RE0544
DateDiff function should contain arguments
Description
You must provide all arguments for DateDiff to work.
RE0545
Overload resolution failed because no accessible ‘{0}’ accepts this number of arguments
Description
The function {0} needs a different number of arguments.
RE0546
PaymentPeriod must be between 1 and numberOfPayments
Description
PaymentPeriod must be between 1 and the total number of payments.
RE0547
This implementation doesn’t handle zero interest rate
Description
The calculation method doesn’t handle 0% interest.
RE0548
A {0} expression for the ‘{1}’ has invalid Expression : {2}
Description
The expression {2} is not valid and needs correction.
RE0549
{1} is not a member in custom code
Description
The code is trying to use something that doesn’t exist.
RE0550
Unknown Error with Report Initialization, {1}
Description
Something went wrong while initializing the report.
RE0551
The ‘Aggregate’ function expression {0} specified in a report definition is not supported.
Description
The way it’s used in the report is not allowed.
RE0552
The ‘{1}’ parameter is missing a value
Description
You need to provide a value for this parameter.
RE0553
An error occurred during expression ‘{1}’ parsing.
Description
The expression is written incorrectly.
RE0554
Unhandled exception has occurred during expression ‘{1}’ parsing.
Description
Something went wrong during parsing.
RE0555
An error occurred during report item ‘{1}’ parsing.
Description
The item has issues that prevent it from being processed.
RE0556
Unhandled exception has occurred during report item ‘{1}’ parsing.
Description
Something went wrong during parsing.
RE0557
An error occurred during expression ‘{1}’ evaluating.
Description
The expression couldn’t be calculated properly.
RE0558
Unhandled exception has occurred during expression ‘{1}’ evaluating.
Description
Something went wrong during evaluation.
RE0559
An error occurred during report item ‘{1}’ evaluating.
Description
The report item couldn’t be processed correctly.
RE0560
Unhandled exception has occurred during report item ‘{1}’ evaluating.
Description
Something went wrong during evaluation.
RE0561
Unhandled exception has occurred during report item ‘{1}’ height layouting.
Description
Something went wrong during layout processing.
RE0562
Unhandled exception has occurred during report item ‘{1}’ Width layouting.
Description
Something went wrong during layout processing.
RE0563
An error occurred during report ‘{1}’ evaluating.
Description
The report failed to process correctly, possibly due to invalid expressions, missing data, or runtime issues.
RE0564
Unhandled exception has occurred during report ‘{1}’ evaluating.
Description
The report failed to process correctly, possibly due to invalid expressions, missing data, or runtime issues.
RE0565
An error occurred during parameter ‘{1}’ evaluating.
Description
The parameter couldn’t be calculated, possibly due to incorrect expressions, missing values, or unsupported references.
RE0566
Unhandled exception has occurred during parameter ‘{1}’ evaluating.
Description
The parameter couldn’t be calculated, possibly due to incorrect expressions, missing values, or unsupported references.
RE0567
An error occurred during data set ‘{1}’ processing.
Description
The dataset couldn’t be loaded or processed, possibly due to connection issues, invalid queries, or missing schema definitions.
RE0568
Unhandled exception has occurred during data set ‘{1}’ processing.
Description
The dataset couldn’t be loaded or processed, possibly due to connection issues, invalid queries, or missing schema definitions.
RE0569
Unhandled exception has occurred during report ‘{1}’ parsing.
Description
The report or item couldn’t be read or initialized properly, possibly due to corrupted definitions or unsupported formats.
RE0570
Unhandled exception has occurred during ‘{0}’ ‘{1}’ parsing.
Description
The report or item couldn’t be read or initialized properly, possibly due to corrupted definitions or unsupported formats.
RE0571
Unhandled exception has occurred during ‘{0}’ ‘{1}’ loading.
Description
The report or item couldn’t be read or initialized properly, possibly due to corrupted definitions or unsupported formats.
RE0572
Unhandled exception has occurred during ‘{1}’ retrieve.
Description
The system couldn’t access the requested report or item, possibly due to incorrect path, missing permissions, or server issues.
RE0573
Failed to retrieve the ‘{0}’ from the path ‘{1}’
Description
The system couldn’t access the requested report or item, possibly due to incorrect path, missing permissions, or server issues.
RE0574
Failed to retrieve the ‘{0}’
Description
The system couldn’t access the requested report or item, possibly due to incorrect path, missing permissions, or server issues.
RE0575
Unhandled exception has occurred during ‘{0}’ ‘{1}’ Export.
Description
Exporting the report failed, possibly due to unsupported formats, large data size, or rendering issues.
RE0576
The expression used for the parameter ‘{1}’ in the data set ‘{3}’ refers to a field. Fields cannot be used in parameter expressions.
Description
Parameters must be independent and cannot directly reference dataset fields.
Solution
Modify the expression of a parameter that references data set fields in a report.
RE0577
The {2} of the {1} scale should be within the range of (0-360)
Description
The value must be within the valid angular range, typically used in charts or gauges.
RE0578
The {2} of the {1} should be within the range of (0-1)
Description
This usually applies to normalized values like opacity, scale, or percentage.
RE0579
Unable to read values from the request body. Add the [FromBody] attribute to the Dictionary type parameter in the WEB API action method.
Description
The Dictionary parameter in the API method must be marked with [FromBody] to allow proper deserialization.
RE0591
The data range exceeded the threshold limit. Currently you have {0} number of records in {1}. ” + “Please reduce the record count for better optimization. (OR) ” + “If you like to proceed with max number of records please specify the max range in the properties which you prefer.
Description
The number of records is too high for optimal performance.
RE0592
Data exceeds the threshold limit.
Description
The number of records is too high for optimal performance.
RE0593
The column count range exceed the threshold limit. The threshold limit for this {1} is {0}. Currently you have {2} number of columns. ” + “Please reduce the column count for better optimization. (OR) ” + “If you like to proceed with max number of column please specify the {3} you prefer.
Description
The report has too many columns, which may affect performance.
RE0594
The row count range exceed the threshold limit. The threshold limit for this {1} is {0}. Currently you have {2} number of rows. ” + “Please reduce the row count for better optimization. (OR) ” + “If you like to proceed with max number of row please specify the {3} you prefer.
Description
The report has too many rows, which may affect performance.
RE0595
An error occurred during cumulative evaluation :{1}
Description
An issue occurred while calculating cumulative values, possibly due to incorrect expressions or data inconsistencies.
RE0597
Failed to convert the SVG image ‘{1}’ to PNG.
Description
The SVG file may be malformed or unsupported.
Solution
Make sure that the given image is in the proper SVG format.
RE0603
The tablix ‘{1}’ has an incorrectly set FixedData properties within the TablixColumnHierarchy. All TablixMembers with FixedData set to true must be contiguous.
Description
In a TablixColumnHierarchy, all members with FixedData = true must be placed next to each other.
RE0604
The tablix ‘{1}’ has an incorrectly set FixedData property. FixedData is not allowed to be set on row TablixMember, unless it is also set on the first row TablixMember.
Description
In a tablix, the FixedData property is used to keep certain rows or columns visible during scrolling. This property cannot be set on a row TablixMember unless it is also set on the first row TablixMember. This ensures consistent behavior and layout.
RE0605
The tablix ‘{1}’ has an incorrectly set FixedHeader property on the opposite hierarchy, based on the property ‘{2}’ of tablix.
Description
The FixedHeader property is meant to fix headers in either the row or column hierarchy. If it’s applied to the wrong hierarchy based on the tablix’s structure and the property {2}, it causes layout issues and is considered invalid.
RE0606
The chart ‘{1}’ has an invalid LogBase setting. The logarithmic base must be greater than or equal to 2.0.
Description
Logarithmic charts require a base value of 2.0 or higher. If the LogBase is set below 2.0, the chart cannot render correctly and will throw this error.
RE0580
Error occurred during report {0}.
Description
A general error happened while processing the report. This could be due to invalid data, broken expressions, or system-level failures.
RE0581
Unable to load Inner Reportitem of {0}.
Description
A nested or embedded report item (like a subreport or control) failed to load, possibly due to missing references or configuration issues.
RE0582
Error occurred while converting the {0}.
Description
The system failed to convert a report item or format, such as converting between image types, export formats, or data types.
RE0583
Error occurred while updating/getting the {0}.
Description
A problem occurred during data access or update operations, possibly due to permission issues, missing data, or connection errors.
RE0584
Error occurred while getting/creating the data from the {0} in expression engine/ReportingAggEngine.
Description
The report engine couldn’t process or generate data due to issues in the expression logic or aggregation rules.
RE0585
Unable to get the data/connection string from the {0} data provider.
Description
The report couldn’t connect to the specified data source, possibly due to missing credentials, incorrect configuration, or unsupported provider.
RE0587
Error occurred while mouse left button down event raised on {0} item.
Description
A user interaction triggered an error, possibly due to unsupported actions or missing event handlers in the report viewer.
RE0588
Error occurred while {0} event raised.
Description
A general event-related error occurred, such as during rendering, interaction, or data refresh.
RE0589
The data source ‘{0}’ uses a custom data processing {1} extension which cannot be null or empty. Please use a valid relative or absolute data extension.
Description
Custom data extensions must be properly defined. Null or empty values are not allowed and will prevent the report from accessing the data source.
RE0590
Error occurred during search text file deletion.
Description
The system couldn’t delete a temporary or cached file, possibly due to file locks, permission issues, or missing file paths.
RE0596
Error occurred while clearing the cache.
Description
The report engine failed to remove cached data, which may affect performance or data freshness.
RE0598
This report contains user-based information; therefore it cannot be cached.
Description
Caching is disabled to protect personalized or sensitive user information. Each user may see different data, so storing a shared version is not allowed.
RE0599
The datasource in this report requires user credentials, therefore it cannot be cached.
Description
Since the report depends on user authentication, caching is not allowed for security and privacy reasons.
RE0600
The Value of the shadowoffset property of the chart {0} is negative. Negative sizes are not allowed.
Description
Visual properties like shadow offset must be positive. Negative values are invalid and may cause rendering issues.
RE0601
Report processing was cancelled.
Description
The report execution was stopped manually or due to a timeout or system interruption.
RE0602
Export processing was cancelled.
Description
The export operation was interrupted or aborted before completion, possibly by the user or system.
RE0607
User-based On-Demand data processing is enabled in this report, therefore it cannot be cached.
Description
Since the report fetches data dynamically based on the user, caching is disabled to ensure accuracy and privacy.