Nearly every TDL problem comes down to one of five things: the wrong path, the wrong Tally version, a licence mismatch, a conflict with another add-on, or a file that never loaded at all. Work through the checks below in order.
Error: file not found or cannot open
Tally is looking at a path that no longer exists. Re-open the TDL configuration and paste the full path including the file name and extension. Avoid folders synced by cloud drives, which can lock the file.
The add-on loads but nothing appears
- Restart Tally — a newly added file only applies after a restart
- Confirm the add-on's menu location; many add-ons sit under a specific report or print screen, not the Gateway
- Check that the add-on is enabled in the TDL list (status Yes)
- Verify the build matches your Tally edition (TallyPrime vs ERP 9)
Compile or syntax errors
Uncompiled TDLs show a line-number error when the code does not match your Tally release. This usually means the add-on was written for an older release. Ask the developer for an updated build rather than editing the code yourself.
Licence or serial number errors
Commercial add-ons validate your Tally serial number. If you have re-activated Tally, changed machines or moved to a new serial, the add-on must be re-issued against the new number.
Two add-ons conflicting
If two add-ons modify the same report or print format, one may override the other. Disable all add-ons, then enable them one at a time and restart to find the clash. Once identified, the developers can usually merge the changes.
Still stuck?
Note your Tally release number, the exact error text and the add-on name, then contact the developer's support desk. Screenshots of the error and of the TDL configuration screen speed up a fix considerably.
Frequently asked questions
Why does my TDL stop working after a Tally update?
New Tally releases sometimes change internal objects. Request the updated build of the add-on; reputable providers supply updates free for the licence period.
Can a TDL corrupt my company data?
A read-only reporting add-on cannot. Add-ons that write data should always be tested on a backup copy first.