Skip to main content
Share / Export

TERA Initial Setup

Complete this setup once on the machine that will run TERA. When you finish, the service is connected, your license is active, SQL Server is ready for Crystal reports, and (optionally) SMTP is ready for email delivery.

Who should do this​

  • The person installing TERA on a workstation or report server.
  • Someone with a TERA license key and SQL credentials for the Vista database.
  • Someone who can provide SMTP settings if reports will be emailed.

Before you start​

  • TERA is installed and the desktop app opens.
  • The TERA Windows Service is running.
  • You have your license key.
  • You know the SQL Server name, database name, and login for Vista.
  • (Optional) You have SMTP host, port, from address, and credentials.

Step 1: Confirm the service in Scheduler Center​

  1. Open TERA.
  2. Go to Scheduler Center.
  3. Check the Service metric.
  4. If needed, select Refresh.

Expected outcome: Service is connected/online (not Offline). License may still show Not Activated until Step 2.

Scheduler Center with Service metric connected and License still not activated

If TERA cannot reach the local service, start the Windows Service from Services.msc, wait a few seconds, then refresh again.

Step 2: Activate your license​

  1. Open Settings.
  2. Select the License tab.
  3. In Activate License, enter your License key.
  4. Select Activate.

Expected outcome: License Status shows Status, Plan, and Valid until. Scheduler Center License metric updates from Not Activated.

Settings sidebar with License tab selected

Activate License panel with License key field and Activate button next to License Status

After activation, you can select Verify license anytime to refresh status from tuds.ai.

License Status panel showing Status, Plan, Valid until, and Verify license button

License notes​

  • An inactive or missing license blocks scheduled runs.
  • Your plan may limit how many active schedules you can enable (for example, Standard vs Professional).
  • Email delivery requires a plan that includes SMTP/email features.

Step 3: Add a database connection​

Crystal reports need a SQL Server connection at run time. Vista-aware parameter discovery and lookups also use this connection.

  1. In Settings, select the Database tab.
  2. Select Add Connection.
  3. Fill in:
    • Name — A friendly label (for example, Production Vista).
    • Server — SQL Server host or instance.
    • Database — Vista company/database name.
    • Username and Password — SQL login used for report execution and metadata.
  4. Select Test Connection.
  5. When the test succeeds, select Save Connection.

Expected outcome: You see a success message from the test, then Database connection saved. The connection appears under Edit Database Connection.

Settings Database tab empty state with Add Connection button

Add Database Connection form with Name, Server, Database, Username, Password, Test Connection, and Save Connection

Database connection test result showing Success message

Database notes​

  • Passwords are stored with Windows DPAPI under C:\ProgramData\TERA\secrets\, not as plaintext in the SQLite database.
  • Use a SQL account that can read the tables your Crystal reports need, plus Vista report/parameter catalog tables if you will use Report ID lookup and Discover Metadata.
  • You can add more than one connection if different reports use different servers or databases.

Skip this step if you will only save files to a folder. You can return later before enabling email delivery on a schedule.

  1. In Settings, select the Email tab.
  2. Select Add Profile.
  3. Fill in:
    • Name — Friendly label (for example, Company SMTP).
    • SMTP host and SMTP port (default port is often 587).
    • From email (required) and optional From name.
    • Username and Password/API key when your mail server requires authentication.
    • Use SSL/TLS as required by your provider.
    • Test recipient — An inbox you can check.
  4. Select Save Profile.
  5. Select Send Test Email.

Expected outcome: Success message that a test email was sent. Check the inbox for a message with subject related to TERA test email.

Settings Email tab empty state with Add Profile button

Add SMTP Profile form with host, port, from address, credentials, Use SSL/TLS, Test recipient, Save Profile, and Send Test Email

Step 5: Return to Scheduler Center and confirm readiness​

  1. Open Scheduler Center.
  2. Confirm License shows an active status.
  3. Confirm Service is connected.
  4. Active Schedules may still be 0/0 until you create schedules—that is expected.

Expected outcome: License and Service metrics look healthy. You are ready to register reports.

Scheduler Center after setup with License active and Service connected

Setup checklist​

  • Windows Service running; Scheduler Center Service metric connected
  • License activated (Status / Plan / Valid until visible)
  • Database connection tested and saved
  • (If emailing) SMTP profile saved and test email received

Common mistakes​

  • Activating license while service is offline — Fix the service first so status and limits refresh correctly.
  • Saving a database connection without testing — Always Test Connection before relying on Discover Metadata or scheduled runs.
  • Wrong database — Report ID lookup and Vista parameter defaults come from the connected Vista database; pick the same environment your .rpt files use.
  • Skipping SMTP until a schedule fails — If delivery mode includes email, configure and test SMTP before enabling the schedule.
  • Assuming closing TERA stops jobs — The Windows Service continues; use Services.msc if you need to stop automation.

Next steps​

  • Adding a Report in TERA — Register a .rpt, discover parameters, and Run Now.
  • Adding a Schedule in TERA — Automate timing, output, and delivery.
  • Email Delivery in TERA — Tokens, recipients, and schedule Delivery tab details.
  • Monitoring and Troubleshooting TERA — Service, license, Crystal, and SMTP failures.