Since I can’t successfully email support, I thought I will post this here to see if anyone can help?
We have a client and their system is keep crashing.
this is the log file.
Any help would be appreciated!
Cheers!
Kensushi Log.zip (21.7 KB)
There are many errors in the log. But we know and fixed this error in 5.7.14
Also this error did not create a crash. Can you give me more detail?
1 Like
Can you try to update to 5.7.14 see if that fixes it
1 Like
OK I will get a update for them and post back. cheers Jesse.
So basically, this system was having some strange clicking behaviors, which I asked here and we thought it would be some USB port issue, so the Machine is going to be sent back for RMA to the manufacture in the new year.
And yesterday, They reported that the system crashed, and it had crashed a few times already in the past few days, and sent me this screenshot.
So I went onto the system and got the log from them.
With a hang that causes that messages, there might not be anything flushed to the log. The recent errors I see in the log most likely would only cause issue on startup.
Look in the event viewer → windows logs → applications and see if there are any entries around the same time.
2 Likes
Hi Memo, Merry Christmas,
and I went and check the event log,
There were 2 errors shown as below:
Error 1
- 1000 2 100 0x80000000000000 104083 Application TITAN-S360
- Samba.Presentation.exe 5.7.8962.19755 6694d6a7 KERNELBASE.dll 10.0.14393.7513 67171aad e0434352 000dd562 1680 01db549bbfdc3354 C:\Program Files (x86)\SambaPOS5\Samba.Presentation.exe C:\Windows\System32\KERNELBASE.dll 1e757ba3-ceea-42f2-a59c-755dc60c21ab
Error 2
- 1026 2 0 0x80000000000000 104082 Application TITAN-S360
- Application: Samba.Presentation.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.Net.Sockets.SocketException at System.Net.Sockets.Socket.Receive(Byte[], Int32, Int32, System.Net.Sockets.SocketFlags) at Samba.Addon.CalleridDevices.CellularCallerId+<>c__DisplayClass7_0.b__1() at System.Threading.ThreadHelper.ThreadStart_Context(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.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at System.Threading.ThreadHelper.ThreadStart()
Looks like a caller id device. Specifically the android caller id
Hi Jesse, Merry Christmas,
Yes the System using the Android CallerID.
But this same setup we use at many locations,
and this location is the only one having this crashing issue.
any suggestion on what to do to troubleshoot this please?
Delete the device and redo the setup.
1 Like
OK I will give that a go. Thanks~
This is happening when the Socket (low-level connection to the android device) is receiving data and I’m wondering if the connection is being closed/aborted by the android device. It’s hard to know for sure without the full exception and stack trace, but that would require changes to the source code to log it.
As this is affecting only one location, I would check if the phone is maybe going to sleep or suspending the wifi interface for some reason. I would also check for signal interference that could cause the connection to momentarily drop.
I’d also try the CID app on another device if it’s easy to do a SIM swap to another phone temporarily.
1 Like