OptiVida cannot reach Tally
The Connector is running but Tally is not answering, or it has the wrong company open.
The Connector is running, but Tally is not answering — or it has the wrong company open.
"Tally is not reachable — open the company in TallyPrime and try again"
The Connector reached out to Tally and got nothing back.
Work through these in order
Is Tally actually open?
On the same computer as the browser you are using. Not on a server, not on the machine next door.
Is a company loaded?
Tally open at its own start screen with no company loaded looks identical from outside to Tally being closed.
Is connectivity switched on?
F1SettingsConnectivity — acting as Both, Enable ODBC set to Yes, port 9000. This is the usual answer.
Test it from the Connector
Open the Connector, go to Settings, then Tally, and choose Test the connection. It pings Tally there and then.
Is something else holding port 9000?
A second Tally instance is the usual culprit. Only one can hold the port.
Tip
The connectivity settings are covered in full at Turning on connectivity in Tally.
"Tally has [another company] open, expected [your client]"
Tally is answering perfectly well — with the wrong entity's books.
Load the right company in Tally and fetch again.
Warning
OptiVida refuses the fetch rather than reading whatever company happens to be open. That is the behaviour you want: a set of statements or an audit report built on another entity's books is the worst kind of error to discover late.
If the company names genuinely differ — the client is recorded under a trading name and Tally holds the legal name — link the client to the Tally company so the check matches in future.
What to do meanwhile
Nothing is lost. Your report is exactly as you left it, and fetching again when Tally is ready picks up from there.
For a CMA report you can carry on entering figures by hand and fetch later. For statements and tax audit the fetch has to succeed before there is anything to review.
Still not answering
Attach the Connector's log to a support query — it records each attempt to reach Tally and usually settles this in one exchange.
Last updated 31 Aug 2026
Still stuck? Ask us