Troubleshooting reports

Several common problems can occur when users try to preview or print a report. These are some of the more common ones with possible solutions:

• Reports do not print.

  See Troubleshooting: Reports do not print.

• Scheduled reports do not run as scheduled.

  See Troubleshooting: Scheduled reports do not run as scheduled.

• Report outputs do not pick up header/footer variable values.

  See Troubleshooting: Report outputs do not pick up header/footer variable values.

• The report generates a "File not found" error message.

  See Troubleshooting: File not found.

• Users outside the network are not receiving forwarded reports.

  See Troubleshooting: Users outside network not receiving forwarded reports.

• Labels are not being replaced with Strings table values.

  See Troubleshooting: Labels not being replaced with Strings table values.

• No report output is found.

  See Troubleshooting: No report output.

• Reports fail intermittently with errors

  See Troubleshooting: Intermittent failures with errors.

• Reports fail with an error code.

  See Troubleshooting: Reports fail with error code.

• Notes do not print with a report.

  See Troubleshooting: Notes do not print.

• Report gets an Error 13 - Type Mismatch.

  See Troubleshooting: Error 13 - Type Mismatch.

• Report gets an Error 128 - Error Running Report.

  See Troubleshooting: Error 128 - Error Running Report.

• Report gets an Error 534: Error Detected by Database DLL.

  This is similar to and has the same possible solutions as a "File not found" error. See Troubleshooting: File not found.

• Running a report produces the error: "This field name is not known."

  See Troubleshooting: This field name is not known.

• No users are receiving email messages about background tasks (including reports).

  See Troubleshooting: No users are receiving email messages.