If Tally Prime stops working, do two things before anything else: stop entering vouchers, and make a copy of your company data folder somewhere safe. Troubleshooting is easier and far less risky once a backup exists. After that, write down the exact message on screen, because the wording decides whether the cause is the licence, the data, the computer or something else. we cannot describe the product's menus or policies, so use the vendor's help pages or your authorised service provider for product-specific steps.
Why come before the fix: what should you back up?
Copy the whole data folder for the affected company to a pen drive or another drive, not just a single file, and keep the original where it is. Do not delete, rename or reinstall anything until the copy is confirmed readable. If you already have a routine backup, note its date and time so you know how many entries could be lost if a repair goes wrong.
How do you narrow the problem down?
| What happens | Likely area | Sensible first step |
|---|---|---|
| Will not open at all | Installation, computer or licence | Restart the PC, check free disk space, note any message |
| Opens but one company fails to load | That company's data | Try a different company; if others open, the issue is in the data |
| Slow, freezes while saving | Disk, network or very large data | Check disk health and free space; test on one machine |
| Error on a shared network | Network or permissions | Check that the server machine is on and the folder is reachable |
| Wrong totals after an import | Imported file | Compare with the source and undo from your backup |
What should you note down for support?
- The exact error text, ideally a screenshot of the whole screen.
- What you were doing a moment before: saving a voucher, opening a report, importing a file.
- Whether it affects one company or all of them, one computer or all of them.
- The date and time of your last good backup.
- Any change made recently: a Windows update, a new antivirus, a moved folder.
Worked example: a loss you can measure
Say a small shop enters about 40 vouchers a day and the last good copy was taken on Monday evening. The problem appears on Thursday afternoon. If nothing can be recovered, the rework is Tuesday, Wednesday and half of Thursday, roughly 40 + 40 + 20 = 100 vouchers. If a copy is also taken every evening, the worst case drops to Thursday's 20. That arithmetic is why a daily end-of-day copy, which takes a minute, is worth more than any clever repair later.
Is the fault in Tally, or in what you put into it?
If the trouble began after you imported entries, check the source file first. Missing ledgers, mismatched names and unusual dates are common causes of failed imports, and they are quicker to fix at the source than inside the books. SpendixAI has an Export centre with a template for Tally, so categorised expenses can be exported in a format meant for it. Treat the first export as a test: load a handful of rows into a duplicate company, compare totals, and have your accountant confirm the ledger mapping before using it for real.
What habits prevent the next scare?
- Take an end-of-day copy to a second drive, and a weekly copy somewhere off the premises.
- Test a restore once, so you know the copy actually opens.
- Keep Windows updates and antivirus changes away from month-end and filing weeks.
- Keep the licence details and the support contact in a safe, known place.
- Close the program properly instead of switching the computer off.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

