Errors When Generating Crystal Reports

[sbeadle1]

📖 Home  Back  
There are a number of different errors that can be returned when Generating a crystal report. The exact text of the error message can be found in the event journal. These are typically strings returned directly from the Crystal Reports APIs.

Table Not Found

The error shown is "Generate report request failed - Failed to generate report, The table '' could not be found..."

This error is displayed when the table referenced in the report is not defined within the ClearSCADA database schema. This most often happens when the table being queried is a historic view or data grid which has not been defined, or named incorrectly. To resolve this issue, either change the name of the table in ClearSCADA, or change the Crystal report to reference the table name correctly.

Data Not Constrained

The error shown is "Generate report request failed - Failed to generate report, Failed to retrieve data from the database..."

This error is displayed when the database link is unable to provide data to Crystal reports. The most common cause of this is when data is queried from a historic table an insufficient constraints are placed on the data set being requested. For example, when querying the CDBHistoric table (or a historic view) it is important to constrain the query by time ie. specify a WHERE clause that limits the amount of records being returned.

For a query on a historic view, it is also important to link the report to also retrieve point information from the CDBPoint table as well as the historic data from the historic view.

No Interface to Driver

The error shown is displayed in a popup inside ViewX stating "InvokeMethod returns 0XC0140026. No interface to driver."

This will be followed up with an event in the event journal stating "Generate report request rejected - Driver 'Crystal Reports' is not running".

This error is displayed when you have requested to generate, export or print a report when the Crystal Reports driver is not running.

Some causes of the driver not running include:

• driver failing on startup due to an invalid printing user

• licence not configured for Crystal Reports (Crystal Reports is a free driver. If this is the case, please contact your support representative for an updated licence).

• driver connection to server failed. This could be due to a resource issue on the machine ie. some other application using up all available TCP sockets.

To view the status of the driver, browse to the Modules window of the server status dialog.

Failed Logon

Each Crystal Report can be configured with a user that is used to logon to the system to access the required data. If this logon is incorrect, or the user has no permissions in the system, an error stating 'Generate report request failed - Failed to generate report, Logon Failed...'

To resolve this issue, modify either the users security permissions to allow them to access part of the system, or check that the report user is still valid in the system.

Incorrect DSN Configuration

ClearSCADA uses a standard ODBC Data Source Name (DSN) configured in the Windows control panel to connect to the database and retrieve information required for the report. If the configured DSN does not match the name of the DSN configured in the Global Parameters - Crystal Reports section of the ClearSCADA Server Configuration dialog, then an error stating 'Generate report request failed - Failed to generate report, Failed to open the connection...' will be displayed.

The obvious solution to this problem is to ensure that the configured DSN matches the name of the DSN configured in ClearSCADA.

Note that if the DSN configured in ClearSCADA is modified to match an existing ODBC DSN on the machine, either the Crystal Reports driver must be restarted to pick up this change.

Go: Home Back