Try OpenEdge Now
skip to main content
Alerts Guide and Reference
Alerts Reference : ReportRunFailed
 

ReportRunFailed

This section identifies the specific message-related text that can appear, indicating a report run has failed. Scan the messages presented in this section to find the one matching the message you received.
To obtain more details related to a report instance for which any ReportRunFailed alert appears:
1. Click Reports. Then choose Defined Reports in the list frame.
2. Select the report instance name in the list frame and display the report definition in the edit mode in the detail frame.
3. Select the Generate debug log file option, resubmit, and rerun the report. It is possible that more log files will display. You can use this data to further investigate your problem.
For more information about reports, see OpenEdge Management: Reporting.

Message

"Output directory not created: <output directory>."

Description

The report engine could not create the necessary directories to store the report output. Check the file system for privileges.

Action

Check the file system for privileges.

Message

"4GL execution error, exit code <return code>. See log files."

Description

The report did not run to completion because of an ABL issue. See the Report Output file (report.out) and the AdminServer log file (admserv.log) for more information.

Action

See the report output log files.

Message

"Graphing request xml file does not exist."

Description

The report failed to complete because there was a problem creating a graph for the report. The _graph.xml file is missing from the report output.

Action

See the log files.

Message

"Report output xml does not exist."

Description

The report failed to complete because the _data.xml file was not created.

Action

See the log files.

Message

"Error writing output file for report. See log files."

Description

There was an I/O error when generating the output file for the report.

Action

See the log files.

Message

"Transformation error. See log files."

Description

The report engine uses XSLT to create the various output formats from the _data.xml. There was an error transforming the XML file to one of the desired output formats.

Action

See the log files.

Message

"Transformation error for HTML output. See log files."

Description

There was an error transforming the data XML file into HTML output using XSLT.

Action

See the log files.

Message

"Transformation error for text output. See log files."

Description

There was an error using XSLT to transform the data XML file into text output.

Action

See the log files.

Message

"SAX parsing error. See log files."

Description

The report failed due to an error parsing an XML file. See the Report Output file (report.out) and the AdminServer log file(admserv.log) for more information.

Action

See the Report Output file (report.out) and AdminServer log file (admserv.log) for more information.

Message

"Graphing error. See log files."

Description

The report failed because the graphing engine had an error producing a graph for the report. See the report output and AdminServer log files (admserv.log) for more information regarding the error.

Type

Asynchronous

Action

See the Report Output file (report.out) and AdminServer log file (admserv.log).

Message

"XSL stylesheet not found: <filename>."

Description

The report failed because it could not find the specified XSL stylesheet to use in transforming the data XML to another output form.

Action

Ensure that the stylesheet is available in the following subdirectory location: OpenEdgeManagement-install-dir/web/report/xsl.

Message

"Report transformation ran out of memory."

Description

The reports use XSL transformations to generate the HTML and text output formats from the XML output that ABL creates. The XML file was too large for the report engine to transform the file, thus the engine ran out of memory. If the report period and/or report format was modified so there is less data in the XML file, the report output will be smaller and the engine will more likely be able to process the file in the amount of memory allotted.

Action

Try reducing the number of columns or rows in the report output by changing the report period or report format.