Bartender App Crash

Legacy Poster

• 22. Oktober 2015 02:11

Hi my name is Jett, I work for a company that uses bartender to print barcode labels for orders sent out. I am just an employee not and IT guy but this problem interferes with my work everyday and even though IT claims to be "working" on it the problem persists and I am curious myself as to the solution. We fill orders through VWare and everything runs fine untill its time to print the label. Then all of the sudden the label won't print and a message that says "server busy retry or switch to" pops up and clicking either will not resolve the problem. But after wither 10 seconds or 5 minutes the label prints and everything works fine (for a while) untill it happens again. Just from the messages I see and the information i have discovered myself having limited access i know that we are running windows 7, oracle, Vware, and bartender with i think the windows print driver. Throughout the day and at different times i will get different error messages, the messages are as follows. *32 bit print driver host has stopped* *bartender 64 bit APP CRASH* *splsh.wow 64 bit APP CRASH* once bartender app crashes though i cannot begin working again unless i force end VWare on task manager and open it again. Once i begin work again i am given the same *server busy retry or switch to* message that will not go away untill all of the sudden the label prints and everything runs fine again. But the problem will occur later in the day. This has gone on for about 2 weeks and is very frustrating. I know that the print driver host is 32 bit and both splsh.wow and bartender are 64 bit. Although the OS is windows 7 i am unsure if it is 64 or 32 bit and same goes for the CPU. Somone please help. It would be greatly appreciated.

0

• 

  Ian Cummings

  Moderator

  ★ BarTender Hero ★

  • 23. Oktober 2015 09:54

  VMware is just a virtual machine environment in which you run a Windows image, in which BarTender would be installed.  VMware is thus not relevant to the issue.  It sounds like you're automating/integrating BarTender in some fashion, it would be helpful to know in what way this is done.

   

  Check the Windows task manager to see if there are lots of "bartend.exe" processes running.  It could be that BarTender is hanging/crashing and thereby accumulating a good man dead processes that will then cause you problems.

   

  Try a full removal of an Seagull printer drivers, reboot, and then install from scratch using the latest version from our website.  Often this can help fix reliability issues when the software is used in an automated environment.

  0
• 

  Legacy Poster

  ★ BarTender Hero ★

  • 9. Mai 2016 16:16

  VMware is just a virtual machine environment in which you run a Windows image, in which BarTender would be installed.  VMware is thus not relevant to the issue.  It sounds like you're automating/integrating BarTender in some fashion, it would be helpful to know in what way this is done.

   

  Check the Windows task manager to see if there are lots of "bartend.exe" processes running.  It could be that BarTender is hanging/crashing and thereby accumulating a good man dead processes that will then cause you problems.

   

  Try a full removal of an Seagull printer drivers, reboot, and then install from scratch using the latest version from our website.  Often this can help fix reliability issues when the software is used in an automated environment.

  not VMWare.Vware as in versatile warehouse. Its simply a virtual machine that we fill orders out of. I am in IT now and we have tried everything. new drivers. old drivers. bartender upgrades. everything. I recently posted a newer topic going further into detail about this.

  0
• 

  Ian Cummings

  Moderator

  ★ BarTender Hero ★

  • 9. Mai 2016 16:38

  Get i touch with tech-support: http://www.seagullscientific.com/support/technical-support/

  0
• 

  Rodney Anderson

  ★ BarTender Hero ★

  • 23. August 2016 18:11

  I'm Rod, from the vendor that wrote the warehouse control system application which uses Bartender to print the labels. We send data to the Bartender print engine in the background, the Bartender application is never visible to the operator.

  We have been in touch with tech support, you can probably find more information under support request #9018. I last traded email with Tyler Comin about the issue in December of 2015.

  I have restored a copy of their production database in my test environment, in an attempt to duplicate the problem, without success. It may be worth noting that they have 50 workstations that may be printing labels at any time. I'm wondering if network traffic may be causing delayed communication with the Seagull License Server. I don't have any first hand knowledge of their network layout, but they are using a lot of old equipment in the warehouse.

   

  0

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