Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: TDEV-1180: Name TManageServices.exe explicitly in Configure and Automate sections; add service-only uninstall example

...

Service install options:

  • Designer UISolution Center has a button to install Runtime → Startup has an AutoStartup button that installs the runtime as a serviceWindows Service
  • Command-linescripted install with elevated PowerShell (see Runtime Startup Reference)use TManageServices.exe (located in the product root folder) from an elevated shell

Example: install the runtime as a Windows Service for a specific solution, unattended:

Code Block
languagepowershell
cd "C:\Program Files\Tatsoft\FrameworX"
.\TManageServices.exe /installtstartup `
    /solution:"C:\Users\Public\Documents\FrameworX\Solutions\Plant1.tproj" `
    /silent

# Uninstall later
.\TManageServices.exe /uninstalltstartup /solution:"Plant1" /silent

TManageServices.exe also handles TWebServices, TSecureGateway, TMQTTBroker, THardkey, and RuntimeMCPHttp. Run TManageServices.exe /? for the full command list. The /silent flag makes it script-friendly: it never pauses for input and returns a non-zero exit code on failure. Full reference: Runtime Startup Reference.

Run the service under a dedicated domain account where possible. The account needs:

...

The uninstaller removes the installed executables, the Windows Service registration, and the registry entries. User content under C:\Users\Public\Documents\FrameworX\ is preserved — remove manually if you want a fully clean uninstall.

To remove only the installed Windows services (without removing the product files), use:

Code Block
languagepowershell
cd "C:\Program Files\Tatsoft\FrameworX"
.\TManageServices.exe /removeallservices /silent

7. Secure

Production deployments should follow the hardening checklist. Topics include TLS configuration, authentication (local users, Windows authentication, Active Directory), role-based access control, secrets storage, audit logging, and network segmentation.

...

  • SCCM / Intune — package the silent installer as an application deployment with the switches shown in section 2. Use exit code 3010 as a soft-reboot signal.
  • PowerShell DSC / Ansible / Chef — wrap Start-Process with the silent switches and check exit codes for the product installer; use TManageServices.exe /silent for service install/uninstall steps.
  • Solution deployment — copy the .dbsln solution file to the target server's Solutions folder, then start run TManageServices.exe /installtstartup /solution:"<path>" /silent to install the runtime as a service. Solutions are self-contained.
  • Bulk uninstall — call unins000.exe with silent switches across a fleet, or TManageServices.exe /removeallservices /silent to clean services only.

9. Troubleshoot

Symptom

First place to look

Service won't start

Windows Event Log (Application) for service source, then TraceLogs folder

Port conflict

netstat -ano to find what's on the port; change port in Runtime Startup config

License error

Event Log source FrameworX, then Licensing Procedures Reference

Client can't connect to runtime

Firewall rule on runtime port, Test-NetConnection from client, runtime client-server logs

Web client blank / auth error

TLS certificate validity, browser console, Web Server Configuration Reference

Database connection fails

Service account permissions, connection string, firewall rule to DB server

...