Symptoms

Report Commander returns the following error message when you try to open a report in the Command Line Builder or to process the report from the command line:

Cause

This is a generic error message returned from the Crystal Reports runtime components used by Report Commander whenever it encounters a problem loading the report file. Unfortunately the Crystal Reports runtime does not return additional information about the problem, making it difficult to diagnose the cause. This article discusses some possible causes for the error.

Report was created using an older version of Crystal Reports

This message is common when you try to use Report Commander with a report that was created in Crystal Reports 8.5 or earlier. The report file structure and database drivers changed significantly between Crystal Reports 8.5 and 9.0, and as a result the newer runtime components used by Report Commander often cannot read the report, even though the Crystal Reports designer can. Because of this, Arcana Development does not support the use of Report Commander with reports created by Crystal Reports 8.5 or earlier (this is noted in the system requirements for Report Commander).

Older Crystal Reports files are still quite common, especially if you are using a report provided as part of another application.

If you have access to a newer version of Crystal Reports (version 9.0 or later), you can generally convert your report file to the newer format so that it can be used with Report Commander. To do this:

1. Open the report in the newer version of Crystal Reports.
2. Use the Verify Database command to ensure that the database driver is updated and the data can be retrieved.
3. Preview the report to make sure that it works correctly.
4. Save a copy of the report under a new name and use this copy with Report Commander.

Important: If the report is being used by another application, be sure to save a copy of the report under a new name. If you overwrite the original report file with the updated format, the other application that uses the file may not be able to open the file.

Report uses User Function Libraries

The error may occur if your report uses functions in a user function library (UFL), and the UFL (or one of its dependencies) is not present on the computer where you are running Report Commander. See article K00000279 for more information on this scenario.

Report uses non-standard database driver

The error may occur if your report uses a non-standard database driver and that driver is not installed on the computer where Report Commander is running. Make sure all the necessary files for your database driver are present on the computer.

Report file name is wrong, or file is inaccessible

This error may occur if you have specified an invalid report file name on the Report Commander command line, or if the report is on a drive or network resource that is inaccessible.

If Report Commander is being run from a scheduler or automation tool, be sure that the account being used to run Report Commander has access to the report location.

If the path contains a mapped drive letter, make sure that drive letter has been mapped for the logon session in which Report Commander is running, or use a UNC path to refer to the file instead.