SENTINEL is very slow in generating print jobs. Multiple job requests (drop files) at the same time seem to exacerbate the problem.
The user experiences very slow performance when printing labels using drop files. The symptom appears when multiple drop files were sent at the same time. When inspecting the logs for SENTINEL, the user may find that some of the print jobs took several minutes to complete.
The likely cause for this is the method which SENTINEL uses to communicate with printers. When SENTINELs are configured with TEKLYNX drivers using direct TCP/IP ports to communicate with the printers, print jobs are sent directly to the printer (the port has a –> symbol before the IP address). SENTINEL must negotiate (handshake) with the printers in that case. Depending on the size of the printer buffer, SENTINEL may have to wait until the labels are printed before it can complete the print job and start the next job.
If multiple SENTINELs are configured to send a particular print job to a printer, then the next print job will need to wait until the first one is complete before SENTINEL starts to process it.
The solution is to have Windows communicate with printers rather than SENTINEL.
- Setup print queues on the server where SENTINEL is installed
- In SENTINEL, set the printer to use the print queues in Windows
In this setup, SENTINEL will generate the print jobs and place them in the Windows print queues. Print jobs will be generated as fast as the hard drives can accept them. Windows will perform the task of sending the jobs to printers.
Reference Article: Setup a Printer Using TEKLYNX Printer Drivers and Windows Spooler / Print Subsystem – KBA-01105-G2R8G8