Printing Label - Long Delay Follow

0
Avatar
Legacy Poster

I have a C# program (see text file attachment for the code) that I have used for 3 or 4 years. It has always taken 5-6 seconds for the first label to come out. The customer would like it much faster but can live with the short delay. The problem is that for some reason it is taking 80 - 100 seconds for the first label to print. The 2nd and subsequent labels print as fast as the printer will print. I put the program in debug mode and it instantly gets through the parameter handling and the first delay is at the statement "LabelFormatDocument btFormat;". It delays at this statement for 40+ seconds. There is also a 5 or 6 second delay on all subsequent Bartender statements. The time to get to the statement "btFormat.print()" is between 80 to 100 seconds. If I open the label format and print tags from the label format designer, they print instantly. Tag printing is much faster (6 - 10 seconds) on other PC's running a different but similar C# program. Also, the license server is running on the PC where the long delay is occurring (but did not have a long delay for the past 2 years). The customer has Bartender Automation Version 9.4 build 2749 for 20 printers (currently using less than 10 printers). Any ideas will be greatly appreciated.

4 comments

0
Avatar
Canguita
Comment actions Permalink

Hello,

 

In first place I would suggest upgrading BarTender to the latest Service Release for your version:

 

http://www.bartenderbarcodesoftware.com/label-software/fixes_94.aspx

 

If after this, you are still having issues, check if your label has True Type fonts or Printer Fonts, Also check if you are using pictures in your label.

 

Which printer are you using? Do you have Seagull Printer Drivers? If yes, let us know which version.

0
Avatar
Domingo Rodriguez
Moderator
Comment actions Permalink

Does the behaviour change if you disable the following Internet Explorer Internet Option "Check for publisher's certificate revocation" (found under the "Advanced" tab) for the Windows account under which the BarTender process will be running under your C# program?

0
Avatar
Legacy Poster
Comment actions Permalink

I am not at the customer site today, but will be soon. I will try all of this to see what helps and post back the results. I found a work around where I print the labels from a SQL database (print routines write an entry into the SQL DB instead of printing to the printer directly) and I have a dedicated process running 24/7 that does the printing. This way the engine, format, and printer are already opened and the routine only has to print. It is almost instant running like this (less than 1 second). This method solves another problem I have where the customer needs to print 30 unique labels in 60 seconds. On stations that work properly, the routine takes 3-5 seconds to start the engine, set the format and printer, and print the tag. Obviously the max number of labels per minute in this case is 20 labels (best case). So this method solves that problem as well. I will answer the questions that I can. The application is printing to a Datamax I-4212 printer using the Seagull printer driver. It is using the printer font. There are no images in the label. I will try upgrading and changing the internet option. The internet option is interesting as this is a PC that has the internet turned off, this may be the reason it delays. Will turning off that setting in IE prevent BarTender from trying to access the internet?
0
Avatar
Domingo Rodriguez
Moderator
Comment actions Permalink

BarTender is a native Windows application developed in C++ and MFC (Microsoft Foundation Class). However, some of Bartenders new functions are based on .NET Framework 2.0 technology. For any .NET
Framework 2.0 application if the mentioned security setting is enabled, it can cause BarTender, License Server or any BarTender Suite service to start slowly or to not start at all. So yes, turning off this setting will prevent BT from

trying to retrieve this certificate revocation from the internet.

 

Also (I didn't check yet the source code in detail), make sure that the BarTender engine and the BarTender document aren't started / opened for each print job that you perform. They should be started / opened once your application (or the print module within your application) starts, and be destroyed when you exit.

Please sign in to leave a comment.