Possible Solutions to Report Scheduler Exceptions

This section lists common Report Scheduler exceptions you may encounter and possible solutions you can use to correct the problem.

Report Scheduler Exception

Possible Solution or Workaround

The report cannot be exported. The export operation failed.

This error could occur with a report whose parameters have changed due to a Report Server service pack being applied after you added the report to the package. If so, edit the report parameters, making sure all values are specified. If you see a parameter with a question mark (?) for its value, select an appropriate value for the parameter.

This error could also occur with a custom report that has been configured incorrectly in the customconfig.xml file. Check to make sure report parameters have been specified correctly. For more information about configuring custom reports, see the Vocera Report Server Database Schema Guide.

The report cannot be exported because it contains no data.

Change the report date range or other parameters (for example, Site and Department) so that the report includes data.

The package is more than 30 minutes late. It is queued for firing.

The package cannot run until the dataload is finished. Change the scheduled run time of the package so that it occurs after a scheduled dataload is finished.

A report cannot be generated because it is disabled within the package.

Modify the package and make sure the report is enabled.

The report cannot be generated because it is past the end date for the package schedule.

If you don't want the package schedule to end, leave the End Date field on the Schedule Information tab of the package empty.

The reports could not be copied to the desired location.

Make sure the hard disk is functioning and has space available.

The schedule is disabled for the package.

Open the package, select the Info tab, and make sure the Enabled check box is checked.

There were problems in reading email addresses.

Make sure email addresses specified in the mailing list or package recipients are valid.

There were problems in sending emails to addresses.

If you selected users or groups as recipients, make sure they have email addresses specified.

The email sending process failed.

Make sure the outgoing mail server is specified correctly. In the Report Console, click Administration, and then click the Mail Info tab. Click Test Mail Server to send a test message to the alert recipient email address.

The zip file size for reports exceeded the given limit.

To make the reports smaller in size, make the date range smaller, or filter the reports by site or department. Otherwise, increase the maximum zip file size.

The report query failed to execute.

If the package includes a custom report, the report may not have a valid SQL query. Make sure you test all custom reports before deploying them on a production server.

One or more database operations failed.

Make sure MySQL is running properly. If necessary, restart the computer.

You tried to run a package that was already running.

A package cannot be run multiple times simultaneously. Therefore, do not manually run a package during the time it is scheduled to launch.

The disk destination list is empty.

Although the package specifies a disk destination by name, it does not contain a destination. Make sure the disk destination is correct.

The specified destination does not exist.

Make sure the disk destination folder exists. If the folder is on another server and it is not shared, Vocera Report Server does not have rights to it.

The specified destination does not have write permission.

Make sure Vocera Report Server has write access to the disk destination. See Giving Vocera Report Server Access to Other Network Servers.

An unknown exception occurred.

Open the latest Vocera Report Server log file in the \Tomcat\logs folder to find the root cause of the exception.