Print Jobs Freezing Mid-Job Folgen

0
Avatar
Legacy Poster

I have a Bartender 10.1 server with Commander. This server sends print jobs to Zebra & Printronix thermal printers in a state next to it, and also jobs to printers in another country. Print jobs can be as large as maybe 20-30k records, and some of the raw .prn files as big as ~50 MB.

 

This works well most of the time.

 

However, at apparently random times throughout the day the label room users will notice 4-5 minute delays in either:

  1. Starting a job; i.e. Commander will send the job but there is a delay before it begins printing
  2. Completion of a job; a job will start but pause mid-job then continue again

I believe this is network related. IT has been unable to find anything such as an over-stressed server or particularly heavy network traffic to coincide with these events, but I think the best course of action is to split Bartender and move it into immediate proximity with the printers (on a test basis first).

 

Is there anything else I should try first? I know my labels are not in printer-native code (e.g. zebra triumvirate) because it's a bit uglier, though that would shrink the size of their data, but that requires label changes/approvals.

 

Another problem we have--though quite rarely--is that a label will print missing various fields, such as a missing barcode. I've looked at the log files closely and Bartender is sending the correct data. I wonder if the missing fields are related also to whatever is causing the delays.

 

THANKS!

4 Kommentare

0
Avatar
Ian Cummings
Moderator
Aktionen für Kommentare Permalink

How are the printer driver installed relative to where BarTender/Commander is running?  Are they installed locally, or in a server/client fashion where the "server" is on a separate print server, and the BarTender/Commander computer is acting as the "client".

 

In the BarTender command handler, what do you have configured under the "Advanced" tab for the desktop desktop heap in KB?

0
Avatar
Legacy Poster
Aktionen für Kommentare Permalink

Hi Ian,

 

Thanks--they are actually installed locally, not with a separate print server. I think this is probably not ideal, and today I'm going to experiment with moving a couple of the printers to a print server that is local to the printers themselves, so that Bartender, its hundreds of miles away, will issue print jobs to a local-to-printer print server, and then it can send to the printers here. I'll do this with a couple of printers and see if it makes a difference.

 

In the Commander config item I see nothing for advanced...?

 

Thanks! I also made great use of a comment you left in another thread by somebody regarding immediate/polling yesterday :0

0
Avatar
Ian Cummings
Moderator
Aktionen für Kommentare Permalink

In Commander, stop detection, select the "Detection>BarTender command handler setup" menu item, and from the dialog that opens select the "Advanced" tab.

0
Avatar
Legacy Poster
Aktionen für Kommentare Permalink

Got it. In that tab I have CHECKED Terminate and restart unresponsive processes after 2 minutes and CHECKED Resend failed jobs, with maximum retries as 1.

 

Thanks!

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.