The Report Scheduler is a sophisticated scheduling engine that has several dependencies on other systems, both internal and external to Vocera Report Server. For example, it depends on the following things to operate successfully:
The outgoing mail server information must be specified correctly, and the mail server must be running.
Disk destinations used by packages must be valid and accessible by the Vocera Report Server
Mailing lists and email addresses for recipients must be defined correctly.
Reports must have valid queries, and the resulting output must contain data.
These are only some of the dependencies that the Report Scheduler relies upon. Therefore, when a package fails to run at its scheduled time it could be due to several reasons. This section provides guidelines on how to identify and solve problems with scheduled reports.
To troubleshoot problems with scheduled reports:
Always run a report package manually before enabling the package schedule to run it automatically. See Running a Report Package.
When you run a package manually, you can see immediately if there are any problems. Make sure the correct reports are generated using the specified parameters, and make sure the reports are sent to the correct mailing list or disk destination.
Run Scheduler Diagnostics reports to list any exceptions that occurred.
Once you see what the exception is, try one of the recommended solutions to the problem.
If an unknown Report Scheduler exception occurred, view the Vocera Report Server log file to see the root cause of the exception.