Print job hangs in Windows spooler for only ONE out of 20+ printers

h.rauch

• 3 août 2023 07:49

We have 20+ printers of the same make and model and 99% of the time we use the same layout with variable data. And we use Enterprise Integration on BT 2022 R6.

For all but one printers, the print jobs from the integration get printed without problems, just on one printer the job hangs and has to be cancelled in Windows manually. 

Printing the same layout with the same data directly out of Designer works fine.

Any suggestions how to track that error? There is no useful information in the Windows Event logs, can I do something in the integration to monitor what is going on?

0

• 

  pthane

  ★ BarTender Hero ★

  • 3 août 2023 10:39

  Assuming you have created the System Database you could look in History Explorer and see if there is anything in there

  0
• 

  h.rauch

  ★ BarTender Hero ★

  • 3 août 2023 22:40

  Thanks for the tip, Peter. History Explorer is a good tool, but did not reveal anything new.

  0
• 

  pthane

  ★ BarTender Hero ★

  • 4 août 2023 09:38

  Have you printed to it from Designer from a client PC or from the server itself and if the latter did that print without issue? Are you using a dedicated BarTender user account for the Print Scheduler service? If so can you log into the server and print from Designer with that?

  I assume you have checked all the settings in the driver against the working devices to make sure there are no differences and also confirmed there are no network clashes with duplicate IPs with the defective printer. 

   

  0
• 

  h.rauch

  ★ BarTender Hero ★

  • 4 août 2023 10:22

  All printing activities are done from the server to ensure identical conditions. Services are running with default accounts.

  All drivers are also in default settings, since we are all newbies here :-) There are no network issues, the printers have been in operation before BarTender for years.
  Also, all printers have recently been updated with the latest firmware from the supplier. I am starting to believe it is a printer issue and not a software issue.

  Just as a last test, do you think printing directly to the printer, without spooler, could resolve it? We can certainly try it, it cannot make the situation worse :-)
  But, is direct printing advisable in a production environment?

  0

Vous devez vous connecter pour laisser un commentaire.