TSPrint is simple software, which is why its failures are almost always simple too - one half missing, one option off, one trial quietly expired. The six mistakes, in the order offices actually make them.
When a TSPrint setup fails, it rarely fails mysteriously. The same six setup mistakes account for nearly every TSPrint-is-not-working complaint in Tally on Cloud offices. Work through them in order before touching anything else.
TSPrint has two halves and both are compulsory. Offices install TSPrint Server on the cloud server, see the virtual printers appear, and declare the job done. But nothing reaches the physical printer until TSPrint Client is installed on the local PC - the client is the half that actually talks to your printer. Missing client is the single most common setup failure.
The TSPrint Client must be running before you connect to the server, so it can hook into the session as it is created. If someone closed it, or it was removed from Windows startup, the session opens without TSPrint printers. Fix: start the client, then disconnect and reconnect the TSplus session. Simply opening Tally again inside the same session does not recreate the printers.
In the TSPrint Client settings there is an option to redirect the local printers into the session. If this is off or set to redirect only one specific printer, users see a partial list - typically only the default - and you are back to the default-printer problem TSPrint was bought to solve. Turn on redirect all local printers on every client PC, as shown in the video.
This is the setting the video specifically calls out. With Print as Image on, every page is converted into a picture before printing. Jobs become much larger and slower, and fine text on invoices can look slightly soft. Turn it off in the client settings so pages travel as compact print data and render crisply through the local driver. Keep it in mind as a troubleshooting lever only - if a specific odd document refuses to print correctly, testing once with it on can help isolate the issue, then turn it off again.
TerminalWorks updates TSPrint regularly, and a very old client talking to a newly updated server (or the reverse) can silently fail to create printers. When TSPrint stops working after a server update, update the clients too. The healthy habit: whenever TSPrint Server is updated on the cloud server, roll the same version of TSPrint Client to all PCs in the same week.
TSPrint's free trial runs for a limited period (25 days at the time of writing). When it expires, printing stops - and because everything "worked last week", teams waste hours checking printers and networks. Before deep troubleshooting on a setup that used to work, open the TSPrint Server options and check the license status first. It takes ten seconds and is embarrassing how often it is the answer.
See the complete TSPrint and Tally on Cloud setup live on screen, step by step, in the full video.
Watch Full VideoThe printers are created by the server component, but the job has nowhere to go. Almost always the TSPrint Client is not installed or not running on that PC. Start the client first, then disconnect and reconnect the session so the printers are created with the client active.
You need matching versions, not necessarily a reinstall on day one. But if printing breaks after a server update, updating the clients to the same version is the first fix to try. Keeping server and client versions in step avoids the problem entirely.
Check the license status in TSPrint Server options before anything else. The free trial is time limited - around 25 days - and an expired trial stops printing in a way that looks like a technical fault. Activating a license restores printing immediately.