Bartender Crashes When Running On Virtual W7-32Bit Machine

Legacy Poster

• April 09, 2014 11:47

I've installed Bartender (Pro) v10.1.SR3 on a (VMWare ESXi) virtual Windows 7 32-bit machine.

Windows updates are installed until januari 2014 

Bartender is not activated.

 

Starting Bartender goes well but creating a new document or opening an existing one always results in a crash of Bartender.

 

Windows Application Log shows the following information:

 

Naam van toepassing met fout: bartend.exe, versie: 10.1.3.2954, tijdstempel: 0x533b3be3

Naam van module met fout: KERNELBASE.dll, versie: 6.1.7601.18229, tijdstempel: 0x51fb10c6

Uitzonderingscode: 0xe0434f4d

Foutoffset: 0x0000812f

Id van proces met fout: 0x848

Starttijd van toepassing met fout: 0x01cf53e7e3217a3b

Pad naar toepassing met fout: C:\Program Files\Seagull\BarTender Suite\bartend.exe

Pad naar module met fout: C:\Windows\system32\KERNELBASE.dll

Rapport-id: 2dbd1f38-bfdb-11e3-966a-005056ba2f7c

 

Result is the same when starting a RDP session to the virtual machine and then start using Bartender.

 

When I install Bartender on a physical Windows 7 64-bit PC and then start a RDP session to this PC, bartender is working fine.

 

I'm investigating if Bartender could be a solution for use because we work in a (Oracle) VDI environment. Which is basically the same as an XenDesktop environment.

 

How can this problem be solved?

0

• 

  Ian Cummings

  Moderator

  ★ BarTender Hero ★

  • April 09, 2014 14:43

  There should be no problem with running BarTender in a VM, indeed we use a VMware ESXi server ourselves for the various images in our testing department.  We also have many customers successfully using BarTender in a XenApp environment.  Perhaps there is something wrong with the image or BarTender installation in the VM that is causing the crash.

   

  Try this: Download and install the Microsoft Visual C++ 2008 SP1 Redistributable Package (x86) from the below link.  If already installed, it might be needed to uninstall it first before reinstalling it again.  And yes it is the x86 variation you need as BarTender is an x86 only application:

   

  http://www.microsoft.com/en-us/download/details.aspx?id=5582

  0
• 

  Legacy Poster

  ★ BarTender Hero ★

  • April 10, 2014 13:39

  I hoped for the answer that it shouldn't be a problem of using bartender in a virtual environment.

  Which means that we can use it if I can get it to work. 

   

  The Windows 7 VM is a pretty straightforward installation of Windows 7.

  Via "Turn Windows Features on or off" I've selected the Microsoft .Net 3.5.1 components.

  All windows updates are installed via our WSUS server. Also .Net 4.5.1 and silverlight are added.

   

  MS Visual C++ 2008 Redistributable - x86 9.0.309729.6161 is installed manually as wel as the VMWare Tools.

  Because of the given solution I removed the installed version, rebooted the VM and installed a newer version.

   

  I've installed a local HP 2200 PCL5 printer connect to LPT1:

   

  Bartender is installed using selected components. Only Bartender and Printstation are selected.

   

  After starting bartender the Pro edition is selected. (I don't think this has any influence at this time)

  I select create new document, empty template, finish.

   

  I get dialog window stating "bartender has stopped working"

   

  I really don't see what could be wrong.

  0
• 

  Ian Cummings

  Moderator

  ★ BarTender Hero ★

  • April 14, 2014 09:31

  Here are the system requirements: http://www.bartenderbarcodesoftware.com/label-software/barcode-label-software-features.aspx#compat

   

  Note that we use .NET framework 3.0 sp2.

   

  Try an uninstall of the "Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)" from your Windows installation via the Windows control panel.  Then download the latest SP1 release from the below location and reinstall.  It's possible that the currently installed component is corrupted in such a way that results in this symptom.

   

  http://www.microsoft.com/en-us/download/details.aspx?id=5582

   

  Another possibility is a corruption with the .NET Framework 3.0 SP2 which Print Station makes heavy use of.  You can use the below Microsoft repair tool to hopefully fix any such issues.

   

  http://www.microsoft.com/en-us/download/details.aspx?id=30135

  0

Please sign in to leave a comment.