OneAnalytics docs

Tally gateway troubleshooting

The Tally gateway agent works reliably once set up, but Tally's ODBC server has a few quirks that surface as errors in OneAnalytics. Here are the common failure modes and their fixes.

"Tally must be open with a company loaded"

This is the #1 issue. Tally's ODBC server only listens while the Tally window is open with a company loaded. Close Tally → ODBC dies → gateway disconnects → refresh fails.

Fix:

  1. Open Tally.
  2. Load your company from the Gateway → Companies list.
  3. Keep it open during scheduled refreshes.

We recommend dedicating a low-spec always-on Windows machine to Tally for this reason. Auto-login + "start Tally on boot" via a scheduled task. The gateway agent itself is a Windows service and survives user logoffs, but Tally is a user app and doesn't.

"ODBC Server not running on port 9000"

Tally's ODBC is disabled by default after some upgrades. Re-enable:

  1. Tally Prime → F1 → Settings → Connectivity → ODBC Server → Yes.
  2. Port: 9000 (or match what's in the gateway config).
  3. Restart Tally.

Verify with Test-NetConnection -ComputerName 127.0.0.1 -Port 9000 — should be TcpTestSucceeded: True.

"Unknown ODBC field AlterID"

You're on a very old ERP 9 (pre-6.6.3). Upgrade to a supported build. Incremental sync relies on AlterID; without it we fall back to full refresh every time (slow but functional).

Refreshes hang at "connecting"

  • Firewall dropping the 9000 connection — add an inbound rule for 127.0.0.1:9000.
  • Antivirus intercepting — exclude the gateway's install directory (C:\Program Files\OneAnalyticsGateway\).
  • Gateway service not running — Services.msc → find OneAnalyticsGateway → Start.

"Enrollment token expired"

Tokens expire 15 minutes after generation. Regenerate from the OneAnalytics UI and paste again during installer rerun, or via:

& "C:\Program Files\OneAnalyticsGateway\oagw.exe" enroll --token <new-token>

Slow first sync

Mid-size companies (100k+ vouchers) take 5-15 minutes on first import. Tally's ODBC is not fast. Mitigations:

  • Run the first sync during off-hours.
  • Disable realtime virus scan on Tally's data folder (C:\Users\<user>\Tally\).
  • Temporarily close other Tally sessions on the same machine.

Character encoding issues (Hindi, Tamil)

Tally stores non-ASCII names in a legacy encoding. We detect and re-encode to UTF-8 at import. If you see mojibake like äçè, set the company locale explicitly in the gateway config: Gateway → Advanced → Tally locale → Hindi (mac-mangled).

Logs

Gateway logs: C:\ProgramData\OneAnalyticsGateway\logs\gateway.log. Rotating daily, 14-day retention. Attach to support tickets.

Still stuck?

Email support@analytics.rstglobal.in with the workspace ID, dataset ID, and a redacted snippet of the gateway log (last 200 lines). We'll get back within one business day.