Connection issues

Diagnose pairing, heartbeat, local Tally access, and company identity failures.

Pairing code rejected or expired

Generate a fresh code from Setup; codes expire after 10 minutes.
Enter all eight characters exactly.
Confirm the installer points to the stable Tally Connect cloud URL.
If the device was previously paired, revoke it before pairing a replacement.

Agent shows offline

Start TallyPrime as the same Windows user who installed the Agent.
Check the Talley Connect Agent scheduled task is running.
Run diagnose --json.
Confirm outbound HTTPS is allowed.
Restart the scheduled task, then wait for a fresh heartbeat.

Tally is unreachable

Confirm TallyPrime is running.
Enable its HTTP/XML interface on port 9000.
Verify no other application is using the port.
Do not substitute a LAN or public IP; the Agent requires 127.0.0.1.

Wrong or unloaded company

Load the bound company whose name and GUID appear in Setup. If the company is missing, run company discovery again. Never change a queued command to another company.

Company discovery returns nothing

Keep the company open in TallyPrime, confirm local XML access, run diagnostics, and retry discovery after the Agent is online. If multiple similar companies are loaded, use the GUID—not the display name alone—to select the intended one.