You are viewing limited content. For full access, please sign in.

Question

Question

Connector 10.3 Hotfix - Crashing

Connector
Updated May 16, 2018
asked on May 4, 2018 • Show version history

Our users originally discovered the issue with Connector not working with Chrome version 66.0.3359.117 (Topic). After applying the Connector 10.3 Hotfix, Connector works however, Connector is now crashing randomly for all the users we applied the Hotfix to. Some machines are Windows 7 while others are Windows 10. All are 64 bit.

Some of the users have to completely restart their computer to get it working again. Connector will crash several times a day for each user.

Here are the Windows Application Error logs from two of the machines that are crashing:

 

Computer 1:

Application: LFC.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ComponentModel.Win32Exception
   at MS.Win32.SafeNativeMethods.SetTimer(System.Runtime.InteropServices.HandleRef, Int32, Int32)
   at System.Windows.Threading.Dispatcher.SetWin32Timer(Int32)
   at System.Windows.Threading.Dispatcher.UpdateWin32TimerFromDispatcherThread(System.Object)
   at System.Windows.Threading.Dispatcher.AddTimer(System.Windows.Threading.DispatcherTimer)
   at System.Windows.Threading.DispatcherTimer.Restart()
   at System.Windows.Threading.DispatcherTimer.Start()
   at System.Windows.Threading.DispatcherTimer.set_IsEnabled(Boolean)
   at System.Windows.Input.InputManager.InvalidateInputDevices()
   at System.Windows.Media.MediaContext.RenderMessageHandlerCore(System.Object)
   at System.Windows.Media.MediaContext.RenderMessageHandler(System.Object)
   at System.Windows.Interop.HwndTarget.OnResize()
   at System.Windows.Interop.HwndTarget.HandleMessage(MS.Internal.Interop.WindowMessage, IntPtr, IntPtr)
   at System.Windows.Interop.HwndSource.HwndTargetFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)

Faulting application name: LFC.exe, version: 10.3.0.267, time stamp: 0x5ae91f02
Faulting module name: KERNELBASE.dll, version: 10.0.16299.371, time stamp: 0x6369e29f
Exception code: 0xe0434352
Fault offset: 0x0000000000014008
Faulting process id: 0x2450
Faulting application start time: 0x01d3e3ab67bed399
Faulting application path: C:\Program Files\Laserfiche\LFConnector\LFC.exe
Faulting module path: C:\windows\System32\KERNELBASE.dll
Report Id: cf277b8a-6e6b-4121-8ddb-832fd5a97e07
Faulting package full name:
Faulting package-relative application ID:

 
Computer 2:

Application: LFC.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ComponentModel.Win32Exception
   at MS.Win32.UnsafeNativeMethods.CreateWindowEx(Int32, System.String, System.String, Int32, Int32, Int32, Int32, Int32, System.Runtime.InteropServices.HandleRef, System.Runtime.InteropServices.HandleRef, System.Runtime.InteropServices.HandleRef, System.Object)
   at MS.Win32.HwndWrapper..ctor(Int32, Int32, Int32, Int32, Int32, Int32, Int32, System.String, IntPtr, MS.Win32.HwndWrapperHook[])
   at System.Windows.Threading.Dispatcher..ctor()
   at System.Windows.Threading.Dispatcher.get_CurrentDispatcher()
   at Laserfiche.Connector.Service.MonitorService+OverlayControlDirectoryImpl.StartOverlayButtonThread()
   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()


Faulting application name: LFC.exe, version: 10.3.0.267, time stamp: 0x5ae91f02
Faulting module name: KERNELBASE.dll, version: 10.0.14393.2189, time stamp: 0x5abdad60
Exception code: 0xe0434352
Fault offset: 0x0000000000033c58
Faulting process id: 0x2590
Faulting application start time: 0x01d3e3a890e0ed03
Faulting application path: C:\Program Files\Laserfiche\LFConnector\LFC.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 28840ee3-311f-4324-8632-97eaed1861bd
Faulting package full name:
Faulting package-relative application ID:

 

0 0

Replies

replied on May 16, 2018

The hotfix from https://support.laserfiche.com/kb/1013958/list-of-changes-for-laserfiche-connector-10-3-update-1 has been updated to address the crash issue introduced by the original hotfix.

Please re-download and re-apply the hotfix.

1 0
replied on May 16, 2018

Thanks!

0 0
replied on May 11, 2018

I have the same issue on a computer.

 

Faulting application name: LFC.exe, version: 10.3.0.267, time stamp: 0x5ae91f02
Faulting module name: ntdll.dll, version: 6.1.7601.24117, time stamp: 0x5add228d
Exception code: 0xc0000005
Fault offset: 0x00000000000eb1e7
Faulting process id: 0x1b64
Faulting application start time: 0x01d3e9402bb5a25c
Faulting application path: C:\Program Files\Laserfiche\LFConnector\LFC.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 312b31b2-5544-11e8-b033-64006a5af60a

0 0
replied on May 11, 2018 • Show version history

Hi Tony and Eric,

We are investigating a fix to this (87905) and are planning to make it available through Support to ensure it is addressing the various ways this issue can come up. You may want to contact them (Although I'm not positive they have the fix yet, they may not until Monday). 

0 0
replied on May 16, 2018

We're having the same issue.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...