BusinessObjects Enterprise Administrator's Guide
Troubleshooting reports with Crystal Reports
On Windows, you can install Crystal Reports on all Job Server, Page Server, and RAS machines in order to speed up the troubleshooting of reports and database connectivity. In this way, you use Crystal Reports to simulate the steps that are performed by the BusinessObjects Enterprise processing servers when a scheduled report is processed, or when a report is viewed on demand over the Web. By locating the step where Crystal Reports is unable to open, refresh, or save the report, you may be able to locate the source of the problem.
Note: The exact steps and menu options may differ, depending on your version of Crystal Reports.
To troubleshoot a report
- Start Crystal Reports on the appropriate machine:
- If the report runs successfully on demand, but fails when scheduled, start Crystal Reports on the Job Server.
- If the report fails when viewed on demand, but runs successfully when scheduled, start Crystal Reports on the Page Server.
- If the report fails when viewed on demand with the Advanced DHTML viewer, start Crystal Reports on the RAS.
- If the report fails in all cases, first complete these troubleshooting steps on one processing server; then verify whether or not the problem is resolved on all processing servers. If not, repeat the steps on a different processing server.
- Open the report from the CMS.
On the File menu, click Open. Click Enterprise Folders and log on to your CMS. If you cannot open the report, verify network connectivity between the server you are working on, the CMS, and the Input File Repository Server.
- Test your database connection and authentication.
On the Database menu, click Log On/Off Server. If you cannot log on to the database server, check the configuration of the database client software and ensure that the report contains a valid database user name and password.
- If the report's parameters or record selection need to be modified by BusinessObjects Enterprise users when they schedule or view the report, change the parameter values or record selection formula accordingly. If the values are invalid, Crystal Reports will report an error.
- Verify that the tables used in the report match the tables in the database.
On the File menu, clear the "Save Data with Report" check box. On the Database menu, click Verify Database. Correct any issues reported by Crystal Reports, and then save the report.
- Refresh the report and, if current data is not returned from the database, check these possible causes:
- If the report fails, ensure that the database credentials provide READ rights to all tables in the report.
- If the database credentials are valid, the report's SQL statement is evaluated at this time. Check the join information. Note any ODBC errors that are produced.
- If the SQL statement is valid, data begins to return to Crystal Reports. As this happens, the temporary files increase in size. Verify resource allocation in case the machine is running out of memory or disk space.
- Go to the last page of the report.
Crystal Reports will report any errors that it encounters within the report (such as formulas, subreports, and other objects).
- Export the report to Crystal Reports format (or any other desired format).
This step ensures that Crystal Reports is able to create temporary files that are required in order to complete the processing of a report.
- If the report now refreshes successfully, save it back to the CMS.
- Close the report.
- Close Crystal Reports.
- Repeat the activity that caused the original report to fail: view the report on demand over the Web, or schedule the report for processing.
Related topics: