![]() Has anyone seen something like this happen? We could roll back to the previous version with a good bit of leg work, but after investing the time and effort thus far I would really like to make the newest version work. It's a similar story every time (before the server rebuild and after it). I thought I would crack open one of these in Visual Studio and see what is happening. I found out Bartender is still creating dump files with the same errors as shown above. I was told the same issues were happening again. Things worked well with minimal issues all day yesterday.until last night. I also setup a single dedicated user account as a local admin for folks to login to the server with to avoid processes running under multiple user accounts.Ībout 36 hours ago (around 11 PM Sunday night) the newly provisioned server went into production. I would watch the print queue on each workstation from print management on the Bartender server to make sure printing worked. Then I installed the necessary drivers and could print to every single printer by dropping a bt file in the right spot. I ripped off the Zebra drivers from every workstation that had them and used the Seagull drivers as recommended. I checked driver versions on every workstation, found some version mismatches, and resolved them so that all Seiko label printers of the same model were on the same driver version. I patched it with all Windows updates and then installed the latest version of Bartender Automation Edition (10.1 SR4). It's not a terribly complicated setup, so after documenting the configuration and backing up the VM, I deleted the VM and built a new Server 2012 VM from scratch. They recommended doing things like using only Seagull drivers for the Zebra printers, making sure we had no corrupt drivers on the servers or the workstations, re-installing Bartender on the same server with AV disabled, running Commander as an application and not a service, or possibly installing on a new server. Đ0:57:10Ė668Ğrror Miscellaneous OKěarTender Image Dump: Saved dump file to 'C:\ProgramData\Seagull\BarTender\Dump\BarTend_0158.dmp' Đ0:56:44Ė668Ğrror Miscellaneous OKěarTender Image Dump: Saved dump file to 'C:\ProgramData\Seagull\BarTender\Dump\BarTend_0157.dmp' Đ0:51:47Ė668Ğrror Miscellaneous OKěarTender Image Dump: Saved dump file to 'C:\ProgramData\Seagull\BarTender\Dump\BarTend_0156.dmp' Đ0:51:29Ė668Ğrror Miscellaneous OKěarTender Image Dump: Saved dump file to 'C:\ProgramData\Seagull\BarTender\Dump\BarTend_0155.dmp' Đ0:48:55Ė668Ğrror Miscellaneous OKěarTender Image Dump: Saved dump file to 'C:\ProgramData\Seagull\BarTender\Dump\BarTend_0154.dmp' Đ0:48:29Ė668Ğrror Miscellaneous OKěarTender Image Dump: Saved dump file to 'C:\ProgramData\Seagull\BarTender\Dump\BarTend_0153.dmp' Đ0:46:20Ė668Ğrror Miscellaneous OKěarTender Image Dump: Saved dump file to 'C:\ProgramData\Seagull\BarTender\Dump\BarTend_0152.dmp' Text Đ0:46:04Ė668Ğrror Miscellaneous OKěarTender Image Dump: Saved dump file to 'C:\ProgramData\Seagull\BarTender\Dump\BarTend_0151.dmp' ![]() This would happen once or more per hour (sometimes many dump files and sometimes only one). We turned on all kinds of logging and found Bartender was throwing errors and creating dump files. 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |