Skip to main content
Share / Export

Getting Started with TERA

This guide orients you to TERA so you can install it, understand how it runs, and know where to go next for your first scheduled Crystal Report.

What is TERA?​

TERA (Timed Enterprise Report Automation) is a local Windows application that schedules existing SAP Crystal Reports (.rpt) files—especially Vista ERP reports—exports them (PDF, Excel, CSV), optionally emails the output, and keeps run history on your machine.

TERA is not a cloud reporting platform. Report files, SQL credentials, schedules, outputs, and history stay on the customer-controlled Windows machine or server. License validation uses tuds.ai.

How TERA is built (important)​

TERA has two parts that work together:

  • Desktop app (TERA) — Configure reports, schedules, database connections, email, and licensing. Monitor upcoming runs and history.
  • Windows Service — Owns scheduling and Crystal execution. This is what actually runs reports on a timer.

Closing or minimizing the desktop app does not stop scheduled reports. Only stopping the Windows Service stops automation. By default, closing the window minimizes TERA to the system tray; the service keeps running either way.

TERA Scheduler Center showing License and Service status metrics at the top

Before you begin​

  • Windows 10 or 11 (64-bit) on the machine that will run reports (often a server).
  • Prerequisites installed (the TERA installer typically prompts for missing ones):
    • .NET 8 Desktop Runtime (x64)
    • .NET Framework 4.8
    • SAP Crystal Reports runtime (64-bit)
    • Microsoft ODBC Driver 17 or 18 for SQL Server
  • A TERA license key from your purchase or TUDS team licensing.
  • SQL Server access to the Vista database used by your Crystal reports.
  • SMTP details if you plan to email report output (can be configured later).
  • At least one working .rpt file and a folder where exports can be written.

Install TERA​

  1. Run the TERA installer on the Windows machine that should execute reports.
  2. Complete the installer prompts. Allow it to install prerequisites if offered.
  3. Confirm the TERA Windows Service is installed and started (Services.msc → look for TERA / Crystal Scheduler service).
  4. Launch the TERA desktop app.

Expected outcome: TERA opens and can reach the local service.

Windows Services list with the TERA scheduler service shown as Running

TERA desktop app first open with sidebar navigation visible

Confirm the service is connected​

  1. Open Scheduler Center (home screen).
  2. Check the Service metric at the top.

Expected outcome: Service shows a connected/online status (not Offline).

If the service is offline, you may see errors such as being unable to reach the local service. Start the Windows Service, then select Refresh in Scheduler Center.

Scheduler Center metrics row highlighting Service status as connected

Learn the main areas​

Use the left sidebar to move between TERA’s main screens:

  • Scheduler Center — License and service status, active schedules, up next, needs attention, available reports, recent runs.
  • Report Library — Register Crystal Reports, discover parameters, run a report now.
  • Schedules — Create timing rules, parameter overrides, output format, and delivery.
  • Run History — Review completed, failed, and in-progress runs; open output files.
  • Settings — License, Email (SMTP), Database, and Theme.

TERA left sidebar with Scheduler Center, Report Library, Schedules, Run History, and Settings

Where TERA stores data​

On a normal install, TERA uses:

  • C:\ProgramData\TERA\data\scheduler.db — Schedules, reports, and run history (no plaintext passwords).
  • C:\ProgramData\TERA\secrets\ — DPAPI-protected database and SMTP passwords.
  • C:\ProgramData\TERA\logs\ — Windows Service logs (useful when a run fails).
  • C:\ProgramData\TERA\temp\ — Temporary Crystal export files.

Lock down C:\ProgramData\TERA so only administrators and the service account can access it.

Window close behavior​

In Settings → Theme, you can choose what happens when you close the TERA window:

  • Minimize to tray (default) — Hides the window; TERA stays in the system tray.
  • Close — Exits the desktop app. The Windows Service still keeps running schedules.

Settings Theme tab showing Minimize to tray and Close options

  1. Complete Initial Setup (license, database connection, optional SMTP).
  2. Add a report in Report Library, save it, discover metadata, and Run Now once.
  3. Add a schedule with a near-term timing rule and confirm it appears in Scheduler Center → Up Next.
  4. Confirm the run in Run History and open the output file.

Use the related TERA articles for each of those steps.

Common mistakes​

  • Thinking the desktop app is the scheduler — Scheduled runs belong to the Windows Service.
  • Skipping Crystal runtime — The app can open without it; report execution fails without it.
  • No license activated — Scheduling and delivery stay locked until you activate a key in Settings → License.
  • No database connection — Reports need a SQL connection to log into Crystal tables and resolve Vista parameter metadata.

Next steps​

  • TERA Initial Setup — Activate license, add SQL, add SMTP.
  • Adding a Report in TERA — Register your first .rpt.
  • Adding a Schedule in TERA — Automate export and delivery.
  • Monitoring and Troubleshooting TERA — When something fails.