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.