Errors, Warnings, and Information Messages
- 20 minutes to read
This topic lists the errors, warnings, and information messages that may appear in the Error List as you design or preview a report, or write report scripts. A hint is available for each message with a suggestion on how to address the issue.
XRE001
Message Text | The property is set to an invalid value |
Message Type |
|
Why the Message Appears | This message appears if your report contains a Sparkline control with unspecified data:
|
How to Fix | Ensure that the Sparkline’s Data Source, Data Member, and Value Member properties are configured. |
Error
XRE002
Message Text | The control is outside the right page margin |
Message Type |
|
Why the Message Appears | If a control falls outside the right page margin, it does not appear on printed media properly. The Designer does not let you move controls outside the top or left margin. The bottom margin is unreachable because the content that exceeds a page is carried over to the next page. |
How to Fix | Ensure that the control is inside the report’s margins to avoid printing extra pages:
|
WarningXRE003
Message Text | The control is outside of the report’s printing area |
Message Type |
|
Why the Message Appears | In multi-column reports, a Detail band‘s width can be shorter than the report’s page width. A control that goes outside this band cannot be displayed or printed properly. |
How to Fix | Ensure that the control is within the print area:
|
XRE004
Message Text | The control is overlapped |
Message Type |
|
Why the Message Appears | Overlapped controls may cause an issue when you export a report to HTML, RTF, DOCX, XLS, XLSX, CSV, and Text formats. To warn you of possible issues, overlapped controls are highlighted and message XRE004 appears. |
How to Fix | Ensure that controls do not overlap - move or resize these controls on the design surface so that they do not overlap. |
XRE009
Message Text | An error occurred when the script method was executed |
Message Type |
|
Why the Message Appears | Report scripts can cause exceptions due to hardware failures or programming errors. If an unhandled exception occurs in report scripts, message XRE009 appears to help you fix the script code. |
How to Fix | Ensure that the script code includes handlers for all possible exception situations. |
XRE010
Message Text | Unable to resolve the Navigation URL for the ‘_self’ Target |
Message Type |
|
Why the Message Appears | The _self target specifies that the Navigation URL property points to a bookmark within the report. If the report does not contain the specified bookmark, error message XRE010 appears to help you fix the issue. |
How to Fix | Set the Navigation URL property to a valid value: Select the control, switch to the Properties window, expand the Navigation URL property’s drop-down list, and select a valid value from the list. |
XRE011
Message Text | Unable to load the content from the specified file/URI |
Message Type |
|
Why the Message Appears | You can use external content in a report: images, PDF documents, or other reports. A file or URI that stores this external content should be referenced in your report. If the referenced location is not found, message XRE011 appears so that you can correct the path/URI or place the file in the right location. |
How to Fix | Ensure that the requested file or content is available at the specified path or URI. |
XRE012
Message Text | Unable to resolve the URI from the specified path/URL |
Message Type |
|
Why the Message Appears | You can use external content in a report: images, PDF documents, or other reports. A file or URI that stores this external content should be referenced in your report. If the path or URI is not valid (for instance, cd:\path\to\image.png or https://path.to/image.png), message XRE012 appears to help you correct the path/URI. |
How to Fix | Ensure that the file or URI location is specified correctly. |
XRE013
Message Text | Unable to load the content from the specified file/URI |
Message Type |
|
Why the Message Appears | You can use external content in a report: images, PDF documents, or other reports. A file or URI that stores this external content should be referenced in your report. If the application does not have access rights to the specified location, message XRE013 appears. |
How to Fix | Ensure that the application, system, or network security settings do not restrict access to the specified file or URI. Contact your system administrator if necessary. |
XRE015
Message Text | The text format string is invalid |
Message Type |
|
Why the Message Appears | You can use format strings in controls to format the displayed values. If a control’s format string is not valid, message XRE015 appears to help you fix the format string. See the following topic for more information: Format Data. |
How to Fix | Adjust the format string. Select the control, switch to the Properties window, and click the Text Format String property’s ellipsis button. Specify a valid format string in the invoked Format String Editor. |
XRE016
Message Text | The formatting rule is not contained in the report’s FormattingRuleSheet and will not be applied |
Message Type |
|
Why the Message Appears | This issue appears when you assign a format rule to a control in code but forget to add this rule to the report’s FormattingRuleSheet collection. As a result, the formatting rule is not applied to the control. This rule is also unavailable in the Report Designer, so the only way to fix the issue is to change the code that generates the report. |
How to Fix | Add the format rule to the report’s FormattingRuleSheet collection and apply the added rule to the control. |
XRE020
Message Text | The property’s binding does not match the data member |
Message Type |
|
Why the Message Appears | The issue appears when you bind a control to a field that is not stored in the table specified as the report’s Data Member. In this case, the control receives only the first record from the referenced table. |
How to Fix | Ensure that the control’s data binding is valid: switch to the Properties window and bind the property to a data field from the table to which the band is bound. |
InformationXRE021
Message Text | The property’s expression does not match the data member |
Message Type |
|
Why the Message Appears | The issue appears when you bind a control to a field that is not stored in the table specified as the report’s Data Member. In this case, the control receives only the first record from the referenced table. |
How to Fix | Ensure that the property’s expression is valid: switch to the Properties window, invoke the property’s Expression Editor, and specify an expression that uses data fields from the table or collection that is the report’s data member. |
XRE022
Message Text | The property’s binding is invalid |
Message Type |
|
Why the Message Appears | When you bind a control to a data field that does not exist, the control does not receive any data. This issue commonly appears in reports generated in program code, as the Report Designer does not allow users to specify non-existing fields. |
How to Fix | Ensure that the control’s data binding is valid: select the control, switch to the Properties window’s Data tab, expand the Data Bindings node and the sub-node, and select a valid value for the Binding property. |
XRE023
Message Text | The property’s expression is invalid |
Message Type |
|
Why the Message Appears | This message appears in one of the following cases:
|
How to Fix | Ensure that data fields used in your expression exist in the data source. If the data fields do exist, make sure that your report’s DataSource and/or DataMember properties are specified. |
XRE024
Message Text | The data member is invalid |
Message Type |
|
Why the Message Appears | When you specify a data member that does not exist, the report or control does not receive any data. This issue commonly appears in reports generated in program code, as the Report Designer does not allow users to specify non-existing data members. |
How to Fix | Specify a valid data member: select the source of the error, switch to the Properties window, and specify a data member for the data source. |
XRE025
Message Text | The data source is invalid |
Message Type |
|
Why the Message Appears | A data source referenced in a report, band, or control should be of a type that is supported by DevExpress reports. This issue commonly appears in reports generated in program code, as the Report Designer does not allow users to specify non-supported data sources. |
How to Fix | Assign an object of a supported type to the report’s data source. |
XRE026
Message Text | The filter string is invalid |
Message Type |
|
Why the Message Appears | A filter string uses invalid syntax or references an invalid data field or parameter. Invalid filter strings are not applied to data. |
How to Fix | Adjust the filter string: switch to the Properties window and specify a valid Filter String property value. |
XRE027
Message Text | The calculated field’s expression is invalid |
Message Type |
|
Why the Message Appears | A calculated field contains an expression that defines the field’s value. If the expression is incorrect, the value is not defined. See the following topic for more information: Expression Language. |
How to Fix | Adjust the calculated field’s expression: select the calculated field, switch to the Properties window, and specify a valid value for the Expression property. |
XRE028
Message Text | Cannot identify the calculated field’s data source |
Message Type |
|
Why the Message Appears | A calculated field can use its own data source or the report’s data source. If no data source is specified or available, the field does not receive data. |
How to Fix | Specify a valid data source for the calculated field: select the calculated field, switch to the Properties window, and specify a Data Source. If the calculated field is not needed, delete this field: select the report, switch to the Properties window, and click the Calculated Fields property’s ellipsis button. |
XRE030
Message Text | The detail report band has an inappropriate detail level |
Message Type |
|
Why the Message Appears | Nested Detail Report Bands should be bound to sequentially increasing nested (related) data members, so that DevExpress Reporting knows which member to iterate. If a Detail Report Band is not bound to the next related member, only the first record from the referenced member is returned. |
How to Fix | Bind the Detail Report Bands to sequential levels of nesting in the data source. Ensure that all intermediate nested levels are displayed. |
XRE040
Message Text | The End Band is not complementary to the Start Band |
Message Type |
|
Why the Message Appears | When you add a cross-band control (for instance, an XRCrossBandLine) to a report, place the control’s start and end in complementary bands that appear on each page of the document. The following bands are complementary:
In other cases, the control’s behavior can differ from an expected result. |
Suggested Actions | Ensure that the control starts and ends in bands that appear in the report an equal number of times on each page. |
XRE050
Message Text | The barcode text contains invalid characters |
Message Type |
|
Why the Message Appears | Each barcode type (a “barcode symbology“) has a specific set of characters that can be encoded. See your symbology’s specification for the supported character set. If a barcode encounters an unexpected character, the “There are invalid characters in the text” message is displayed instead of the specified text in the resulting report. |
How to Fix | Ensure that all characters meet the barcode specification. If your barcode uses static text, select the barcode, expand the smart tag, and correct the Text property value. If the barcode uses an expression, ensure that the expression fetches only valid characters. |
XRE051
Message Text | The barcode text format is not valid |
Message Type |
|
Why the Message Appears | Each barcode type (a “barcode symbology“) has a specific text format that can be encoded. See your symbology’s specification for the supported format. |
How to Fix | Ensure that the barcode text format meets the barcode specification. If your barcode uses static text, select the barcode, expand the smart tag, and correct the Text property value. If the barcode uses an expression, ensure that the expression fetches correct values. |
XRE052
Message Text | The barcode data is not valid |
Message Type |
|
Why the Message Appears | Each barcode type (a “barcode symbology“) has specific data type(s) that can be encoded. See your symbology’s specification for the supported data types. |
How to Fix | Ensure that the binary data assigned to the bar code is not longer than 1033 bytes and meets requirements for the current symbology. |
XRE053
Message Text | The barcode bounds are too small |
Message Type |
|
Why the Message Appears | A barcode needs a certain amount of space to display the encoded text. If the specified barcode size is insufficient, the barcode cannot display the encoded text. |
How to Fix | Increase the barcode size: select the barcode, switch to the Properties window, and increase the Width and Height properties. |
XRE054
Message Text | The barcode has incompatible settings |
Message Type |
|
Why the Message Appears | Each barcode type (a “barcode symbology“) has a set of settings that should be set to expected values. See your symbology’s specification for the supported settings. |
How to Fix | Ensure that the barcode settings meet the barcode specification. |
XRE060
Message Text | The referenced report contains a page header or a page footer band |
Message Type |
|
Why the Message Appears | The XRSubreport control has a limitation that does not allow referenced reports to contain a page header or page footer band. |
How to Fix | Referenced reports cannot contain a page header or page footer band. Remove these bands from the referenced report or reference a report that does not contain a page header or page footer band. |
XRE061
Message Text | The referenced report’s page width exceeds the current one |
Message Type |
|
Why the Message Appears | The XRSubreport control can be configured to use its own page settings. If the referenced report’s page size exceeds the main report’s page size, the combined report may not print as expected. |
How to Fix | The referenced report’s page width should be smaller than the main report’s page width. Select the report, switch to the Properties window, and change the Paper Kind property value. |
XRE062
Message Text | The parameter name in the binding is invalid |
Message Type |
|
Why the Message Appears | When you bind an XRSubreport control’s parameter to a data field that does not exist, the parameter does not receive data. |
How to Fix | Expand the Subreport control’s smart tag and click Edit Parameter Bindings. In the invoked Parameter Binding Collection Editor, select a valid parameter. |
XRE063
Message Text | The binding type does not match the report parameter type in the binding |
Message Type |
|
Why the Message Appears | When you bind an XRSubreport control’s parameter to a data field of a different type, the parameter does not receive data. |
How to Fix | Ensure that the referenced report’s parameter is of the same type as the main report’s parameter. Expand the Subreport control’s smart tag and click Edit Parameter Bindings. In the invoked Parameter Binding Collection Editor, select a parameter of the appropriate type. |
XRE064
Message Text | Unable to assign the value to the report parameter in the binding |
Message Type |
|
Why the Message Appears | When you bind an XRSubreport control’s parameter to a data field of a different type, the parameter does not receive data. |
How to Fix | Ensure that the value type is appropriate for the report parameter. |
XRE070
Message Text | The line’s width exceeds its bounds |
Message Type |
|
Why the Message Appears | Each report control has the size (the width and height) property, which defines how much space the control occupies in a report. The XRLine control also has the Line Width property, which specifies how thick the line should be. If the Line Width exceeds the control’s Size, the control’s appearance in the resulting report can differ from the expected result. |
How to Fix | Reduce the line width or increase the control size: select the control, switch to the Properties window, and set a smaller Line Width or a larger Size. |
XRE080
Message Text | The cross tab field is invalid |
Message Type |
|
Why the Message Appears | When you bind an XRCrossTab control’s cell to a data field that does not exist, the cell does not receive any data and the cross tab is displayed differently from an expected result. |
How to Fix | Ensure that the cross tab field is bound to a valid data field. Expand the report’s smart tag and click Edit Bindings. In the invoked Edit Bindings dialog, check that all cross tab cells are bound to valid data fields. |
XRE081
Message Text | The parameter’s binding is invalid |
Message Type |
|
Why the Message Appears | When you bind an XRCrossTab control’s parameter to a data field that does not exist, the parameter does not receive data. |
How to Fix | Ensure that the parameter is bound to a valid data field. Expand the Cross Tab control’s smart tag and click the Parameters property’s ellipsis button. In the invoked Collection Editor, specify a valid binding for the Cross Tab’s parameter. |
XRE090
Message Text | No region is specified for the summary |
Message Type |
|
Why the Message Appears | A control that displays a summary needs to know if the summary should be calculated within a page, group, or an entire report. |
How to Fix | Specify where to calculate the summary: select the control that displays the summary, expand the smart tag, and set Summary to Page, Group, or Report. |
XRE091
Message Text | No group fields are specified for the group summary |
Message Type |
|
Why the Message Appears | A control that displays a summary needs to know which data field to use to calculate the summary. These fields should be specified in a Group Header or Group Footer band. |
How to Fix | Specify group fields in the band that contains the summary control. As an alternative, move the control that displays the summary to a group header or group footer band that has group fields. |
XRE092
Message Text | The Detail band does not display data to use for the page summary |
Message Type |
|
Why the Message Appears | The calculated page summary is based on the data displayed. If no data is displayed, the summary is not calculated. |
How to Fix | Ensure the Detail band displays data. Add controls to the Detail band and bind these controls to data source fields. |
XRE093
Message Text | Summary Running for the control is set to the Report | Group | Page value, but the expression has no summary functions. |
Message Type |
|
Why the Message Appears | The Summary Running property specifies that the control should display a summary value within a report, group, or page. The Text property’s expression should include a summary function that calculates the summary value to be displayed. If you do not intend to display summary values in the control, set Summary Running to None. |
How to Fix | Select the control, switch to the Properties window, and add a summary function (for instance, sumSum) to the Text property’s expression, or set Summary Running to None. |
XRE100
Message Text | The query’s parameter binding is invalid |
Message Type |
|
Why the Message Appears | When you bind a query parameter to a data field that does not exist, the parameter does not receive data. This issue commonly appears in reports generated in program code, as the Report Designer does not allow users to specify non-existing fields. |
How to Fix | Ensure that the query parameter’s binding is valid. Right-click the data source in the Field List and select Manage Queries. In the invoked Manage Queries dialog, click the query’s ellipsis button, and then click Run Query Builder in the Query Editor. Click Edit Parameters in the Query Builder dialog and specify a valid value for the query parameter. |
XRE101
Message Text | The query parameter type does not match the report parameter in the query |
Message Type |
|
Why the Message Appears | When you bind a query parameter to a data field of a type that cannot be converted to the parameter’s type, the parameter does not receive data. This issue commonly appears in reports generated in program code, as the Report Designer does not allow users to specify fields of non-matching types. |
How to Fix | Ensure you bind the query parameter to data of the appropriate type. Right-click the data source in the Field List and select Manage Queries. In the invoked Manage Queries dialog, click the query’s ellipsis button, and then click Run Query Builder in the Query Editor. Click Edit Parameters in the Query Builder dialog and specify a valid value for the query parameter. |
XRE110
Message Text | The PDF does not contain the specified page |
Message Type |
|
Why the Message Appears | The XRPdfContent control cannot display PDF content that does not contain the page(s) specified in the control’s Page Range property. |
How to Fix | Ensure that the PDF contains the specified pages: select the control, switch to the Properties window, and specify a valid page range in the Page Range property. |
XRE230
Message Text | Some elements of your document overlap and thus can be exported to Excel format incorrectly. |
Message Type |
|
Why the Message Appears | If your report contains overlapped controls, the report document will contain overlapped elements (bricks) generated from these controls. Such elements might produce merged cells and extra columns/rows in the exported Excel file. If the Report Design Analyzer identifies that such incorrect export might occur for the document, the analyzer displays the error message. |
How to Fix | If possible, modify your report layout such that the report document does not contain overlapped elements. Refer to the following troubleshooting guide for instructions: Export to Excel - Overlapped Controls (Troubleshooting). |
XRE270
Message Text | Some elements of your document span across several pages and thus cannot be exported to RTF, DOCX, XLS, and XLSX format correctly with the specified export settings. |
Message Type |
|
Why the Message Appears | Some report controls might span across several pages in the report document. When you export the document to RTF, DOCX, XLS, or XLSX format, such elements might be displayed incorrectly with some export settings. If the Report Design Analyzer identifies that such incorrect export might occur, the analyzer displays the error message. |
How to Fix | If possible, try to use Single File mode when you export your document to RTF, DOCX, XLS, or XLSX format. |
XRE900
Message Text | The Report Design Analyzer has crashed |
Message Type |
|
Why the Message Appears | An exception occurred, and the Report Design Analyzer could not continue to operate correctly. |
How to Fix | Do one of the following:
|