Troubleshooting Problems with Scheduled Reports

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:

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:

  1. 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.

  2. Run Scheduler Diagnostics reports to list any exceptions that occurred.

    SeeRunning Scheduler Diagnostics Reports.

  3. Once you see what the exception is, try one of the recommended solutions to the problem.

    See .Possible Solutions to Report Scheduler Exceptions.

  4. If an unknown Report Scheduler exception occurred, view the Vocera Report Server log file to see the root cause of the exception.

    See Viewing the Vocera Report Server Log.