We have upgraded FileMaker pro 11 to 15 on windows7 and 8 machine. After this migration , we are facing FileMaker pro crash issue.

Application: FileMaker Pro.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.DivideByZeroException
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
   at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
   at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)
   at System.Windows.Window.ShowHelper(System.Object)
   at System.Windows.Window.Show()
   at System.Windows.Window.ShowDialog()
   at <Module>.WPFCBase.DoModal(WPFCBase*)
   at <Module>.WPFCDialog.DoModal(WPFCDialog*)

--------------------------------------------------------------------------------------------

Faulting application name: FileMaker Pro.exe, version: 15.0.1.119, time stamp: 0x5706f6cd
Faulting module name: ViewSystem.dll, version: 15.0.1.50139, time stamp: 0x5706fbeb
Exception code: 0xc0000094
Fault offset: 0x00069cfb
Faulting process id: 0xdfc
Faulting application start time: 0x01d208ef6876fbd1
Faulting application path: C:\Program Files (x86)\FileMaker\FileMaker Pro 15\FileMaker Pro.exe
Faulting module path: C:\Program Files (x86)\FileMaker\FileMaker Pro 15\ViewSystem.dll
Report Id: ed5ed57f-74ea-11e6-9d44-54271ecb41ea

 

In application event logs , Framework Version: v4.0.30319 > but when I look into .net framework - it says 4.6. In application log's framework version is equal to .Net framework version ???????

 

Are you using plugins? It has been my experience that plugins are a very common cause of crashes.

Yes , we use base element(32 bit)

Try removing it and see if it still crashes.

Its not crashing on all machine. On some of win 7/8 m/c its working fine.

Edited September 7, 20169 yr by sam215