The CoreScanner.exe service is crashing when a Symbol LS2208 scanner is plugged in and a program tries to connect to the CoreScanner service.
USB Device Type is set to IBM Hand-Held USB on the LS2208
CoreScanner.exe is version 2.7.0.0
The same program works fine with an LS4278.
This has occurred on two different Windows 7 64 bit computers.
The relevant entries from the Event Log are below.
I believe that there was a significant change in firmware / drivers for LS2208 scanners manufactured after 02 Jan 2015. Is there a incompatibility between the drivers for scanners manufactured before the end of 2014 and CoreScanner.exe?
The scanner was manufactured before this change. Should we be using a different version of CoreScanner.exe?
Or how should we resolve this problem?
Event Log Entries
=================
Faulting application name: CoreScanner.exe, version: 2.7.0.0, time stamp: 0x55def2e6
Faulting module name: IBMHIDTrans.dll, version: 2.7.0.0, time stamp: 0x55def2cc
Exception code: 0xc0000005
Fault offset: 0x000000000001bc50
Faulting process id: 0x1320
Faulting application start time: 0x01d1b822d3c524e2
Faulting application path: C:\Program Files\Motorola Scanner\Common\CoreScanner.exe
Faulting module path: C:\Program Files\Motorola Scanner\Common\IBMHIDTrans.dll
Report Id: 3c6bc7f5-2416-11e6-949e-005056c00008
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: CoreScanner.exe
P2: 2.7.0.0
P3: 55def2e6
P4: IBMHIDTrans.dll
P5: 2.7.0.0
P6: 55def2cc
P7: c0000005
P8: 000000000001bc50
P9:
P10:
Attached files:
F:\WINDOWS\Temp\WERE5F1.tmp.appcompat.txt
F:\WINDOWS\Temp\WERE611.tmp.WERInternalMetadata.xml
F:\WINDOWS\Temp\WERE612.tmp.hdmp
F:\WINDOWS\Temp\WERE7E7.tmp.mdmp
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_CoreScanner.exe_c259b25b1f08384d549af3082bba19d26786168_cab_126be96a
Analysis symbol:
Rechecking for solution: 0
Report Id: 3c6bc7f5-2416-11e6-949e-005056c00008
Report Status: 4
I'm having the same issue with 32-bit windows 7. I can get it to work however if after rebooting it beeps once, then while windows loads it beeps again, immediately I scanning the IBM Hand-Held USB barcode configuration, then it will work. If I don't do it in time the core crashes.
update.. so long as I scan the IBM Hand-held USB config barcode before using the SDK apps it will work.
Points: 0
You voted ‘up’
The latest ZebraScan 1232 update downloaded a new driver that seems to have fixed this issue thankfully.
Points: 0
You voted ‘up’