This section provides a detailed explanation and solution to the respective problems in the Report Viewer for parsing and processing the report.
The source of the report definition has not been specified.
The Report Viewer will not render the report when either the report path or stream is not set, or the given path is incorrect.
Provide Report Server information to get shared data source information.
Report with a shared data source must contain the Report Server information and credentials that are provided to render in the Report Viewer.
Make sure that the credentials in the Report Server URL are not empty and ensure that the correct information is provided to the Report Viewer. For example, refer to the below code.
Viewer.ReportServerUrl = @"https://demos.boldreports.com/services/api/ReportViewer";
Viewer.ReportServerCredential = new System.Net.NetworkCredential("username", "password");An error occurred while sending a request to the reporting service.
Report will not be rendered when there is a problem while connecting or retrieving the data from the provided reporting service’s URL.
If not, start the reporting service from the desktop shortcut (for example: Start BoldReports in IIS) or from an installed location.
Installed location path: (C:\Program Files (x86)\Bold Reports\Enterprise Reporting\Utilities\DeployIIS)
The report definition has an invalid schema version.
Report definition should contain the supported schema version (for example, 2008) to render the report in the Report Viewer.
Make sure that the provided schema in your report definition is supported in the Report Viewer. Supported versions are 2008, 2010, and 2016.
The requested file or assembly was not found. It may have either moved or renamed.
Any of the assembly related to the report platform is missing at the installation location.
(C:\Program Files (x86)\Bold Reports\Report Designer) or reinstall the Report Designer application.(C:\Program Files (x86)\Bold Reports\Embedded Reporting\Assemblies) or reinstall the Report Platform SDK application.(C:\Program Files (x86)\Bold Reports\Enterprise Reporting\Utilities\DeployIIS) or reinstall the Report Server application.Note: Please contact Syncfusion® support if you cannot resolve the issue.
Expressions are not used within the scope.
Report Viewer encounters an error when an expression must be used outside the scope.
Provide a valid expression within the scope. Note: Detailed description with the line number and position is mentioned in the Report Viewer instance error dialog.
An error occurred during the local report processing. There is an error that occurred while rendering the custom code.
Report Viewer encounters an error when compiling the custom code used in the report.
Provide valid custom code in your report based on detailed information mentioned in the Report Viewer instance error dialog. Note: Custom code exists in report properties.
The Value property of an image report item contains an invalid value.
Report will not be rendered to the Report Viewer when you try to use invalid image data or a non-existing image in the report.
Ensure that the value provided to the image report item is specified properly, and make sure that the image is available.
The data source used in a report does not exist or not accessible.
Report will not be rendered in the Report Viewer when the data source used in a report does not exist or it is not accessible due to permission rights.
Ensure whether the data source in a report exists in the referred location.
Fields cannot be used in report parameter expressions.
Report Viewer does not render the report when the parameter contains field expressions and fields cannot be used in report parameter expressions.
Remove the field expressions used in parameter expressions.
Forward dependencies are not valid.
Report will not be rendered when there is an existence of forward dependencies between parameters.
Make sure to remove the forward dependencies in your report definition before previewing the report. Example: First Parameter depends on Dataset 1 and Dataset 2 depends on Second Parameter, and then it results in forward dependency. Note: Parameters are executed based on the order.
Please select a value for the report parameter.
Report parameters must be supplied with values if it is non-nullable while trying to preview the report in the Report Viewer.
Enter the value of the parameter in a parameter block when it is non-nullable or allow blank.
The expression that references the parameter is not valid and does not exist in the parameter collection or forward dependencies.
Report Viewer throws errors when you try to use a non-existing report parameter or with forward dependencies.
Make sure to use the parameters that exist report definition and avoid forward dependencies in the report. Note: Letters in the names of parameters should be in the correct case.
The value provided for the report parameter is not valid for its type.
The report will not be rendered by the Report Viewer when the specified value for the report parameter is irrespective of its type.
Provide an appropriate value for the report parameter based on its data type while rendering the report. Example: A parameter with an integer data type allows integer values, not float values.
Report item refers to an invalid DataSetName.
Report will not be rendered in the Report Viewer when a non-existing dataset is used in the report.
Collection class or data table input is needed.
To render the RDLC report in the Report Viewer, the report must have a collection class or data table input to rendering the report.
Make sure to provide dataset collection to render the report. Supported collections are IEnumerable, System.Data.DataTable, and System.Data.Dataset.
Report variable or group variable reference cannot be used in report parameter expressions.
Report Viewer does not render the report when the parameter contains group or report variables. Variable values cannot be used in report parameter expressions.
Remove the variable reference used in the parameter expressions.
An invalid operator is used in expression.
Report Viewer encounters an error if it contains an invalid operator in an expression.
Make sure to use appropriate and supported operators in the expression. Note: Detailed information is provided with the expression, and the report item name is mentioned in the Report Viewer instance error dialog.
Data region items are not allowed in reports without datasets to render in the Report Viewer.
Report Viewer will not render the report when the data region items does not refer to the dataset.
Make sure to provide the dataset name property value in your report definition. Note: Report will render when the report definition has a single dataset; When the dataset count is greater than one, you must specify the dataset name property value to data region items (Tablix, Chart, Gauge, etc..).
Toggle items must be text boxes that share the same scope, and they are not allowed in page headers or footers.
In our Report Viewer, toggle items must be shared within the same scope, and they are not allowed in page headers and page footers.
Provide toggle items in the report in the same scope, not from their page header or page footer. Example: If a report item in the page header contains a toggle item, then the referred toggle item should be in the header region.
A ReportName cannot be an empty string or just white space.
In SubReport item, the ReportName property value cannot be an empty or just white space.
Make sure that the ReportName property value for the subreport item is not empty.
Aggregate and lookup functions cannot be used in report parameter expressions.
The value expression is used for report parameter, it includes an aggregate or lookup function. Aggregate and lookup functions cannot be used in report parameter expressions.
Remove Aggregate and Lookup functions in your report parameter expressions.
Lookup function has an incorrect number of parameters.
Provided lookup function has an incorrect number of parameters in report definition.
Provide the correct number of arguments for lookup expressions in respective report item expressions and refer to the syntax of the lookup expressions.
ReportItem expressions can be referred only to fields within the current dataset.
ReportItem expressions can be referred only to fields within the current dataset. Make sure that the field expression is referred to the current dataset.
Provide current dataset fields for report item expression.
Note: Tablix report item with scope Dataset1 must contain the fields in the dataset1. If field expression specified in another dataset is required, then you should specify the scope.
Example: =First(Fields!Name.Value, "Dataset2")
Each dataset, data region, or grouping in the report has different name for their report item. Dataset, data region, and grouping names must be unique within a report.
Report item referred dataset, data region, and grouping names must be unique within a report.
Provide a unique dataset, data region, and grouping name for their report item in your report definition.
An error has occurred on the Report Server.
Specified reporting service encounters an error while rendering the report in the Report Viewer.
(C:\Program Files\Bold Reports\Enterprise Reporting\idp\web\Logs)The value expression for the TextRun contains a colon or a line terminator.
The Textbox report item value expression contains a colon or a line terminator. Colons and line terminators are not valid in expressions.
Remove colons and line terminator used in the specified report item expression.
Cannot load sub report.
Sub report cannot be loaded with an invalid name or report path.
The subreport cannot be found at the specified location.
Report will not be rendered in the Report Viewer when the report does not exist in the specified location.
Make sure that the report name or path is correct, and the report exists in the specified directory.
Subreport cannot be shown.
Report Viewer will not render the sub report without the ReportPath or ReportServerUrl.
Provide a subreport ReportPath or ReportServerUrl in your report.
The tablix has a detail member with inner members. Detail members contain only static inner members.
In the tablix report item, detail members contain only static inner members.
In the tablix report item, provide static inner members for their detail members.
The tablix report item has an invalid Tablix member in the column hierarchy, and the KeepTogether property is not set to None.
All tablix member elements in a TablixColumnHierarchy must have the KeepWithGroup property as None.
Set KeepWithGroup property as None in a TablixColumnHierarchy for all Tablix members in the tablix report item.
Report Deserialization failed.
An error occurred during the deserialization of the report definition.
Provide Report Server information to get shared dataset information.
Report with shared datasets must contain the Report Server information and credentials to render in the Report Viewer.
Make sure that the credentials in the Report Server URL are not empty and ensure that the correct information is provided to the Report Viewer.
Example: Viewer.ReportServerUrl = @"https://demos.boldreports.com/services/api/ReportViewer"; Viewer.ReportServerCredential = new System.Net.NetworkCredential("username", "password");
The ReportServerUrl or ReportServerCredential is missing.
Server report or server referred items used in the report will not be rendered in the Report Viewer without ReportServerUrl and ReportServerCredential.
Make sure that the ReportServerUrl and ReportServerCredential are not empty and provided with proper data and are accessible.
The value for the DataSetName property is missing.
Data region items are not allowed in reports without datasets to render in the Viewer.
Make sure to provide a dataset name property value in your report definition and ensure that the property value is not empty.
Provide dataset inputs for the report.
To render the RDLC report, you must add the data source collection in the Report Viewer if any dataset is used in the report.
Make sure to add the dataset to render the report in Report Viewer if dataset fields are used.
Example: Viewer.DataSources.Add("Dataset1", object collection of data)
Note: Here, name (“Dataset 1”) is the dataset name used in the report definition.
Invalid Expression
Report Viewer does not render the report when an invalid expression is used.
Provide valid expressions in the respective report item. Note: Detailed description with line number and position is mentioned in the Report Viewer instance error dialog.
Unsupported Expression
Provided expression does not support in the Report Viewer. Object expressions do not have complete support.
Please use supported expressions in the Report Viewer to render the report.
The DateAdd function should have arguments.
Report Viewer encounters an error if DateAdd function does not contain any arguments.
Provide arguments for DateAdd function in the respective report item expression and refer to the syntax of the DateAdd function.
Example: =DateAdd("d",3,Fields!BirthDate.Value)
The DateDiff function should contain arguments.
Report Viewer encounters an error if DateDiff function does not contain arguments in an expression.
Provide arguments for DateDiff function in the respective report item expression and refer to the syntax of the DateDiff function.
Example: =DateDiff("yyyy",Fields!BirthDate.Value,"1/1/2010")
PaymentPeriod must be between 1 and numberOfPayments.
Report Viewer encounters an error if the payment period does not fall within the range.
Provide payment period value between 1 and numberOfPayments.
This implementation does not handle zero interest rate.
Report is not rendered in the Report Viewer when it holds the zero interest rate.
Provide greater than 0 or less than 0 interest rate. Does not provide 0 value for their interest rate.
Invalid Expression
The expression used in the report is incorrect scope, syntax, or unsupported.
Ensure that the expression used in the report is correct with valid scope and syntax. Note: Detailed information of report item along with line number and position is mentioned in the Report Viewer instance error dialog.
Method name is not a member in custom code.
Evaluated method name is not a member in your custom code.
Provide a valid method name. Make sure that the provided method name is present in your custom code.
Parameter is missing a value.
Report Viewer will not render the report when the hidden parameter does not contain a value that is non-nullable.
Provide value to hidden parameters in your report definition before rendering the report.
Note: Hidden parameters must contain a default value, or it should be nullable.
The report path value cannot be null or empty.
This error occurs when the ReportPath property of the Report Viewer is not assigned a valid report definition path.
Provide the valid relative or absolute path location of the report in the ReportPath property. Example: reportViewer.ReportPath = ../ReportTemplate.rdl;
The path {0} specified for the report is not valid or not found.
This error indicates that the path assigned to ReportPath either points to a non-existent report or is incorrectly formatted.
Ensure the valid report path is specified in the ReportPath property or make sure that the specified report exists and is accessible in the provided location.
The {0} file input stream is null.
This error is thrown when attempting to load a report using a stream, but the stream provided is null.
Make sure that the provided file input stream is not empty/null.
Example: reportViewer.LoadReport(reportStream);
The stream input is not available for the report subreport {0}.
This occurs when a subreport is expected, but the stream for the subreport is missing or not supplied.
To load a subreport, make sure to set the stream input in the LoadSubreport definition.
Example: reportViewer.LoadSubreport(subReportName, subReportStream);
The report server URL specified is invalid.
This error occurs when the ReportServerUrl provided to the viewer is incorrect or unreachable.
Provide the valid report server URL of a report in the ReportServerUrl property to load the server report.
Example: reportViewer.ReportServerUrl = @'http://localhost/reportserver';
The credentials required to access the report server are not supplied.
This error occurs when the ReportServerUrl provided to the viewer is incorrect or unreachable.
Specify report server credentials in the report viewer to access the report server.
Example: reportViewer.ReportServerCredential = new NetworkCredential('userName', 'password');
The server report details have been given and the processing mode set to local incorrectly.
This occurs when the processing mode is set to Local but server-related settings like ReportServerUrl are also specified, which causes a conflict.
Ensure the provided processing mode is correct. ‘Remote’ for server report processing and ‘Local’ to process a local report.
Example:
reportViewer.ProcessingMode = ProcessingMode.Remote //For remote processing
reportViewer.ProcessingMode = ProcessingMode.Local //For local report processing.
The provided credentials are invalid to access the report server. Login failed for user ‘{0}‘.
This error indicates that the authentication credentials supplied to the report server are incorrect.
Make sure that the provided credentials are valid to access the report server.
Example: reportViewer.ReportServerCredential = new NetworkCredential('userName', 'password');
Failed to retrieve the {0} ‘{1}’ stream from the provided server details ‘{2}’
This error occurs when the Report Viewer cannot retrieve a resource (like a report or subreport) from the report server due to incorrect server configuration or missing files.
Provide the valid report server information (ReportServerURL, ReportServerCredential, ReportPath) to retrieve the report stream from server.
An error occurred in communicating to the reporting service.
This error is thrown when there is a network or configuration issue preventing the Report Viewer from connecting to the report server.
Verify that the report server is reachable and that correct details are provided. Also, ensure that firewalls or proxies are not blocking communication.
The report definition is not valid.
This error occurs when the report definition (.rdl/.rdlc file) is invalid or corrupted. It may happen if required elements are missing or incorrectly formatted in the XML schema.
Ensure that the provided report has a valid report definition. Example : Report element missing in .rdl file.
An unexpected error occurred in Report Processing during serialization: {0}.
This error occurs when the Report Viewer encounters an unexpected issue during the report processing or serialization stage, often caused by corrupt data or misconfigured objects in the report.
Review the provided exception message {0} for more insight. Validate all expressions and report objects. Also, confirm the report does not contain circular references or unsupported data types.
The report definition is not valid or has an unsupported element by this version of ReportDefinition schema. The report definition contains XML that is not well formed or the XML is not valid based on the Report Definition schema. Details: {0}
This error occurs when the report uses an unsupported ReportDefinition schema version or contains elements not recognized by the current Report Viewer.
Make sure that the provided schema in your report definition is supported in report viewer. Supported versions are 2008, 2010, and 2016.
The dependent assembly was not found. It may have been either moved or renamed.
The dependent assembly was not found. It may have been either moved or renamed.
Ensure that dependent assemblies of report viewer exist in the referenced location. Check whether the assembly is missing at the installed location. If you are loading the report from report
designer : (%ProgramData%/Syncfusion/Report Designer/ReportDesigner)
SDK : (%ProgramData%/Report Platform SDK/Assemblies)
ReportServer : (%ProgramData%/Report Server/ReportServer.Web\bin)
The expression used for the language of ‘{1}’ refers to a field. Fields cannot be used in report language expressions.
This error occurs when a field expression is incorrectly used in the reports Language property.
Make sure to avoid the usage of field expressions in report language expressions.
The number of columns specified for the report body is not valid. The number of columns must be between 1 and 100.
This error is thrown when the column count defined in the report body layout is outside the valid range.
Ensure that the number of columns in the rdl/rdlc report are in the range from 1 to 100.
The {0} {1} is in the page header or footer and has a {2}. {2} cannot be used by a {0} in the page header or footer.
This error occurs when unsupported items (like a tablix or chart) are placed inside page headers or footers.
Make sure that a designed report contains report items in valid regions. Data visualization items (Tablix, chart, gauge, map, sparkline, databar, indicator) cannot be used in page headers or footers.
The {0} ‘{1}’ contains a {2} with a duplicate name, ‘{3}‘. {2} names must be unique within the report.
This error is thrown when two or more report items share the same identifier, which must be unique.
Ensure that the report contains a unique report item or group name.
A {2} in the {0} ‘{1}’ has an invalid {2} name, ‘{3}‘. {2} names must be CLS-compliant identifiers.
This error occurs when a name assigned to a report item or variable violates Common Language Specification (CLS) naming rules.
Provide the report item, variable, or group name with a valid format. The name should not contain spaces, and it must begin with a letter followed by letters, numbers, or the underscore character.
A {2} in the {0} ‘{1}’ has an invalid {2} name, ‘{3}‘. {2} names must be greater than 0 and less than or equal to {4} characters.
This error is caused when the name of a report element (like a variable or group) is either empty or exceeds the allowed length.
Provide a valid variable name: the name should not be empty or longer than 256 characters.
The {2} expression for the {0} ‘{1}’ refers to the global variable Aggregates, which is not defined.
This error occurs when an expression in a report references a global variable or collection named Aggregates, which is either undefined or incorrectly used in the current scope.
Ensure that the expression contains valid global collection variant types.
The First, Last aggregate functions cannot be specified as nested aggregates.
This error occurs when First() or Last() functions are used inside other aggregate functions (like Sum(First(...))), which is not supported.
Remove the First, Last aggregate functions used in nested expressions.
The expression that references the variable ‘{0}’ does not exist in the Variables collection. Expressions can only refer to variables within the report scope or a containing grouping scope. Letters in the names of variables must use the correct case.
This error is triggered when a report expression refers to a variable that hasn’t been defined in the scope or has incorrect casing.
Specify the valid variables in an expression that exists in the report definition. The name must match an item/group/data set in a report.
There is an error on line {4} of custom code: {3}
This error occurs when the custom embedded code in the report fails to compile due to a syntax or runtime error.
Make sure that the provided custom code is compiled successfully without an error.
More than one class instance in the report has the name ‘{1}‘. Class instance names must be unique within a report.
This error occurs when multiple code class instances in the report share the same name.
Provide a unique class instance name and ensure that the InstanceNames of a two or more classes are different in a report.
Error in class instance declaration for class {1}: {3}
This error indicates a problem in the class instance declaration, such as incorrect syntax, invalid reference, or missing class in custom code.
Modify the class instance declaration and ensure there is no compile error.
Failed to load assembly. Details: {3}
This error is triggered when a required assembly (DLL) referenced in the report cannot be found or loaded.
Add the assemblies to the Assemblies API in the Report Viewer.
Error while loading code module: ‘{3}‘. Details: {4}
This error occurs when a report references a code module that is either missing, corrupted, or improperly referenced.
Ensure that elements of Report.CodeModule exist in a report to use in the expression.
The report references the code module {3}, which is not a trusted assembly.
This error indicates that the report tries to use a code module that is not whitelisted or trusted in the current environment.
Add the trusted assembly references in the code module.
The report contains an invalid embedded image name, {1}. Embedded image names must be greater than 0 and less than or equal to {3} characters.
This error occurs when the name assigned to an embedded image is missing or exceeds the allowed length.
Provide the valid name in the Name property of EmbeddedImage; name length must be greater than zero and fewer than 256 characters.
More than one embedded image in the report has the name {1}. Embedded image names must be unique within a report.
This error occurs when multiple embedded images share the same name, which must be unique within a report definition.
Provide a unique name in EmbeddedImage and ensure that the name properties of two or more EmbeddedImages are different within the same report.
The report contains an embedded image with an invalid name {1}. Embedded image names must be CLS-compliant identifiers.
This error is thrown when the image name does not follow Common Language Specification (CLS) rules.
Provide the name property of EmbeddedImage with a valid format. The name should not contain spaces, and it must begin with a letter followed by letters, numbers, or the underscore character.
The embedded image {1} contains invalid data. Embedded image data must be a base 64 encoded string.
This error indicates that the image data stored in the embedded image node is not valid Base64-encoded data.
Make sure that the embedded image data is in the proper format.
The value of the {2} property for the {0} {1} is “{3}”, which is not a valid {2}.
This error occurs when a report property (like MIMEType or Source) is assigned an invalid or unsupported value.
Use the existing embedded image within a report, ensure that the provided image exists in the Report.EmbeddedImages element in an RDL file.
The report contains an invalid data source with the name {1}. Data source names must be greater than 0 and less than or equal to {3} characters.
This error occurs when the Name property of a DataSource is missing or exceeds the allowed length.
Provide the valid name in the ‘Name’ property of DataSource. Name length must be greater than zero and fewer than 256 characters.
The report contains an invalid data source with the name {1}. Data source names must be CLS-compliant identifiers.
This error occurs when the data source name includes invalid characters or formatting that violates CLS (Common Language Specification) naming rules.
Specify the name property of DataSource with a valid format. The name should not contain spaces, and it must begin with a letter followed by letters, numbers, or the underscore character.
The data source {1} has both or neither of the following: DataSourceReference and ConnectionProperties. The data source must have exactly one of these elements.
This error occurs when a data source is not properly configured. It must either reference a shared data source or provide connection properties for an embedded one, but not both or neither.
Provide a valid data source. A data source with same name must contain one of the following items in a report:
DataSourceReference—Specifies for shared data source.
ConnectionProperties—Embedded for data source.
The expression that references the data source ‘{0}’ does not exist in the DataSource collection. Letters in the names of data sources must use the correct case.
This error occurs when an expression refers to a non-existent or incorrectly cased data source name.
Use the existing data source name within a report, ensure that the provided data source exists in the DataSource element in a RDL file.
The type of the data source has not been specified.
This error occurs when the report’s data source type is empty.
Data source type must not be empty, type must be Shared or Embedded.
The data set {1} refers to the data source “{3}”, which does not exist.
This error occurs when a dataset references a data source that is not defined in the report.
Use the existing data source name within a report, ensure that the provided data source exists in the DataSource element in a RDL file.
More than one data source in the report has the name {1}. Data source names must be unique within a report.
This error occurs when duplicate names are used for different data sources in the same report.
Provide a unique name attribute in DataSource and ensure that the name properties of two or more data sources are different within the same report.
One or more data source credentials required to run the report have not been specified.
This error appears when secure data sources require authentication, but credentials are missing.
Specify the credentials to preview the report.
Error during processing of the ConnectString expression of data source {0}.
This error occurs when the ConnectString expression for a data source is incorrect or invalid.
Specify the valid connection string for the data source element in a report definition.
Enter a user name and password to access the data source:
This prompt is shown when the data source is protected and requires user credentials, but none were supplied.
Provide the user name and password to access and retrieve the data from the data source.
Data cannot be retrieved for ‘{1}’ dataset, Error Detail: ‘{4}’
This error occurs when the report viewer fails to retrieve data for the specified dataset due to permission issues or connectivity problems.
Ensure that permission is granted to create/access the data source.
Cannot impersonate user for data source ‘{0}‘.
This error occurs when impersonation is attempted with invalid or missing credentials, or the hosting environment doesn’t support impersonation.
Cannot create command for data source ‘{0}‘.
This error occurs when a command object cannot be created for the given data source.
Failed to commit transaction for data source ‘{0}‘.
This error occurs when the report’s attempt to commit a database transaction fails, possibly due to a connection error or database issue.
Failed to roll back transaction for data source ‘{0}‘.
This error occurs when a transaction rollback operation fails, typically due to connection loss or internal server/database failure.
Failed to close connection for data source ‘{0}‘.
This error appears when the report viewer cannot close a data source connection, possibly due to a lingering process, open reader, or a connection issue.
The data source ‘{0}’ uses a custom data processing extension that cannot be accessed.
This error occurs when a data source refers to a custom extension (like a plug-in or third-party connector) that is missing, not deployed correctly, or inaccessible at runtime.
Make sure that the custom data extension used in a data source exists and is accessible.
The {2} expression for the {0} {1} refers to a non-existing data source {3}. Letters in the names of data sources must use the correct case.
This error occurs when an expression references a data source name that does not exist or is misspelled (including casing mismatches) in the report definition.
Use the existing data source within a report and ensure that the provided data source exists in the DataSources global collection.
The expression used for the parameter {1} in the data set {3} refers to a data source. Data sources cannot be used in query parameter expressions.
This error occurs when a dataset query parameter improperly attempts to access or evaluate a data source object.
Modify the expression in the query parameter value that references the data source global collection in a report.
The expression used for the language of ‘{1}’ refers to a data source. Data sources cannot be used in report language expressions.
This error occurs when the Language property of the report attempts to derive its value from a data source, which is not allowed.
Modify the expression in the Report.Language property that references the data source global collection in a report.
A {2} expression used for the report parameter {1} refers to a data source. Data sources cannot be used in report parameter expressions.
This error occurs when a report parameter expression attempts to use the data source collection, which is not valid in that context.
Modify the expression in the ReportParameter RDL element if it references the data source global collection in a report.
The {2} expression for the {0} {1} refers to a data source. Data sources cannot be used in page headers or footers.
This error occurs when an expression in a header or footer attempts to access a data source, which is disallowed because headers and footers cannot access data-bound content directly.
Modify the expression in the PageHeader and PageFooter RDL elements if it references the data source global collection in a report.
More than one report parameter in the report has the name {1}. Report parameter names must be unique within a report.
This error occurs when two or more report parameters share the same name, causing conflicts in reference and evaluation.
Provide a unique name for ReportParameter in the ReportParameters collection. Ensure that the name properties of two or more ReportParameters are different within the same report.
More than one report parameter in the report has the (case-insensitive) name {1}. Report parameter names that only differ in case should be avoided.
Even though parameter names may technically differ by case, case-insensitive environments can lead to ambiguity or runtime conflicts.
Provide a unique ReportParameter name. Ensure that the parameter name is different, including case.
{1} is not a valid {0} name. Parameter names must be greater than 0 and less than or equal to {3} characters.
This error occurs when the parameter name is either empty or exceeds the maximum allowed length (typically 256 characters).
Provide the valid name in the ‘Name’ property of the ReportParameter element. The name length must be greater than zero and fewer than 256 characters.
A parameter in the {0} {1} has the name {3}. Parameter names must be CLS-compliant identifiers.
This error indicates that a parameter name contains invalid characters or formatting. It must follow CLS (Common Language Specification) naming rules.
Specify the name property of ReportParameter with a valid format. The name should not contain spaces, and it must begin with a letter followed by letters, numbers, or the underscore character.
More than one parameter in the {0} {1} has the name {3}. Parameter names must be unique within a {0}.
This error occurs when duplicate parameter names exist within the same context (Example: multiple parameters with the same name in the ReportParameters collection).
Provide a unique name attribute in ReportParameter and ensure that the name properties of two or more ReportParameters in the ReportParameters collection are different within a same report.
A {2} expression used for the report parameter {1} refers to a field. Fields cannot be used in report parameter expressions.
This error occurs when a report parameter expression references a Fields! collection, which is not accessible outside of a data region.
Modify the expression in the ReportParameter RDL element if it references Field from the Fields global collection in a report.
The report parameter {1} has a DefaultValue that has both or neither of the following: Values and DataSetReference. DefaultValue must have exactly one of these elements.
This occurs when the default value is incorrectly configured—either both a static value and dataset reference are provided, or neither is provided.
Specify the default value of a ReportParameter as one of the following: None, specific value, data set value. None is the default value.
The report parameter {1} has a DefaultValue that has a Values collection containing more than one value. For single-value parameters, only the first value in the Values collection will be used.
This warning/error appears when multiple default values are set for a parameter that only accepts a single value.
Provide the single default specific value for ReportParameter when the parameter is Single-Values (Multivalue is set to false).
The report parameter {1} is a multiple value parameter and accepts a null value. This is not allowed.
Multi-value parameters cannot accept null values because null cannot be included in a selection of multiple values.
Ensure that both the Multivalue and Nullable properties of ReportParameter are set to true. Since the Multivalue parameter does not accept a null value, remove Nullable.
The report parameter {1} has multiple default values and is not a multiple value parameter.
This error occurs when more than one default value is assigned to a parameter that is configured as single-valued.
ReportParameter contains multiple default values but Multivalue is not enabled. Set the Multivalue property value to true to use multiple default values.
The report parameter {1} has a ValidValues that has both or neither of the following: ParameterValues and DataSetReference. ValidValues must have exactly one of these elements.
This occurs when valid values are improperly defined using both static entries (ParameterValues) and a dataset (DataSetReference) or none at all.
Specify the valid value of a ReportParameter as one of the following: None, specific value, data set value. None is the default value.
The report parameter {1} valid values refers to a data set “{3}”, that does not exist.
This error occurs when the DataSetReference for valid values points to a dataset that isn’t defined in the report.
Provide the valid data set name in the DataSetReference element when ValidValue for ReportParameter is specified from a data set.
The parameter {1} has no default. A default is required for all non-nullable parameters that are defined as read-only.
A read-only parameter that doesn’t allow null values must have a default value set, since the user cannot provide input.
Provide a default value for all non-nullable parameters.
The parameter {1} has no default. A default is required for all non-nullable parameters without a prompt or the valid values list has to contain Null.
Non-nullable parameters that don’t prompt the user must be assigned a default value. Otherwise, the report cannot resolve the parameter value.
Specify a default value for all non-nullable parameters or ensure that valid value contains a ‘Null’ value.
The report parameter {1} default value refers to a data set “{3}”, which does not exist.
This error occurs when a report parameter’s default value references a dataset name that is not defined in the report.
Provide the valid data set name in the DataSetReference element when a default value for ReportParameter is specified from a data set.
The report parameter {1} has a DefaultValue or a ValidValue that depends on the report parameter “{3}”. Forward dependencies are not valid.
A forward dependency occurs when one report parameter depends on the value of another parameter that appears later in the evaluation order.
Remove the forward dependency of ReportParameter. Make sure that the dependent order of a parameter is correct.
The value of parameter ‘{0}’ is not valid or null.
The parameter has either not been provided a value or was given an invalid/null value that is not acceptable due to its constraints.
Add the valid value to ReportParameter
A {2} expression used for the report parameter {1} refers to a parameter. Parameters cannot be used in report parameter expressions.
This error occurs when a report parameter expression references another parameter, which is not supported in certain expression contexts.
The {2} expression for the {0} {1} refers to a non-existing report parameter {3}. Letters in the names of parameters must use the correct case.
An expression references a report parameter that does not exist in the report definition, or the name is misspelled or has incorrect casing.
Modify the non-existing ReportParameter expression in the subreport or Drillthrough Parameters collection in a report with a valid parameter.
One or more parameters required to run the report have not been specified.
Required parameters were not supplied when attempting to render or preview the report.
Provide the valid value to ReportParameter while previewing the parent/child report.
The {2} property of {0} {1} is false. However, the ‘{3}’ property contains a value that violates the {2} property condition.
This error occurs when a parameter property setting (Example: AllowBlank=false) is violated by the provided value (Example: an empty string).
Provide the valid value to ReportParameter based on its property value. For example: If a report parameter AllowBlank property value is false, then the parameter value must be non-empty.
Error during processing of {0} report parameter. The {1} property of the report parameter {0} references the value of field {2} in data set {3}, which contains an error: {4}
An error occurred while evaluating a parameter value that references a field in a dataset. The underlying dataset or field contains an error.
Error during processing of {0} report parameter.
A generic error occurred while processing the report parameter, typically due to an invalid expression, data type mismatch, or missing data.
The property {2} of {0} {1} doesn’t have the expected type.
The value assigned to a parameter or its property (Example: default value) does not match the expected data type defined in the report.
Specify the valid value or default value of ReportParameter with respect to its data type.
Parameter validation failed. It is not possible to provide valid values for all parameters.
Report parameter validation failed because not all parameters were supplied with valid or non-null values, making it impossible to execute the report.
The value ‘{0}’ is invalid. Valid values are between ‘{1}’ and ‘{2}‘.
The input value provided is outside the valid range defined for the parameter.
The {2} expression used in {0} {1} returned a numeric value that cannot fit in an Int32. In the target report, consider modifying the type of parameter ‘{3}’ to Text to be able to represent the numeric value.
An expression resulted in a numeric value that is too large to be represented as an Int32 data type.
Specify the value to report parameter with the correct format or else change the parameter type to Text to avoid casting errors.
The {0} {1} refers to an invalid {2} {3}.
A reference in the report points to an invalid or non-existent element such as a DataSet, ReportItem, or Parameter.
Specify the valid DataSetName property of an element, ensure that the data set name exists in the DataSets global collection.
A field in the data set {4} has the name {3}. Field names must be greater than 0 and less than or equal to {5} characters.
A field name in the dataset exceeds the allowed length or is missing.
Provide the valid name in ‘Name’ property of Field element, name length must be greater than zero or less than 256 characters.
A field in the data set {4} has the name {3}. Field names must be CLS-compliant identifiers.
The field name in the dataset is not a CLS-compliant identifier.
Provide the name property of data set Field with a valid format. The name should not contain spaces, and it must begin with a letter followed by letters, numbers, or the underscore character.
The data input collection null or empty for the data set : ‘{0}’ is used in the report.
The dataset used in the report has no input data or is null.
Provide data set inputs to preview the report in ReportViewer.
The data value input is not supplied for the data set ‘{0}‘.
No value was supplied for a dataset required by the report.
Provide data set values to the DataSet element to preview the report in ReportViewer.
The value input is not a supported data type for the data set ‘{0}‘.
The input data type for the dataset is unsupported.
Reporting controls support the following types, so provide input in any one of the following formats:
IEnumerable
System.Data.DataTable
System.Data.Dataset
The {0} {1} must define either a Query or a SharedDataSetReference, but not both.
A dataset cannot define both a Query and a SharedDataSetReference.
Provide a valid data set query. A data set with same name must contain one of the following items in a report: SharedDataSetReference—Specifies shared data set; Query—Embedded data set.
The report parameter {1} uses the field {3} in a data set reference, but the data set {4} does not contain that field.
A report parameter references a field in a dataset, but the field does not exist in that dataset.
Use the existing data set reference ‘Field’ in ReportParameter.
The data set {0} refers to a shared data set “{1}”, which is not available.
The dataset refers to a shared dataset that is not available or not published on the report server.
Use the existing data set name within a report, ensure that the provided shared data set exists in ReportServer or make sure that the permission is available.
The shared data set definition is not valid. Details: {3}
The shared dataset definition is invalid due to an internal error.
Provide the valid data set definition, make sure that SharedDataSet is accessible.
The expression that references the data set ‘{0}’ does not exist in the DataSets collection. Letters in the names of data sets must use the correct case.
An expression references a dataset that does not exist or has a case-sensitive mismatch.
Use the existing data source name within a report, ensure that the provided data source exists in the DataSource element in a RDL file.
The shared data set definition is not valid.
The shared dataset definition is not valid due to incorrect syntax or schema violation.
SharedDataset definition is not valid, provide the definition as per schema standards.
The data set {1} refers to the shared data source {3}, which is not published on the report server. The shared data source {3} must be published before this {2} can run.
The dataset references a shared data source that is not yet published on the server.
Publish the data source to ReportServer to set as DataSourceReference in DataSource element.
The {2} expression for the {0} {1} refers to a non-existing data set {3}. Letters in the names of data sets must use the correct case.
An expression refers to a dataset that does not exist in the report.
Use the existing data set within a report, ensure that the provided data set exists in the DataSets global collection.
The data set {1} refers to the shared data set {3}, which is not published on the report server. The shared data set {3} must be published before this report can run.
The report references a shared dataset that is not published.
Publish the data set to ReportServer to make the set a SharedDataSetReference in the DataSet element.
The {0} ‘{1}’ specifies zero fields.
The dataset defines no fields, making it unusable in the report.
Add the fields to the DataSet element in a report definition.
The field with the name {1} in the data set {3} has both or neither of the following properties: DataField and Value. Fields must have exactly one of these properties.
A field in the dataset is defined with both DataField and Value properties, or neither, which is invalid.
Ensure that the Field element in the report data set contains only one of the following properties: DataField, Value. It should not contain both properties.
More than one field in the data set {4} has the name {3}. Field names must be unique within a data set.
This occurs when two or more fields in a dataset are assigned the same name, which causes ambiguity during report processing.
Ensure that the Field element contains a unique name attribute in Dataset. Modify the data set fields with unique names.
The {0} ‘{1}’ contains a definition for the {2} ‘{3}’. This field is missing from the returned result set from the data source.
The report references a field that is not included in the dataset’s result set, possibly due to changes in the query or stored procedure.
Add the missing field in the Dataset element. Example: Field name used in a report is missing Stored Procedure.
The {0} ‘{1}’ specifies a database collation name that is not valid: {3}.
The collation name provided in the dataset or data source is not recognized by the database engine.
Provide the valid database collation name.
The {0} ‘{1}’ is bound to a data source using the {2} data extension. The data extension returned an invalid database collation culture name: {3}.
The data extension (For example: SQL, Oracle) returned a collation culture name that is not valid or supported.
Provide the valid database collation culture name.
Error during processing of the CommandText expression of data set ‘{0}’.
The SQL query or expression used in the dataset’s CommandText is invalid or improperly formatted.
Provide the valid command text expression in the Dataset element of the report definition.
Query execution failed for data set ‘{0}‘.
The dataset query could not be executed, possibly due to permission issues, syntax errors, or connection problems.
Ensure that permission is granted to execute or retrieve the values of a data set.
The query returned no rows for the data set. The expression therefore evaluates to null.
The dataset query executed successfully but returned no data, causing expressions to evaluate to null.
Make sure that values used in expression are not null. Also ensure that rows of data are returned from the data set.
The expression used for the parameter ‘{1}’ in the data set ‘{3}’ refers to a field. Fields cannot be used in query parameter expressions.
A query parameter is incorrectly referencing a field from the dataset, which is not allowed.
Modify the value expression of a query parameter that references data set fields in a report.
One or more parameters required to run the shared data set have not been specified.
One or more parameters needed to execute the shared dataset were not provided.
Specify the value to the query parameter while executing the shared data set query.
Cannot create a data reader for dataset ‘{0}‘.
The system failed to initialize a data reader, possibly due to connection or configuration issues.
Cannot create query parameter for dataset ‘{0}‘.
The system encountered an error while creating a query parameter, possibly due to invalid definitions.
Cannot read a data field for the dataset {0}.
A field expected in the dataset could not be read, possibly due to schema mismatch or missing data.
The {0} ‘{1}’ contains a definition for the {2} ‘{3}’. The data extension returned an error during reading the field. {4}
The data extension encountered an error while reading a specific field.
The {0} ‘{1}’ contains a definition for the {2} ‘{3}({4})’. The data extension returned an error during reading the field property. {5}
The data extension failed to read a property (For Example: data type, size) of a field.
Cannot read the next data row for the dataset {0}.
An error occurred while attempting to read the next row of data from the dataset.
Cannot set the command text for dataset ‘{0}‘.
The system was unable to assign the SQL command text to the dataset.
Cannot set the command type for dataset ‘{0}‘.
The dataset command type (For Example: Text, StoredProcedure) could not be set.
Cannot set the query timeout for dataset ‘{0}‘.
The system failed to apply the specified timeout setting for the dataset query.
Cannot set the transaction for dataset ‘{0}‘.
The dataset could not be associated with a transaction, possibly due to configuration issues.
The {2} expression for the {0} ‘{1}’ has an inner aggregate in an outer aggregate that specifies a dataset scope. An aggregate that specifies a dataset scope cannot contain other aggregates.
An aggregate function that specifies a dataset scope contains another aggregate, which is not permitted.
Cannot read IsAggregationField for a data field for the dataset {0}.
The system failed to determine whether a field is used in an aggregation, possibly due to a corrupted or incomplete dataset definition.
The {0} ‘{1}’ contains a definition for the {2} ‘{3}’. The data type for this field is not supported.
A field in the dataset uses a data type that is not supported by the reporting engine or data extension.
The {2} expression for the {0} ‘{1}’ refers to a dataset. Datasets cannot be used in page headers or footers.
Expressions in page headers or footers cannot reference datasets because these sections are processed before data is retrieved.
The expression used for the parameter ‘{1}’ in the dataset ‘{3}’ refers to a dataset. Datasets cannot be used in query parameter expressions.
Query parameters cannot reference datasets, as datasets are not yet available when parameters are evaluated.
The expression used for the language of ‘{1}’ refers to a dataset. Datasets cannot be used in report language expressions.
The report language setting cannot be dynamically set using dataset fields or expressions.
A {2} expression used for the report parameter ‘{1}’ refers to a dataset. Datasets cannot be used in report parameter expressions.
Report parameters cannot reference datasets, as parameters are evaluated before datasets are processed.
The {2} expression for the {0} ‘{1}’ refers to the global variable RenderFormat, which is not valid for this type of report item expression.
The RenderFormat global variable is used in an expression where it is not supported, such as in certain report items.
The {2} expression for the {0} ‘{1}’ refers to more than one report item. An expression in a page header or footer can refer to only one report item.
Expressions in headers or footers can only reference a single report item to avoid ambiguity during rendering.
The expression that references an item ‘{0}’ does not exist in the Globals collection. Letters in the names of Globals collection items must use the correct case.
The expression references a non-existent or incorrectly cased item in the Globals collection.
Specify the valid element in the expression that refers to the Globals collection. The name must match an item that exists in the Globals collection.
The expression that references the parameter ‘{0}’ does not exist in the Parameters collection. Letters in the names of parameters must use the correct case.
The expression references a parameter that does not exist or is incorrectly cased in the Parameters collection.
Specify the valid parameter in the expression that exists in the parameter collection. The name must match a parameter that exists in the Parameters collection.
The expression that references the report item ‘{0}’ does not exist in the ReportItems collection. Expressions can only refer to other report items within the same grouping. Letters in the names of report items must use the correct case.
The expression references a report item that does not exist, is misspelled, or is outside the current grouping scope.
Specify the valid variables in the expression in the report definition. The names must match items, groups, or data sets in the report.
The {2} expression for the {0} ‘{1}’ refers to the global variable OverallPageNumber or OverallTotalPages. These global variables can be used only in the page header and page footer.
These global variables are only valid in page headers or footers and cannot be used in the report body.
Remove or modify the expression that contains the OverallPageNumber or OverallTotalPages global collection, which exists in the report body collection instead of in the header or footer sections.
The {2} expression for the {0} ‘{1}’ refers to the global variable OverallPageNumber or OverallTotalPages in an aggregate function that specifies a dataset scope. These global variables cannot be used with an aggregate function that has a dataset scope in a page header or page footer.
These global variables cannot be used within aggregate functions that specify a dataset scope in headers or footers.
Remove or modify the expression in the PageSection or PageHeaderFooter. It contains the OverallPageNumber or OverallTotalPages global collection as scope aggregate.
The {2} expression for the {0} ‘{1}’ refers to the global variable PageNumber or TotalPages. These global variables can be used only in the page header and page footer.
These global variables are only valid in page headers or footers and cannot be used in the report body.
Remove or modify the expression that contains the PageNumber or TotalPages global collection and exists in the report body collection instead of in the header or footer sections.
The {2} expression for the {0} ‘{1}’ refers to the global variable PageNumber or TotalPages within a data set aggregate. These global variables cannot be used in scoped aggregates within the page header and page footer.
These global variables cannot be used within dataset-scoped aggregates in headers or footers.
Remove or modify the expression that exists in the PageSection or PageHeaderFooter and contains the PageNumber or TotalPages global collection as scope aggregate.
A group expression for the {0} ‘{1}’ refers to a report item. Report items cannot be used in group expressions.
Group expressions must be based on fields or parameters, not report items.
Remove or modify the group expression (Group.GroupExpressions) that references the ReportItems global collection.
The {2} expression for the {0} ‘{1}’ contains a report item reference in an argument to a Lookup or LookupSet function. Report item references cannot be used for the destination or result Expression parameter of a lookup function.
Report items cannot be used as arguments in Lookup or LookupSet functions for destination or result expressions.
Remove or modify the Lookup or LookupSet expression that references the ReportItems global collection in the resultant argument.
The expression used for the parameter ‘{1}’ in the dataset ‘{3}’ refers to a report item. Report items cannot be used in query parameter expressions.
Query parameters cannot reference report items, as report items are not available at query execution time.
Remove or modify the QueryParameter value expression that references the ReportItems global collection.
The expression used for the language of ‘{1}’ refers to a report item. Report items cannot be used in report language expressions.
The report language setting cannot be dynamically set using report items.
Remove or modify the Report.Language value expression that references the ReportItems global collection.
A {2} expression used for the report parameter ‘{1}’ refers to a report item. Report items cannot be used in report parameter expressions.
Report parameters cannot reference report items, as parameters are evaluated before report items are processed.
Remove or modify the expression that references the ReportItems global collection within the ReportParameter element.
The {2} expression for the {0} ‘{1}’ references report item ‘{3}’ in an aggregate expression with a scope. A scope is not allowed on aggregates in the page header or footer which reference report items.
An aggregate expression in a page header or footer references a report item and includes a scope. This is not allowed because scoped aggregates cannot reference report items in these sections.
Remove or modify the expression in the PageSection or PageHeaderFooter that contains the ReportItems global collection as scope aggregate.
A sort expression for the {0} ‘{1}’ refers to a report item. Report items cannot be used in sort expressions.
Sort expressions must be based on fields or parameters. Report items cannot be used because they are not evaluated in the context required for sorting.
Remove or modify the expression that references the ReportItems global collection within the UserSort.SortExpression or SortExpression.Value element.
The {2} value expression used for the language of ‘{1}’ refers to a report item. Variable values cannot be used in report language expressions.
The language of a report cannot be dynamically set using report items, as these are not available at the time the language is evaluated.
Remove or modify the expression that refers to the report item via the ReportItems global collection within the Variable.Value element.
The {2} expression for the {0} ‘{1}’ refers to the report item ‘{3}’. Report item expressions can only refer to other report items within the same grouping scope or a containing grouping scope. Letters in the names of report items must use the correct case.
A report item is referenced in an expression, but it is not within the same or a containing grouping scope, which is required for valid references.
Use the existing report item in an expression that is referenced through the ReportItems global collection.
The {2} expression for the {0} ‘{1}’ refers to the report item ‘{3}’. Report item expressions in a Page Header or Footer can only refer to report items within the same ReportSection. Letters in the names of report items must use the correct case.
Expressions in page headers or footers can only reference report items that exist within the same ReportSection.
Remove or modify the expression in PageSection that refers to report items via the ReportItems global collection and does not exist in the current ReportSection. Provide the expression based on scope.
The expression used for the calculated field ‘{1}’ includes a variable reference. Variable values cannot be used in calculated field expressions.
Variables cannot be used in calculated field expressions because fields are evaluated in a different context than variables.
Remove or modify the field expression that refers to the Variables global collection. Field elements must not contain the Variables global collection in a report.
A sort expression for the {0} ‘{1}’ includes a variable reference. Variable values cannot be used in data row sort expressions.
Variables cannot be used in sort expressions for data regions like Tablix, Chart, or GaugePanel, as sorting is evaluated before variables are processed.
Remove or modify the sort expressions of respective report items that refer to the Variables global collection. GaugePanel, Chart, or Tablix sort expressions must not reference Variables collection in a report definition.
A group expression for the {0} ‘{1}’ includes a variable reference. Variable values cannot be used in group expressions.
Group expressions must be based on fields or parameters. Variables are not allowed because they are not evaluated in the grouping context.
Remove or modify the group expression that refers to the Variables global collection. Group.GroupExpressions must not contain the Variables global collection in a report.
The {2} expression for the {0} ‘{1}’ contains a variable reference in the Expression argument of a Previous function. Variable values cannot be used in the Expression parameter of the Previous function.
The Previous function cannot use variables in its expression argument, as it relies on row context which variables do not support.
Remove or modify the Previous aggregate expression that refers to the Variables global collection. The Previous function must not contain the Variables global collection in a report definition.
The expression used for the parameter ‘{1}’ in the dataset ‘{3}’ includes a variable reference. Variable values cannot be used in query parameter expressions.
Variables cannot be used in query parameter expressions because parameters are evaluated before variables are initialized.
Remove or modify the QueryParameter value expression that refers to the Variables global collection. The QueryParameter.Value element must not contain the Variables global collection in a report definition.
The expression used for the language of ‘{1}’ includes a variable reference. Variable values cannot be used in report language expressions.
This error indicates that a report language setting is incorrectly using a variable. Language expressions must be static and cannot depend on runtime variables.
Remove or modify the Report.Language expression that refers to the Variables global collection. The Report.Language element must not contain the Variables global collection in a report definition.
The {2} expression used for the report parameter ‘{1}’ includes a variable reference. Variable values cannot be used in report parameter expressions.
A report parameter expression incorrectly references a variable. Such expressions should not include variable dependencies.
Remove or modify the ReportParameter expression that refers to the Variables global collection. The ReportParameter element must not contain the Variables global collection in a report definition.
The {2} expression for the {0} ‘{1}’ refers to a field. Fields cannot be used in page headers or footers.
A field is referenced in a page header or footer, which is not allowed. Fields are evaluated in the context of data regions, not page headers or footers.
Remove or modify the field expression in PageSection or PageHeaderFooter that refers to Field via the Fields global collection.
The {2} expression for the {0} ‘{1}’ uses a scope parameter for an aggregate function. The scope parameter cannot be used in page headers or footers.
An aggregate function with a scope parameter is used in a header or footer, which is not permitted.
Remove or modify the expression in PageHeaderFooter that refers to the aggregate function as scope.
A {2} for the {0} ‘{1}’ uses the aggregate function RunningValue. RunningValue cannot be used in filters.
The RunningValue function is used in a filter, which is invalid. RunningValue is not supported in filter expressions.
Remove or modify the Filter.FilterExpression element value expression that refers to the RunningValue aggregate function. Filter expressions must not contain the RunningValue aggregate function.
A filter value in the filter for {0} ‘{1}’ specifies a data type that is not supported by the ‘{3}’ operator. Verify that the data type for each filter value is {4}.
A filter value uses an unsupported data type for a specified operator.
Specify the valid data type for the filter value expression. Supported data types are: Text, Integer, Date Time, Boolean, Float.
A {2} for the {0} ‘{1}’ includes an aggregate function. Aggregate functions cannot be used in dataset filters or data region filters.
An aggregate function is incorrectly used in a dataset or data region filter.
Remove or modify the Filter.FilterExpression element or Filter.FilterValues expression that refers to an aggregate function. Filter expressions must not contain aggregate functions. Note: Previous, RunningValue, and RowNumber aggregate functions will display respective error codes.
Failed to evaluate the {2} of the {0} ‘{1}
Evaluation of a component (For example: expression or filter) failed, but further details are unspecified.
Failed to evaluate the {2} of the {0} ‘{1}’. It references a dataset field which has an error: {3}
Evaluation failed due to an error in a referenced dataset field.
A {2} for the {0} ‘{1}’ refers to a report item. Report items cannot be used in filters.
A report item is referenced in a filter, which is not allowed.
Remove or modify the expression that refers to report items via the ReportItems global collection within the Filter.FilterExpression or Filter.FilterValues element.
A filter expression for the {0} ‘{1}’ includes a variable reference. Variable values cannot be used in {0} filter expressions.
This error occurs when a filter expression includes a variable reference from the Variables global collection, which is not allowed in report filter expressions.
Remove or modify the FilterValues or FilterExpression that refers to the Variables global collection. Gauge filters, Chart filters, Tablix filters or Dataset filters must not refer to the Variables global collection in a report definition.
The dependent assembly ‘{0}’ is missing to export the report into required format.
This error is raised when a required dependent assembly is missing for exporting the report into the specified format.
More than one report item in the report has the name ‘{1}’. Report item names must be unique within a report.
This error indicates that multiple report items in a report have the same name, which must be unique.
Provide a unique Name attribute for the report item in the ReportItems collection. Ensure that the Name properties of two or more report items are different within the same report.
The {0} ‘{1}’ is invalid. The value for the {2} property is missing.
This error appears when a report item is missing a required property value, such as DataSetName, for certain data region items when there are multiple data sets.
Specify the DataSetName property value for Gauge, Tablix, List, etc. Data region report items must contain a non-empty DataSetName element if report contains more than one data set in the Datasets collection.
More than one {2} in the {0} ‘{1}’ has the name ‘{3}’. {2} names must be unique within a {0}.
This error arises when multiple items within a container, like a report or group, share the same name which should be unique.
Provide a unique Name attribute for the report item in a report or group within scope. Ensure that the Name properties of two or more items are different in the report definition.
The value of the {2} property for the {0} ‘{1}’ is negative. Negative sizes are not allowed.
This occurs when a size-related property in a report item is specified as a negative value, which is not allowed.
Specify a non-negative value in the Size element in the report definition.
The {0} ‘{1}’ has ‘{3}’ as a toggle item. Toggle items must be text boxes that share the same scope as the hidden item or are in a scope that contains the hidden item, and cannot be contained within the current report item unless current grouping scope has a Parent.
It flags an incorrect toggle item setup where the toggle is not within the proper scope or does not follow the scope rules related to grouping.
Provide the Visibility ToggleItem element within the same scope in a report definition.
The {0} ‘{1}’ contains CustomProperties. The CustomProperty({3}) is missing a {2} element, which is mandatory.
This error is reported when a required element for a custom property is missing, making it incomplete.
Specify a name attribute of CustomProperty. Custom property names are mandatory and the attribute should not be empty.
The {0} ‘{1}’ is in the page header or footer and has bookmark property. Bookmarks in page headers and page footers are not supported by all renderers.
This indicates unsupported bookmarks used in page headers or footers that certain renderers do not handle.
Remove the Bookmark property specified in a PageSection or PageHeaderFooter element.
The object ‘{0}’ does not exist in the collection.
This error is triggered when an object does not exist in the specified collection.
The {0} ‘{1}’ is in the page header or footer and has a {2} element. {2} cannot be used by text boxes in the page header or footer.
This error happens when a text box in a header or footer incorrectly uses an element that is not supported in those sections.
Specify the UserSort Textbox element within the scope.
The {0} ‘{1}’ has an Action that has more than one of the following: Hyperlink, BookmarkLink or Drillthrough. Action must have exactly one of these elements.
This is triggered when an action in a report item is configured with multiple elements like Hyperlink, BookmarkLink, or Drillthrough rather than just one.
Remove the multiple action info specified in an Action element. The ActionInfo of a Report Item element must contain one of the following: Hyperlink, Bookmark, or Drillthrough.
The {0} ‘{1}’ has multiple actions. Action label property is required.
This error indicates that an action label property is missing for report items that have multiple actions.
Remove the multiple action or specify the label for each action and provide valid action label.
The {2} expression for the {0} ‘{1}’ includes the function CountRows. CountRows cannot be used in page headers or footers.
This error is raised by using the CountRows function in page headers or footers, where it is not permitted.
The {2} for the {0} ‘{1}’ is not valid. A {2} can not be an empty string or just white space.
This arises when a property is an empty string or just whitespace, which is not valid for certain report elements.
Provide a value for the ReportName property of a Subreport or Drillthrough element. It should not be empty.
The {2} for the {0} ‘{1}’ is not valid. Item names cannot contain the following reserved characters {3}.
This warns against invalid characters in report item names which should not include reserved characters.
Remove the invalid or special character(s) in a name of a report.
The {2} for the {0} ‘{1}’ is not valid.
This error signifies that a report item contains invalid or special characters that are not supported in its name.
Remove the invalid or special character(s) for URI in name of report.
The value ‘{3}’ of the {2} property of the {0} ‘{1}’ has an invalid schema. URLs in reports may only use http://, https://, ftp://, mailto: or news:
This occurs when a URL in a report uses a schema that is not among the supported ones like http, https, ftp, etc.
Specify the valid URL. URL must begin with http://, https://, ftp://,mailto:, or news: and is referenced by the following elements, 1. Action.Hyperlink, 2. Image value of Background, Cap, Frame, Gauge, Image, MapMarker, Pointer, State, TopImage properties.
The {0} ‘{1}’ has the URL “{3}” as one of its properties. URLs in reports must begin with one of the following prefixes: {4}.
This error occurs when a URL specified in a report item (such as an image, hyperlink, or action) does not start with a valid or recognized URI scheme.
Specify the valid URL in an Image.Value element. URL must begin with http://, https://, ftp://,mailto:, or news:.
The URL {0} has an invalid schema. URLs in reports may only use http://, https://, ftp://, file:, mailto: or news:
This error occurs when a URL used in a report item (such as an image, hyperlink, or action) begins with a schema (protocol) that is not supported by BoldReports
Specify the valid and supported URL in the report. URL must begin with http://, https://, ftp://,mailto:, or news:.
The endpoint of the line ‘{1}’ is negative. The value for Left plus the value for Width of a line cannot result in a negative value.
This error indicates that the endpoint calculations for line items result in a negative value, which is not permissible.
Specify non-negative values for the Left and Width elements of a line report item in a report definition.
The endpoint of the line ‘{1}’ is negative. The value for Top plus the value for Height of a line cannot result in a negative value.
This signals a negative endpoint value for top plus height calculations of a line item.
Specify non-negative values for the Top and Height elements of a line report item in a report definition.
The {0} ‘{1}’ has a Toggle. Toggle is not allowed in page headers or footers.
This error arises when a toggle function is improperly placed in page headers or footers.
The SortItemId is invalid. It must be a positive integer and has to be existing.
This points to an invalid SortItemId, which must be existing and a positive integer.
The {0} ‘{1}’ has an invalid {2} “{3}”. The scope must be the current scope, a peer scope, which is a data region, or an ancestor scope. If the current scope and target scope are groupings, then both scopes must be along the same axis.
Indicates an invalid scope for a report element, requiring it be a current, peer, or ancestor scope.
The {0} ‘{1}’ contains an invalid {4}. The {2} element is not allowed if {3} is omitted.
Flags the inclusion of an element when a required accompanying element is omitted.
The {0} ‘{1}’ has an invalid {2} ‘{3}‘. The scope cannot be a grouping that has a domain scope defined.
A component references a scope that is defined across multiple domains or contexts, which is not allowed for certain operations.
The {0} ‘{1}’ has an invalid {2} “{3}”. The scope cannot be a detail grouping scope. To use a detail grouping scope, do not specify a {2}.
A detail-level scope (that is one without grouping) is being used where a named scope is required.
The {2} expression for the {0} ‘{1}’ is invalid (it is an empty string).
This specifies that an expression for a report component is not valid because it results in an empty string.
The {2} for the {0} ‘{1}’ is invalid. Details: {3}
An expression is invalid due to a specific issue, which is detailed in the accompanying message.
The {2} expression for the {0} ‘{1}’ specifies a scope that is not valid for a nested aggregate. The scope must be the same name of the scope specified by the outer aggregate or the name of a group or data region that is contained in the scope specified by the outer aggregate.
Highlights that a nested aggregate expression has an incorrect scope that does not match the requirements for proper scoping.
Specify the valid scope in an expression parameter of the nested aggregate function.
The {2} expression for the {0} ‘{1}’ has a nested aggregate that specifies a dataset scope. Inner aggregates cannot specify a dataset scope.
A nested operation references a dataset-level scope, which is not allowed.
Remove the data set name specified in the expression parameter of the nested aggregate function.
The {2} expression for the {0} ‘{1}’ has an inner aggregate that specifies the recursive flag. Nested aggregates cannot specify the recursive flag.
A nested operation includes a recursive flag, which is not supported in this context.
Remove the recursive parameter specified in the expression argument of the nested aggregate function.
The {2} expression for the {0} ‘{1}’ uses an aggregate expression with the recursive/simple flag. The recursive/simple flag is not allowed for First, Last, Previous, RowNumber, RunningValue and Aggregate.
Highlights inaccuracies with the use of specific function flags within aggregate expressions.
Remove the First, Last, Previous, RowNumber, RunningValue, or Aggregate functions specified in the recursive function.
The {2} expression for the {0} ‘{1}’ includes an aggregate function in the argument to another aggregate function. Nested aggregates are not allowed inside filter expressions.
This error highlights an issue with a nested aggregate present within a filter expression, which is not allowed.
Remove the nested aggregate function specified in the Filter expression value.
The {2} value expression for the {0} ‘{1}’ uses an aggregate function in the argument to another aggregate function. Nested aggregates are not allowed inside group variable expressions.
Points out the invalid use of a nested aggregate function inside a group variable expression.
Remove the nested aggregate function specified in the Group.Variables expression value.
The {2} expression for the {0} ‘{1}’ uses an aggregate function in the argument to another aggregate function. Nested aggregates are not allowed in the page header or footer.
Occurs when a nested aggregate is incorrectly used in a header or footer expression.
Remove the nested aggregate function specified in the report page header or page footer expression parameter.
The {2} expression for the {0} ‘{1}’ contains a nested aggregate that does not specify a scope. In a tablix cell that belongs to both row and column groups, or on a data point that belongs to both series and category groups, when the outer aggregate specifies a group scope, nested aggregates must specify a scope.
Indicates that a nested aggregate lacks the required scope specification in complex report items like tablix cells.
Specify the scope parameter for the aggregate function. Aggregate functions in an expression must contain a scope parameter.
The {2} expression for the {0} ‘{1}’ uses both row and column scopes or scopes from two different data axes in the same aggregate expression. All nested aggregate functions must specify a named scope along the same data axis as the scope of the containing aggregate.
Flags improper utilization of mixed or incorrect scope in nested aggregate functions.
Specify the unique scope for the nested aggregate expression. The scope of an aggregate and axis, row group, or column group must be same.
The {2} expression for the {0} ‘{1}’ uses an outer aggregate that specifies a Lookup expression that uses an aggregate. Nested aggregates cannot be specified in a Lookup expression.
This error warns against employing nested aggregates within Lookup expressions, which is not supported.
Remove the nested aggregate function in a Lookup, LookupSet, MultiLookup source parameter expression, in which a miscellaneous function exists inside the aggregate function.