I contacted Seagull to get some recommendations on what to do to try and resolve this. We're getting this information from shop leads, and sometimes by the time we would test, all would be fine. Sometimes the label would not print at all and never get to the print queue of the workstation in question. The right file would get created for Commander to detect, it would be converted, but a label might print a few seconds later or 15 minutes later. We began to see inconsistency in label printing reliability. The upgrade was simple enough to do, but the after effects just plain stink. My boss requested we upgrade to 10.1 SR 4 so we can use their label files and just adjust them slightly to pull in ERP data since we host Epicor here at HQ. They are using Bartender also, but it's a later version of the software. Our shop workers have told me things worked great before we made any changes. We use a mix of Seiko Smart Label 440 / 650, Zebra ZT 220, and Zebra ZP 450 printers throughout our shops (all connected to Windows 7 Pro computers via USB), and the server had been serving the label printing needs of 4 physical sites. Bartender was running on a Server 2012 VM (all components - Seagull License Server, Commander, and the Bartender Suite) and humming along with no issues. The file gets converted to btp by Commander, and the label prints. Our company intranet site writes a bt file into a specific location that is watched by Commander. We were using Seagull Bartender v10.0 Automation Edition with a 30-printer license to print Epicor ERP system data on labels in our manufacturing shops.
0 kommentar(er)
