Pages of random symbols are not a mystery - they are the printer telling you the job arrived in a language it does not understand. The ladder below finds which layer is lying, in the right order.
Few sights panic an accounts team like an invoice printer pouring out pages of random characters - or the opposite, blank page after blank page. Random changes waste hours. This six step ladder isolates the faulty layer with certainty, one test at a time.
Before touching the cloud session, print a Windows test page locally from the same PC to the same printer. If the local test page is also garbage, your problem is the local printer or its driver - the cloud and TSPrint are innocent. Fix locally first: reinstall the printer's correct driver from the manufacturer's website. If the local page is perfect, climb to step two.
Connect to the server, open Notepad inside the session, type a few lines and print them through TSPrint. This separates Tally from the printing path:
Open TSPrint Client settings on the local PC and confirm Print as Image is OFF, the setting the video highlights. When a client update or a fresh install quietly turns it on, pages render as pictures and some printers respond with slow output, soft text, or on older models outright garbage. Toggle it off, disconnect and reconnect the session, and retest with the Notepad page.
A stuck or corrupted spooler produces blank pages and half-printed garbage. Restart the Print Spooler service on the local PC (run services.msc, find Print Spooler, Restart) and clear any stuck jobs from the printer queue. If many users share the server and all are affected at once, the server's spooler needs the same restart - that one needs your server admin.
If garbage survives the steps above, the local driver itself is the remaining suspect - especially after a Windows update replaced it with a generic one. Download the current driver for your exact printer model from the manufacturer's site, remove the old printer, install fresh, and print the local test page again before reconnecting to Tally. Also check for a printer firmware update if the model has a history of it - and be honest with yourself: a very old printer with only a basic generic driver may never render complex Tally formats correctly, and no setting will change that.
Two final suspects. First, a large version gap between TSPrint Server and TSPrint Client can corrupt the job in transit - update both to the current version. Second, if only some characters print wrong (boxes instead of symbols, wrong glyphs in the company name), the font Tally uses is missing or substituted on the local PC. Install the same fonts locally that the invoice format uses on the server.
See the complete TSPrint and Tally on Cloud setup live on screen, step by step, in the full video.
Watch Full VideoThe printer received print data it could not interpret - usually rendered by the wrong driver or in the wrong format. In a TSPrint setup the rendering happens on the local PC, so the cause is almost always the local driver, the Print as Image setting, or a version mismatch between TSPrint Server and Client.
That pattern points at the printer or its driver struggling with the job itself - memory limits on small printers, or a driver fault partway through a long document. Try printing the report in smaller batches, update the local driver, and make sure Print as Image is off so jobs stay compact.
When all users fail together, think shared components, not individual PCs - the server's print spooler, the TSPrint Server service, or the license or trial status. Restart the server spooler and check TSPrint Server options before troubleshooting any single PC.