Bartender Error - An Image Error Occurred: Not Enough Memory Available
The particulars:
- Bartender Automation v9.4 SR3
- We do plan to update to v10, but will most likely wait for SR1 to fix an issue with Print Station
- Windows 2003 x64 SP2 (fully updated)
- Seagull Drivers v7.3
- All Zebra Printers
I am seeing this message appearing in my BTMsg.txt log file every 1-3 ... when this happens no labels will print that contain images. The jobs are spawned by Commander, so I can see the jobs being created and can see that my labels containing no images continue to print fine. When this happened today I went into task Manager and saw two bartend.exe processes running under the user that commander uses, these processes were only using 80MB and 103MB of RAM each (the server has 16GB available). If it ran out of memory I would have expected these processes to be huge. Anyway, if I kill those bartend.exe processes and allow the next print from commander to spawn a new instance, it works fine again for 1-3 days.
Its not exactly a huge volume of prints per day, but it is the largest of my handful of sites ... I'd guesstimate 800-1000 labels per day 8hr shift are processed through commander. 50% or so would contain images. Our labels that contain images can contain from 1-6 PNG images depending on various factors.
Any ideas would be greatly appreciated. Thanks.
- Bartender Automation v9.4 SR3
- We do plan to update to v10, but will most likely wait for SR1 to fix an issue with Print Station
- Windows 2003 x64 SP2 (fully updated)
- Seagull Drivers v7.3
- All Zebra Printers
I am seeing this message appearing in my BTMsg.txt log file every 1-3 ... when this happens no labels will print that contain images. The jobs are spawned by Commander, so I can see the jobs being created and can see that my labels containing no images continue to print fine. When this happened today I went into task Manager and saw two bartend.exe processes running under the user that commander uses, these processes were only using 80MB and 103MB of RAM each (the server has 16GB available). If it ran out of memory I would have expected these processes to be huge. Anyway, if I kill those bartend.exe processes and allow the next print from commander to spawn a new instance, it works fine again for 1-3 days.
Its not exactly a huge volume of prints per day, but it is the largest of my handful of sites ... I'd guesstimate 800-1000 labels per day 8hr shift are processed through commander. 50% or so would contain images. Our labels that contain images can contain from 1-6 PNG images depending on various factors.
Any ideas would be greatly appreciated. Thanks.
0
-
Shotaro Ito
★ BarTender Hero ★
Hi Pulsa,
BarTender up to 9.4 not properly handle PNG's transparency(alpha), so if your PNG image has transparent part, try change to non transparent. PNG transparency works from BarTender 10.0.
However I'm not sure that actually caused the error.
I wonder "Restart process" of command handler setup is not working properly - in default, bartender process restarted every single hour so you should be able to avoid cumulative issue of BarTender process which happens after days.
(this feature introduced from BarTender 9.4SR2 along with format caching.)
Try create command handler again. while detection stop, Detection menu > BarTender command handler setup, rename current command handler (such as "BarTender1" to "tmp"). from left bottom, click "add new" to create a command handler, and rename to the same name as old handler (such as "BarTender1").
Set Restart process to [Every hour].
Modify command handler setup (login account etc) to match original command handler, then remove old command handler.0 -
Shotaro,
Thanks for the reply ... I am not finding the option in Commander's task setup (new or editing existing) to restart the process. Can you give me a better idea of what menu I should be looking at?0 -
Shotaro Ito
★ BarTender Hero ★
Command handler setup is from Detection > BarTender Command handler setup - as picture below.
(Alternatively you can find Task property > Command tab > [BarTender command handler Setup] button at the bottom)
Make sure the BarTender version is 9.4SR3(build 2781) - process restart setting has been introduced from 9.4SR2.
For BarTender 9.4 initial build to SR2 users, please apply [url="http://www.seagullscientific.com/aspx/fixes_94.aspx"]9.4SR3 update[/url].0 -
[quote name='Shotaro I -Seagull Support' timestamp='1335143261' post='2286']
Command handler setup is from Detection > BarTender Command handler setup - as picture below.
(Alternatively you can find Task property > Command tab > [BarTender command handler Setup] button at the bottom)
Make sure the BarTender version is 9.4SR3(build 2781) - process restart setting has been introduced from 9.4SR2.
For BarTender 9.4 initial build to SR2 users, please apply [url="http://www.seagullscientific.com/aspx/fixes_94.aspx"]9.4SR3 update[/url].
[/quote]
Ah found it now ... unfortunately I already had it set to restart the process hourly.
Some of our PNGs do use transparency so thats probably the cause. I'll probably be looking at going to v10 sooner rather than later.0 -
Shotaro Ito
★ BarTender Hero ★
[quote name='PulsaMatt' timestamp='1335368696' post='2308']
Ah found it now ... unfortunately I already had it set to restart the process hourly.
Some of our PNGs do use transparency so thats probably the cause. I'll probably be looking at going to v10 sooner rather than later.
[/quote]
If something wrong (such as setting corrupted) in command handler setup, the process restart may not occur at specified period. In that case, you need to re-create the command handler again.0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
5 Kommentare