Kiaro 2.11.4.1 print driver causes BarTend.exe App error フォローする

0
Avatar
Pete Beebe

Am fighting a problem with printing through Bartender from a Kiaro printer using the Kiaro native 2.11.4.1 print driver. We are running BarTender 2016 R4.

Whenever a print request is received and processed through the BarTend.exe application a Windows app event error occurs:

 

Faulting application name: BarTend.exe, version: 11.0.4.3127, time stamp: 0x5955ac38
Faulting module name: MSVCR100.dll, version: 10.0.40219.1, time stamp: 0x4d5f034a
Exception code: 0x40000015
Fault offset: 0x00000000000761c9
Faulting process id: 0x6328
Faulting application start time: 0x01d3b702b8033954
Faulting application path: D:\Program Files\Seagull\BarTender Suite\BarTend.exe
Faulting module path: C:\Windows\system32\MSVCR100.dll
Report Id: 004963b4-22f6-11e8-b6ef-005056811279

Although the app crash is logged, the actual label printing is successful however over time the server becomes unstable and starts experiencing virtual memory resource errors resulting in the eventual need to reboot the server. An alternative has been to run an automated script that restarts the BarTender Print Scheduler service every 15 minutes. Both of these band-aids obviously not a desirable or long-term fix.

Any suggestions are more than welcome.

 

6 コメント

0
Avatar
Pete Beebe
コメントアクション Permalink

The above Event log error is the common error that occurs after BarTend.exe is called during the printing procedure.

Below are additional errors that we see which normally results in us having to restart the Windows server:

Event 1026, .NET Runtime

Application: BarTend.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileLoadException
Stack:
at <Module>.ClrSupport.SetCultureInformation()
at <Module>.wWinMainCRTStartup()
at <Module>.wWinMainCRTStartup()

Event 2250, MSMQ

Message Queuing will not be able to accept messages temporarily because system paged pool is low. During this period, machine quota will be set to 0. No manual intervention is required at this stage. Once memory utilization has normalized, Message Queuing will automatically resume accepting messages.

Event 1026, .NET Runtime

Application: PrintScheduler.Service.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.OutOfMemoryException
Stack:
at System.Net.Sockets.Socket.UnsetAsyncEventSelect()
at System.Net.Sockets.Socket.UpdateStatusAfterSocketError(System.Net.Sockets.SocketError)
at System.Net.Sockets.SocketAsyncEventArgs.FinishOperationAsyncFailure(System.Net.Sockets.SocketError, Int32, System.Net.Sockets.SocketFlags)
at System.Net.Sockets.SocketAsyncEventArgs.CompletionPortCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)
at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)

Event 1000, Application Error

Faulting application name: PrintScheduler.Service.exe, version: 11.0.4.3127, time stamp: 0x5955ad9d
Faulting module name: KERNELBASE.dll, version: 6.1.7601.23796, time stamp: 0x59029714
Exception code: 0xe0434352
Fault offset: 0x000000000001a06d
Faulting process id: 0x89c8
Faulting application start time: 0x01d3b6b37cdda7d7
Faulting application path: D:\Program Files\Seagull\BarTender Suite\PrintScheduler.Service.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: ee477700-22a7-11e8-9903-005056811279

Event 1026, .NET Runtime

Application: PrintScheduler.Service.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.OutOfMemoryException
Stack:
at NLog.Targets.Wrappers.AsyncTargetWrapper.ProcessPendingEvents(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.TimerQueueTimer.CallCallback()
at System.Threading.TimerQueueTimer.Fire()
at System.Threading.TimerQueue.FireNextTimers()

Event 1000, Application Error

Faulting application name: PrintScheduler.Service.exe, version: 11.0.4.3127, time stamp: 0x5955ad9d
Faulting module name: KERNELBASE.dll, version: 6.1.7601.23796, time stamp: 0x59029714
Exception code: 0xe0434352
Fault offset: 0x000000000001a06d
Faulting process id: 0x98a8
Faulting application start time: 0x01d3b6b7a7e6e43a
Faulting application path: D:\Program Files\Seagull\BarTender Suite\PrintScheduler.Service.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 1315d785-22ac-11e8-9903-005056811279

Event 1026, .NET Runtime

Application: BarTend.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code e0434352, exception address 000007FEFCC6A06D
Stack:

At this point we'll opt to reboot the server which clears up the issue for a period of time.  When printing resumes to the Kiaro printer(s) the same App error event log entries are logged until system resources become unstable resulting in another server reboot.

 

I  neglected to mention that the operating system for the production server is Windows Server 2008 R2 Enterprise SP1.  We also spun up a test Windows Server 2012 R2 Datacenter installation and laid down BarTender R6. As soon as we pushed a print job through BarTender on this new install to the Kiaro printer the same Application Error event log entries started to appear. Printing to other printers (Zebra) does not exhibit this crippling issue.

 

 

0
Avatar
Pete Beebe
コメントアクション Permalink

Apologies for the multiple posts.  Also worth noting that the server config uses 2 vCPUs and 8GB of RAM. Overall server resources appear to be ample.

0
Avatar
Pete Beebe
コメントアクション Permalink

Feel free to delete this entire thread.  While it has been "Pending Approval" a possible resolution has been found.

0
Avatar
Shotaro Ito
モデレータ
コメントアクション Permalink

Thank you for update and good to hear that you've found the possible resolution. (I don't have a very good idea of what's happening, actually)
In case of hurry, please contact to support via email / chat.

 

0
Avatar
Josh Gelle
コメントアクション Permalink

We are having the EXACT same problem with Bartender and a Kiaro printer.  Can you shed some light as to your possible resolution and whether it worked or not?

0
Avatar
Pete Beebe
コメントアクション Permalink

Seagull support was of little to no help on this subject even with a support case open.

1. Solution for us was to uninstall the entire Kiaro driver package (Kiaro v2.2 is what we used) and peripheral utilities and the related Windows Kiaro printer queue.

2. Created a TCP/IP print queue for the Kiaro printer.

3. Installed ~just~ the print driver (not by running the Kiaro Setup.exe file) by pointing to the "QuickLabel-Kiaro.inf" file from the extracted Kiaro v2.2 download file and ensured it was selected on the new Kiaro printer queue.

4. Ensured that the "Kiaro Media Utilities" application was installed. The utilities app is necessary otherwise labels would print blank. This particular fix was provided by QuickLabel support staff.

ログインしてコメントを残してください。