Skip to main content

Hi,

 

We had not problem on Windows7. Recently switched to Win 10 1903/1909 and IFS EE crashing randomly without error to enduser. Windows eventviewer shows event 1000 and 1026

Anyone having same issue?

 

Greetings,

Jos

 

1000

Faulting application name: Ifs.Fnd.Explorer.exe, version: 4.80.33.0, time stamp: 0x5465b84a

Faulting module name: clr.dll, version: 4.8.4075.0, time stamp: 0x5dd8a356

Exception code: 0xc000041d

Fault offset: 0x0002137a

Faulting process ID: 0x5a80

Faulting application start time: 0x01d5d06a41a05e40

Faulting application path: \\193.210.165.190\runtime\Ifs.Fnd.Explorer.exe

Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll

Report ID: f92d931e-2780-486f-9615-09f6c3581c2b

Faulting package full name:

Faulting package-relative application ID:

 

1026

Application: Ifs.Fnd.Explorer.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: System.Runtime.InteropServices.SEHException

   at System.Reflection.RuntimeAssembly.GetResource(System.Reflection.RuntimeAssembly, System.String, UInt64 ByRef, System.Runtime.CompilerServices.StackCrawlMarkHandle, Boolean)

   at System.Reflection.RuntimeAssembly.GetManifestResourceStream(System.String, System.Threading.StackCrawlMark ByRef, Boolean)

   at System.Reflection.RuntimeAssembly.GetManifestResourceStream(System.Type, System.String, Boolean, System.Threading.StackCrawlMark ByRef)

   at System.Resources.ResourceManager.GetResourceSet(System.Globalization.CultureInfo, Boolean, Boolean)

   at System.ComponentModel.ComponentResourceManager.FillResources(System.Globalization.CultureInfo, System.Resources.ResourceSet ByRef)

   at System.ComponentModel.ComponentResourceManager.FillResources(System.Globalization.CultureInfo, System.Resources.ResourceSet ByRef)

   at System.ComponentModel.ComponentResourceManager.FillResources(System.Globalization.CultureInfo, System.Resources.ResourceSet ByRef)

   at System.ComponentModel.ComponentResourceManager.ApplyResources(System.Object, System.String, System.Globalization.CultureInfo)

   at Ifs.Fnd.FeatureContainer.FeatureErrorControl.InitializeComponent()

   at Ifs.Fnd.FeatureContainer.FeatureErrorControl..ctor()

   at Ifs.Fnd.FeatureContainer.FndFeatureContainer.ShowFeatureErrorControl(Ifs.Fnd.Core.FndUrlAddress, System.Exception)

   at Ifs.Fnd.FeatureContainer.FndFeatureContainer.OnNavigateError(Ifs.Fnd.Core.FndUrlAddress, System.Exception)

   at Ifs.Fnd.FeatureContainer.FndFeatureContainer.NavigateInternal(Ifs.Fnd.Core.FndUrlAddress, Ifs.Fnd.Explorer.Interfaces.FndNavigatorEntry, Boolean, NavigationDirection, Int32, Boolean)

   at Ifs.Fnd.FeatureContainer.FndFeatureContainer.Navigate(Ifs.Fnd.Core.FndUrlAddress, Ifs.Fnd.Explorer.Interfaces.FndNavigatorEntry, FndNavigationOptions)

   at Ifs.Fnd.FeatureContainer.FndFeatureContainer.Navigate(Ifs.Fnd.Explorer.Interfaces.FndNavigatorEntry, FndNavigationOptions)

   at Ifs.Fnd.FeatureContainer.FndFeatureContainer.Navigate(Ifs.Fnd.Explorer.Interfaces.FndNavigatorEntry)

   at Ifs.Fnd.Explorer.UI.NavigationTreeContainer.treeViewNavigator_NodeMouseClick(System.Object, System.Windows.Forms.TreeNodeMouseClickEventArgs)

   at System.Windows.Forms.TreeView.OnNodeMouseClick(System.Windows.Forms.TreeNodeMouseClickEventArgs)

   at System.Windows.Forms.TreeView.WmNotify(System.Windows.Forms.Message ByRef)

   at System.Windows.Forms.TreeView.WndProc(System.Windows.Forms.Message ByRef)

   at System.Windows.Forms.Control+ControlNativeWindow.OnMessage(System.Windows.Forms.Message ByRef)

   at System.Windows.Forms.Control+ControlNativeWindow.WndProc(System.Windows.Forms.Message ByRef)

   at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)

 

H @mesjd0061 ,

 

Could you please tell us the IFS Application version that you’re trying to run?


Hi Himasha,

 

IFS EE Client version 4.80.33.0

Server version 5.80.22.1

 

IFS8 SP2 Apps server running on Windows Server 2012 R2, but no changes made to server-environment.

 

Greetings,

Jos

 


Hi @mesjd0061,

 

IFS Applications 8 supports only up to Windows 10 version 1607 64-bit (em64t,amd64). Therefore, you will face issues here and there when using the latest Windows versions to run the IFS Client.

 

Hope this helps!


As mentioned by @Himasha Kapugeekiyanage  this possible cause for this issue shoudl be the  End User machines are using de-supported Windows version.

Just for the information is the IFS EE crashing when doing specific operations? 


Hi Charith,

 

No specific operations. It can run for 4 hours without problem and then crash 2 times in 1 hour. Some users have up to 10 crashes on 1 day with clr.dll, while others only have it 2 times a month.

 

Jos


Hi @mesjd0061,

 

I’ll attach the Supported Platforms document for Applications 8 for you to refer. 


Hi @mesjd0061 ,

Have you tried uninstalling any of the old versions of the IEE Client from that machine and opening IEE URL again?  This will install it fresh. 

 

Thanks,

Kasun


Reply