Troubleshooting Errors

2 Jun 202113 minutes to read

To resolve the respective issues in report viewer, use the following troubleshooting steps:

RV001

CODE RV001
TEXT The source of the report definition has not been specified.
DESCRIPTION The report viewer will not render the report when either the report path or stream is not set or the given path is incorrect.
SOLUTION
  • Make sure that the report path is specified and ensure whether the name or report path is correct.
  • Check whether the report exists in the specified directory or not and also it should be accessible.
    • For Example : viewer.ReportPath = @"../../SampleReport.rdl";

    RV002

    CODE RV002
    TEXT The report definition has an invalid schema version.
    DESCRIPTION Report definition should contain the supported schema version (For Example : 2008) to render the report in the report viewer.
    SOLUTION Make sure that the provided schema in your report definition is supported in the report viewer.
    Supported versions are 2008, 2010, and 2016.

    RV003

    CODE RV003
    TEXT Report Deserialization failed.
    DESCRIPTION An error is occurred during the deserialization of the report definition.
    SOLUTION
  • XML deserialization is failed due to incorrect item tags or missed element. Report item elements should have its required attribute.
  • Note: Detailed description with line number and position is mentioned in the report viewer instance error dialog.
    		•

    RV004

    CODE RV004
    TEXT Invalid Expression
    DESCRIPTION The expression used in the report is incorrect scope or syntax or unsupported.
    SOLUTION
  • Ensure that the expression used in the report is correct with valid scope and syntax.
    • Note: Detailed information of report item along with line number and position is mentioned in the report viewer instance error dialog.

    RV005

    CODE RV005
    TEXT The requested file or assembly was not found. It may have either moved or renamed.
    DESCRIPTION Any of the assembly related to report platform is missed at installation location.
    SOLUTION If you are previewing the report from Report Designer, check whether any assembly is missed at installed location (%ProgramData%\Syncfusion\Report Designer\ReportDesigner) or reinstall the Report Designer application. If you are loading the report from SDK sample, check whether any assembly is missed at installed location (%ProgramData%\Report Platform SDK\Assemblies) or reinstall the Report Platform SDK application. If you are loading the report from Report Server, check whether any assembly is missed at installed location (%ProgramData%\Report Server\ReportServer.Web\bin) or reinstall the Report Server application. Note : Please contact Syncfusion support if you cannot resolve the issue.

    RV006

    CODE RV006
    TEXT An error is occurred while sending a request to the reporting service.
    DESCRIPTION Report will not be rendered when there is a problem while connecting or retrieving the data from provided reporting service's URL.
    SOLUTION
    1. Make sure that you are connected to the Internet.
    2. Ensure that the specified reporting service URL is valid.
    3. Check whether the reporting service is running or not.
      If not, start the reporting service from the desktop shortcut (For Example : Start Syncfusion Report Server IIS Express) or from installed location.
    Installed location path : (%ProgramData%\Report Server\Infrastructure\StartReportServerIISExpress)

    RV007

    CODE RV007
    TEXT Invalid object name.
    DESCRIPTION Specified data source is invalid.
    SOLUTION Verify that you are connected to the data source and query syntax is correct.

    RV008

    CODE RV008
    TEXT Cannot load sub report.
    DESCRIPTION Sub report cannot be loaded with an invalid name or report path.
    SOLUTION
  • Make sure that the sub report path is specified and ensure whether the name or path is correct.
  • Check whether the report exists in the specified directory or not and also it should be accessible.
    		•

    RV009

    CODE RV009
    TEXT The data source used in a report does not exist or not accessible.
    DESCRIPTION Report will not be rendered in the report viewer when the data source used in a report does not exists or it is non accessible due to permission rights.
    SOLUTION Ensure whether the data source in a report exists in the referred location.
  • For embedded data source, the data source is referred in the local machine
  • For shared data source, the data source is existed in the server and used in the local machine. Make sure that the authentication is sufficient to access the data source.
    		•

    RV010

    CODE RV010
    TEXT An error is occurred on the Report Server.
    DESCRIPTION Specified reporting service encounters an error while rendering the report in report viewer.
    SOLUTION Check the error log file(s) generated in the below mentioned location. (C:\Syncfusion\Report Server\ReportServer.Web\App_Data\Logs)
    For more information about the types of status code, refer to the available status code in online.

    RV011

    CODE RV011
    TEXT Please select a value for the report parameter.
    DESCRIPTION Report parameters must be supplied with value if it is non-nullable while trying to preview the report in report viewer.
    SOLUTION Enter the value to parameter in a parameter block, when it is non-nullable or allow blank.

    RV012

    CODE RV012
    TEXT The value provided for the report parameter is not valid for its type.
    DESCRIPTION The report will not be rendered from the report viewer when the specified value for report parameter is irrespective to its type.
    SOLUTION Provide an appropriate value to report parameter based on its data type while rendering the report.
    Example: A parameter with integer data type allows integer value, it does not allows float values.

    RV013

    CODE RV013
    TEXT Parameter is missing a value.
    DESCRIPTION Report viewer will not render the report when the hidden parameter does not contain a value, which is non-nullable.
    SOLUTION Provide value to hidden parameters in your report definition before rendering the report.
    Note: Hidden parameters must contain default value or it should be nullable.

    RV014

    CODE RV014
    TEXT Forward dependencies are not valid.
    DESCRIPTION Report will not be rendered when there is an existence of forward dependencies between parameters.
    SOLUTION Make sure to remove the forward dependencies in your report definition before previewing the report.
    Example: FirstParameter depends on Dataset1 and Dataset1 depends on SecondParameter, and then it results in forward dependency.
    Note: Parameters are executed based on the order.

    RV015

    CODE RV015
    TEXT The expression that references parameter is not valid and does not exist in the parameters collection or forward dependencies.
    DESCRIPTION Report viewer throws error when you try to use the non-existing report parameter or with forward dependencies.
    SOLUTION Make sure to use the parameters that are exists in report definition and avoid forward dependencies in the report.
    Note: Letters in the names of parameters should be in correct case.

    RV016

    CODE RV016
    TEXT Value property of an image report item contains invalid value.
    DESCRIPTION Report will not be rendered to report viewer when you try to use the invalid image data or non-existing image in the report.
    SOLUTION Ensure that the value provided to image report item is specified properly, and make sure that the image is available.
  • Embedded : Image data should be available in a report definition.
  • External : External images can be obtained by specifying a URL, and make sure that credentials are sufficient to access the image.
  • Database : Images can be referred from the dataset, and make sure that credentials are sufficient to access the database.
    		•

    RV017

    CODE RV017
    TEXT Provide Report Server information to get shared data source information.
    DESCRIPTION Report with shared data source must contain the Report Server information and credentials that are provided to render in the report viewer.
    SOLUTION Make sure that credentials in Report Server URL are not empty, and ensure that the correct information is provided to the report viewer.
    Example: viewer.ReportServerUrl = @"http://mvc.syncfusion.com/reportserver/" viewer.ReportServerCredential = new System.Net.NetworkCredential("username", "password");

    RV018

    CODE RV018
    TEXT Provide Report Server information to get shared dataset information.
    DESCRIPTION Report with shared dataset must contain the Report Server information and credentials to render in the report viewer.
    SOLUTION Make sure that credentials in Report Server URL are not empty, and ensure that the correct information is provided to the report viewer.
    Example: viewer.ReportServerUrl = @"http://mvc.syncfusion.com/reportserver/" viewer.ReportServerCredential = new System.Net.NetworkCredential("username", "password");

    RV019

    CODE RV019
    TEXT The ReportServerUrl or ReportServerCredential is missing.
    DESCRIPTION Server report or server referred items used in the report will not be rendered in the report viewer without ReportServerUrl and ReportServerCredential.
    SOLUTION Make sure that ReportServerUrl and ReportServerCredential are not empty and provided with proper data and accessible.

    RV020

    CODE RV020
    TEXT The value for the DataSetName property is missing.
    DESCRIPTION Data region items are not allowed in reports without datasets to render in the viewer.
    SOLUTION Make sure to provide dataset name property value in your report definition, ensure that the property value is not empty.

    RV021

    CODE RV021
    TEXT Data region items are not allowed in reports without datasets to render in the viewer
    DESCRIPTION Report viewer will not render the report when data region items does not refer the dataset.
    SOLUTION Make sure to provide dataset name property value in your report definition.
    Note: Report will render when the report definition has a single dataset; When dataset count is greater than one you must specify the dataset name property value to data region items (Tablix, Chart, Gauge etc..)

    RV022

    CODE RV022
    TEXT Report item refers to an invalid DataSetName.
    DESCRIPTION Report will not be rendered in the report viewer when non-existing dataset is used in the report.
    SOLUTION
  • Embedded : Make sure that the report item referred dataset exists in report definition.
  • Shared : Make sure that the referred dataset exists in server and accessible.
    		•

    RV023

    CODE RV023
    TEXT Toggle items must be text boxes that share the same scope, and they are not allowed in page headers or footers.
    DESCRIPTION In our report viewer, toggle items must be shared within same scope, and they are not allowed in page headers and page footers.
    SOLUTION Provide toggle items in the report in same scope, not from their page header or page footer.
    Example: If a report item in the page header contains the toggle item then the referred toggle item should be in header region.

    RV024

    CODE RV024
    TEXT Provide dataset inputs for report.
    DESCRIPTION To render the RDLC report, you must add the data source collection in the report viewer if any dataset is used in the report.
    SOLUTION Make sure to add the dataset to render the report in report viewer if dataset fields are used.
    Example: viewer.DataSources.Add("Dataset1", object collection of data)
    Note: Here, name ("Dataset1") is the dataset name used in the report definition.

    RV025

    CODE RV025
    TEXT Collection class or datatable input is needed.
    DESCRIPTION In report viewer to render the RDLC report, the report must have collection class or datatable input to rendering the report.
    SOLUTION Make sure to provide dataset collection to render the report. Supported collections are "IEnumerable", "System.Data.DataTable", and "System.Data.Dataset"

    RV026

    CODE RV026
    TEXT The value expression for the TextRun contains a colon or a line terminator.
    DESCRIPTION Textbox report item value expression contains a colon or a line terminator.
    Colons and line terminators are not valid in expressions.
    SOLUTION Remove colons and line terminator used in the specified report item expression.

    RV027

    CODE RV027
    TEXT The tablix report item has an invalid TablixMember in column hierarchy, and the KeepTogether property is not set to None.
    DESCRIPTION All tablix member elements in a TablixColumnHierarchy must have the KeepWithGroup property as None.
    SOLUTION Set KeepWithGroup property as "None" in a TablixColumnHierarchy for all TablixMember in the tablix report item.

    RV028

    CODE RV028
    TEXT The tablix has an invalid TablixMember in column hierarchy, and the RepeatOnNewPage property is not set to false.
    DESCRIPTION All TablixMember elements in a TablixColumnHierarchy must have the RepeatOnNewPage property which is set to false.
    SOLUTION Set RepeatOnNewPage property as "false" in a TablixColumnHierarchy for all TablixMembers.

    RV029

    CODE RV029
    TEXT Each dataset, data region, or grouping in the report has different name for their report item.
    Dataset, data region, and grouping names must be unique within a report.
    DESCRIPTION Report item referred dataset, data region, and grouping names must be unique within a report.
    Referred dataset, data region, and grouping names are different for their report item.
    SOLUTION Provide unique dataset, data region, and grouping name for their report item in your report definition.
  • Incorrect : Dataset name : Item1, Tablix name : Item1
  • Correct : Dataset name : Item1, Tablix name : Item1

    • RV030

    CODE RV030
    TEXT The tablix has a detail member with inner members.
    Detail members contain only static inner members.
    DESCRIPTION In tablix report item, detail members contain only static inner members.
    SOLUTION In tablix report item, provide static inner members for their detail members.

    RV031

    CODE RV031
    TEXT A "ReportName" can not be an empty string or just white space.
    DESCRIPTION In SubReport item, the ReportName property value cannot be an empty or just white space.
    SOLUTION Make sure that 'ReportName' property value for subreport item is non empty.

    RV032

    CODE RV032
    TEXT Subreport cannot be shown.
    DESCRIPTION Report viewer will not render the sub report without the ReportPath or ReportServerUrl.
    SOLUTION Provide subreport ReportPath or ReportServerUrl in your report.

    RV033

    CODE RV033
    TEXT The subreport cannot be found at the specified location.
    DESCRIPTION Report will not be rendered in the report viewer when the report does not exists in specified location.
    SOLUTION Make sure that the report name or path is correct, and the report exists in the specified directory.

    RV034

    CODE RV034
    TEXT RunningValue aggregate should contain 3 arguments.
    DESCRIPTION In aggregate expression, the RunningValue should have 3 arguments.
    SOLUTION Make sure that RunningValue aggregate contains three arguments.
  • Syntax: =RunningValue("FieldExpression", "Aggregate", "Scope")
  • Example: =RunningValue(Fields!YearlyIncome.Value,Sum,"GroupByInitial")
    		•

    RV035

    CODE RV035
    TEXT Report variable or group variable reference cannot be used in report parameter expressions.
    DESCRIPTION Report viewer does not renders the report when the parameter contains group or report variables. Variable values cannot be used in report parameter expressions.
    SOLUTION Remove the variable reference used in parameter expressions.

    RV036

    CODE RV036
    TEXT Fields cannot be used in report parameter expressions.
    DESCRIPTION Report viewer does not render the report when the parameter contains field expressions and fields cannot be used in report parameter expressions.
    SOLUTION Remove the field expressions used in parameter expressions.

    RV037

    CODE RV037
    TEXT Aggregate and lookup functions cannot be used in report parameter expressions.
    DESCRIPTION The value expression is used for report parameter, it includes an aggregate or lookup function.
    Aggregate and lookup functions cannot be used in report parameter expressions.
    SOLUTION Remove Aggregate and Lookup functions in your report parameter expressions.

    RV038

    CODE RV038
    TEXT ReportItem expressions can be referred only to fields within the current dataset.
    DESCRIPTION ReportItem expressions can be referred only to fields within the current dataset.
    Make sure that the field expression is referred to current dataset.
    SOLUTION Provide current dataset fields for report item expression.
  • Note : Tablix report item with scope "Dataset1" must contain the fields in the dataset1. If field expression specified in another dataset is required then you should specify the scope.
  • Example: =First(Fields!Name.Value, "Dataset2")
    		•

    RV039

    CODE RV039
    TEXT Invalid Expression
    DESCRIPTION Report viewer does not render the report when invalid expression is used.
    SOLUTION Provide valid expression in respective report item.
  • Note: Detailed description with line number and position is mentioned in the report viewer instance error dialog.
    		•

    RV040

    CODE RV040
    TEXT Expression does not used within the scope.
    DESCRIPTION Report viewer encounters an error when expression must be used outside the scope.
    SOLUTION Provide the valid expression within the scope.
  • Note: Detailed description with the line number and position is mentioned in the report viewer instance error dialog.
    		•

    RV041

    CODE RV041
    TEXT An error is occurred during the local report processing. There is an error occurred while rendering the custom code.
    DESCRIPTION Report viewer encounters an error when compiling the custom code used in the report.
    SOLUTION Provide valid custom code in your report based on detailed information mentioned in the report viewer instance error dialog.
    Note: Custom code exists in report properties.

    RV042

    CODE RV042
    TEXT Invalid operator is used in expression.
    DESCRIPTION Report viewer encounters an error if it contains invalid operator in an expression.
    SOLUTION Make sure to use appropriate and supported operators in the expression.
  • Note: Detailed information is provided with the expression, and the report item name is mentioned in the report viewer instance error dialog.
    		•

    RV043

    CODE RV043
    TEXT Unsupported Expression
    DESCRIPTION Provided expression does not support in the report viewer.
    Object expressions do not have complete support.
    SOLUTION Please use supported expression in the report viewer to render the report.

    RV044

    CODE RV044
    TEXT Method name is not a member in custom code
    DESCRIPTION Evaluated method name is not a member in your custom code.
    SOLUTION Provide valid method name. Make sure that the provided method name is present in your custom code.

    RV045

    CODE RV045
    TEXT Lookup function has incorrect number of parameters.
    DESCRIPTION Provided lookup function has incorrect number of parameters in report definition.
    SOLUTION Provide correct number of arguments for lookup expressions in respective report item expression, and refer the syntax of an look up expressions.

    RV046

    CODE RV046
    TEXT DateAdd function should have arguments.
    DESCRIPTION Report viewer encounters an error if "DateAdd" function does not contain any arguments.
    SOLUTION Provide arguments for DateAdd function in respective report item expression, refer the syntax of an DateAdd functions.
    Example: =DateAdd("d",3,Fields!BirthDate.Value)

    RV047

    CODE RV047
    TEXT DateDiff function should contain arguments.
    DESCRIPTION Report viewer encounters an error if "DateDiff" function does not contain arguments in an expression.
    SOLUTION Provide arguments for DateDiff function in respective report item expression, and refer the syntax of an DateDiff functions.
    Example: =DateDiff("yyyy",Fields!BirthDate.Value,"1/1/2010")

    RV048

    CODE RV048
    TEXT DatePart function should contain arguments.
    DESCRIPTION Report viewer encounters an error if "DatePart" function does not contain any arguments in an expression.
    SOLUTION Provide arguments for DatePart function in respective report item expression, and refer the syntax of an DatePart functions.
    Example: =DatePart("q",Fields!BirthDate.Value,0,0)

    RV049

    CODE RV049
    TEXT DateSerial function should contain arguments.
    DESCRIPTION Report viewer encounters an error if "DateSerial" function does not contain any arguments in an expression.
    SOLUTION Provide arguments for DateSerial function in respective report item expression, and refer the syntax of an DateSerial functions.
    Example: =DateSerial(DatePart("yyyy",Fields!BirthDate.Value)-10, DatePart("m",Fields!BirthDate.Value)+3,DatePart("d",Fields!BirthDate.Value)-1)

    RV050

    CODE RV050
    TEXT Provided IIF expression has invalid number of parameters.
    DESCRIPTION Report is not rendered in the report viewer when an "IIF" expression has invalid number of parameters.
    SOLUTION Provide valid number arguments in your IIF expression.
  • Syntax: IIf(Expression As Boolean, TruePart As Object, FalsePart As Object) As Object

    • RV051

    CODE RV051
    TEXT PaymentPeriod must be between 1 and numberOfPayments.
    DESCRIPTION Report viewer encounters an error if the payment period does not falls within the range.
    SOLUTION Provide payment period value between 1 and numberOfPayments.

    RV052

    CODE RV052
    TEXT This implementation does not handle zero interest rate.
    DESCRIPTION Report is not rendered in the report viewer when it holds the zero interest rate.
    SOLUTION Provide greater than 0 or less than 0 interest rate. Does not provide 0 value for their interest rate.