Skip to main content
Share / Export

Monitoring and Troubleshooting TERA

Use Scheduler Center and Run History to see what is next, what failed, and what to fix. This article covers day-to-day monitoring and the failures teams hit most often.

Where to look first​

  • Scheduler Center — License, Service, Active Schedules, Needs Attention, Up Next, Available Reports, Recent Runs.
  • Run History — Status, errors, email status, open/reveal output, cancel queued/running runs.
  • C:\ProgramData\TERA\logs\ — Windows Service logs when the UI message is not enough.

Scheduler Center overview with metrics, Up Next, Needs Attention, and Recent Runs

Scheduler Center checklist​

  1. Open Scheduler Center.
  2. Confirm Service is connected (not Offline).
  3. Confirm License is active and allowed to run schedules.
  4. Check Active Schedules counts match what you expect enabled.
  5. Review Up Next for upcoming rule times.
  6. Review Needs Attention for recent failures.
  7. Select Refresh after fixing the service or license.

Scheduler Center metrics row showing License, Service, Active Schedules, and Needs Attention

Up Next panel listing upcoming scheduled runs

Needs Attention​

Failed runs appear under Needs Attention with a short error summary.

  • Open History from the panel for full detail.
  • Use Archive on a card (or Archive all) to dismiss items from the attention list after you have handled them.

Archiving clears the attention list entry; it does not delete Run History by itself.

Needs Attention panel with failed run summary and Archive action

Run History​

  1. Open Run History.
  2. Find the run by schedule name, report name, or time.
  3. Read status and any error or email failure text.
  4. If an output exists, use Open Output File or Open File Location.
  5. For queued or running jobs, use Cancel Run if you need to stop them.
  6. Use Delete Run to remove a history row when appropriate.

Run History list with status, error or output detail, and action icons

Healthy vs unhealthy signals​

  • Healthy: Service connected, license active, Up Next populated for enabled schedules, Recent Runs succeeding, Needs Attention empty or only archived noise.
  • Unhealthy: Service offline, license not activated / cannot run, schedules enabled but never appearing in Up Next, repeated failures in Needs Attention, exports missing with failed status.

Troubleshooting by symptom​

Could not reach the local service / Service Offline​

  1. Open Windows Services and confirm the TERA scheduler service is Running.
  2. Start the service if it is stopped.
  3. Return to TERA and select Refresh on Scheduler Center.
  4. If it still fails, check C:\ProgramData\TERA\logs\ and that nothing else is blocking local port communication to the service.

Windows Services showing TERA service stopped or running

License blocks runs​

  1. Open Settings → License.
  2. Confirm Status / Plan / Valid until.
  3. Select Verify license (requires network access to tuds.ai).
  4. If the plan caps active schedules, disable unused schedules or upgrade—Add Schedule may show remaining capacity.

License Status panel with Verify license when subscription is inactive or expired

Schedule never runs​

  • Schedule Enabled is checked on Report & Output.
  • At least one Timing rule exists and is Enabled.
  • Windows Service is running (desktop app alone is not enough).
  • Rule time is in the future relative to the system timezone shown in the schedule form.
  • License allows scheduled runs.

Check Up Next after saving. If the schedule never appears there, fix enablement/rules/service before waiting on the clock.

Manual Execute / Run Now fails​

  • Default output folder missing on the report (library Run Now / Execute stay disabled or warn).
  • Crystal Reports runtime not installed on this machine.
  • .rpt path or output folder not readable/writable by the Windows Service account.
  • Database connection wrong or credentials expired—retest under Settings → Database.
  • Required parameters blank or invalid—fix Discover Metadata and defaults.

Read the failure text in the run message or Run History, then confirm a file appears after a successful retry.

File exported but email failed​

  • Retest SMTP with Send Test Email in Settings → Email.
  • Confirm Delivery mode is email-enabled and To / profile are set.
  • Check attachment size limits and SSL/TLS settings.
  • Run History often shows export success with an email failed detail—fix mail without redoing the whole report design.

Bursting problems​

  • SQL preview requires a saved schedule.
  • No mappings → every row may use the same parameter defaults.
  • Too many SQL rows → long sequential queues; tighten the query.
  • See Report Bursting in TERA for setup detail.

Discover Metadata fails or parameters empty​

  • Save the report on Setup before discovering.
  • Confirm database connection and Report ID for Vista enrichment.
  • Confirm the .rpt path is valid for the service account.

Log files and data locations​

  • C:\ProgramData\TERA\logs\ — Service and execution logs
  • C:\ProgramData\TERA\data\scheduler.db — Schedules, reports, history
  • C:\ProgramData\TERA\secrets\ — DPAPI-protected passwords
  • C:\ProgramData\TERA\temp\ — Temporary Crystal export files

When opening a support case, include the approximate run time, schedule/report name, Run History error text, and the matching log snippet.

File Explorer open to C ProgramData TERA logs folder

Quick recovery order​

  1. Service running?
  2. License active?
  3. Database connection tests OK?
  4. Report path + output folder OK? Crystal runtime installed?
  5. Schedule enabled with timing rules?
  6. SMTP test OK (if emailing)?
  7. Read Run History + logs for the specific error.
  • Getting Started with TERA — UI vs Windows Service
  • TERA Initial Setup — License, database, SMTP
  • Adding a Report in TERA / Adding a Schedule in TERA — Happy-path configuration
  • Email Delivery in TERA / Report Bursting in TERA — Delivery and fan-out