Issue With Bartend.exe On Win 2008R2

Legacy Poster

• 26. September 2012 08:58

We have an issue during execution printing on our bartend.exe on citrix xenapp 6.5.

Below is the error log:

Faulting application name: Bartend.EXE, version: 6.0.443.97, time stamp: 0x39b70811
Faulting module name: CFGMGR32.dll, version: 6.1.7601.17621, time stamp: 0x4ddb8851
Exception code: 0xc0000005
Fault offset: 0x0000125d
Faulting process id: 0x2380
Faulting application start time: 0x01cd9b924d4c66fe
Faulting application path: C:\PROGRA~2\BARTEN~1\Bartend.EXE
Faulting module path: C:\Windows\syswow64\CFGMGR32.dll
Report Id: 8be9f769-0785-11e2-bdc6-d4ae528ba9cd

Any idea how we should resolved this?

0

• 

  Fernando Ramos Miracle

  ★ BarTender Hero ★

  • 26. September 2012 15:53
  Could you tell me what exact version, edition and build of BarTender are you working with?

  0
• 

  Legacy Poster

  ★ BarTender Hero ★

  • 28. September 2012 05:52
  [quote name='Fernando R-Seagull Support' timestamp='1348674829' post='3350']
  Could you tell me what exact version, edition and build of BarTender are you working with?
  [/quote]
  
  We are using Bartender
  Version: 6.00
  Build: 443
  
  Current OS: Windows 2008 R2
  Application: Citrix XenApp 6.5
  
  We have using this version without issue on our Windows 2003 server.

  0
• 

  Fernando Ramos Miracle

  ★ BarTender Hero ★

  • 28. September 2012 07:55
  I'm afraid that BarTender v6.00 is very old and it's certainly not compatible with Windows 2008 R2. In order to work on this OS you'll need BarTender v9.2 or higher.

  0
• 

  Legacy Poster

  ★ BarTender Hero ★

  • 19. April 2013 18:15

  Hi I am seeing the same issue.  

   

  BarTender version in server: 9.20

   

  I see 1 event error at 3:56:54PM  Application Error

   

  Faulting application name: bartend.exe, version: 9.20.2648.1889, time stamp: 0x4ad696b2

  Faulting module name: bartend.exe, version: 9.20.2648.1889, time stamp: 0x4ad696b2

  Exception code: 0xc0000005

  Fault offset: 0x000fe52a

  Faulting process id: 0x18fc

  Faulting application start time: 0x01ce3cd151c6c9e4

  Faulting application path: C:\PROGRA~2\Seagull\BARTEN~1\BARTEN~1\bartend.exe

  Faulting module path: C:\PROGRA~2\Seagull\BARTEN~1\BARTEN~1\bartend.exe

  Report Id: b3292c06-a8c6-11e2-bc90-005056b896db

   

  2 seconds later 3:56:56PM

  Faulting application name: bartend.exe, version: 9.20.2648.1889, time stamp: 0x4ad696b2

  Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec49b8f

  Exception code: 0xc015000f

  Fault offset: 0x000847db

  Faulting process id: 0x18fc

  Faulting application start time: 0x01ce3cd151c6c9e4

  Faulting application path: C:\PROGRA~2\Seagull\BARTEN~1\BARTEN~1\bartend.exe

  Faulting module path: C:\Windows\SysWOW64\ntdll.dll

  Report Id: b3ea5e18-a8c6-11e2-bc90-005056b896db

   

   

  I'm running a web service utilizing the Interop.BarTender.dll version 9.20.  Normally we don't have an issue but maybe once or twice a day we get this error.  The exception caught from the service is something like: (I'm guessing because the web service crashed). 

   

  Symptom I will see are 4-5 unclosed bartender.exe applications on the server task manager with 0 CPU utilization, which means they were unclosed by the service. Is this because there is a limit to how many bartender applications that can be open at any one time on the server?  

   

  System.ServiceModel.FaultException: The server was unable to process the request due to an internal error.  For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.

   

      

  Server stack trace: 

  at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message reply, MessageFault fault, String action, MessageVersion version, FaultConverter faultConverter)

  at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)

  at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)

  at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)

  at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

      

  Exception rethrown at [0]: 

  at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)

  at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)

   

  0
• 

  RikoNw

  ★ BarTender Hero ★

  • 20. Oktober 2017 07:13
  • Bearbeitet

  Thanks to Ian Cummings! Driver isolation is working ! Bartender is no longer breaks down.

  0

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