Question

Error Creating Window Handle message

  • 12 March 2024
  • 3 replies
  • 35 views

Userlevel 3
Badge +8
  • Sidekick (Customer)
  • 31 replies

I have a user that frequently gets this error when trying to Final Post a supplier invoice - particularly from the Instant Authorization screen. 

Then, it will terminate her IFS session. 

Does anyone know a remedy for this? I don’t have other users in her department reporting this problem.

We are in IFS v10 - UPD 12

 

 


3 replies

Userlevel 6
Badge +19

Hello @Joy 

I would recommend removing IFS log files from his computer and restart application. See if still error exist. If so then create a support ticket.

  1. Log out from application
  2. Go to folder -→ C:\Users\{User NAme}\AppData\Local\Apps
  3. You will find here a folder name 2.0
  4. Remove the folder completely. This may take some time to complete.
  5. Log in application

This will remove all logs and downloads from application. User will download all dll one more time.

Hope this helps

Userlevel 2
Badge +7

We have had similar issues with APPS 10 UPD16.

it seems to creep up randomly. 

 

here is the full error stack.

Ifs.Fnd.FndSystemException: 
Explorer: An Unhandled Exception has occurred ---> 
System.ComponentModel.Win32Exception: Error creating window handle. 
at System.Windows.Forms.NativeWindow.CreateHandle(CreateParams cp) 
at System.Windows.Forms.Control.CreateHandle() 
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible) 
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible) 
at System.Windows.Forms.Control.CreateControl() 
at System.Windows.Forms.Control.OnVisibleChanged(EventArgs e) 
at System.Windows.Forms.ScrollableControl.OnVisibleChanged(EventArgs e) 
at System.Windows.Forms.Control.OnParentVisibleChanged(EventArgs e) 
at System.Windows.Forms.Control.OnVisibleChanged(EventArgs e) 
at System.Windows.Forms.ScrollableControl.OnVisibleChanged(EventArgs e) 
at System.Windows.Forms.Control.OnParentVisibleChanged(EventArgs e) 
at System.Windows.Forms.Control.OnVisibleChanged(EventArgs e) 
at System.Windows.Forms.ScrollableControl.OnVisibleChanged(EventArgs e) 
at System.Windows.Forms.Control.OnParentVisibleChanged(EventArgs e) 
at System.Windows.Forms.Control.OnVisibleChanged(EventArgs e) 
at System.Windows.Forms.ScrollableControl.OnVisibleChanged(EventArgs e) 
at System.Windows.Forms.Form.OnVisibleChanged(EventArgs e) 
at System.Windows.Forms.Control.SetVisibleCore(Boolean value) 
at System.Windows.Forms.Form.SetVisibleCore(Boolean value) 
at System.Windows.Forms.Control.set_Visible(Boolean value) 
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context) 
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context) 
at System.Windows.Forms.Application.RunDialog(Form form) 
at System.Windows.Forms.Form.ShowDialog(IWin32Window owner) 
at Ifs.Fnd.Explorer.Extenders.SearchExplorerManager.SearchExploreManager.Ifs.Fnd.Explorer.Interfaces.IFndSearchExploreManager.ShowSearchDialog(FndSearchDialogSettings settings, FndClientSearch& clientSearch) 
at Ifs.Fnd.ApplicationForms.cDataSource.DataRecordSearchDialog() 
at Ifs.Fnd.ApplicationForms.cDataSource.DataRecordQueryDialog() 
at Ifs.Fnd.ApplicationForms.cTableWindowBase.DataRecordQueryDialog() 
at Ifs.Fnd.ApplicationForms.cTableWindowBase.vrtDataRecordQueryDialog() 
at Ifs.Fnd.ApplicationForms.cDataSource.vrtDataRecordQueryDialog() 
at Ifs.Fnd.ApplicationForms.cDataSource.DataSourcePopulate(SalNumber nWhat, SalNumber nParam) 
at Ifs.Fnd.ApplicationForms.cTableWindowBase.DataSourcePopulate(SalNumber nWhat, SalNumber nParam) 
at Ifs.Application.Appviz.Visualizer.VisualizationTableWindow.vrtDataSourcePopulate(SalNumber nWhat, SalNumber nParam) 
at Ifs.Fnd.ApplicationForms.cDataSource.vrtDataSourcePopulate(SalNumber nWhat, SalNumber nParam) 
at Ifs.Fnd.ApplicationForms.cDataSource.cDataSource_WindowActions(Object sender, WindowActionsEventArgs e) 
at PPJ.Runtime.Windows.SalWindow.InvokeWindowActions(WindowActionsEventArgs args, SalContext context, Int32 startIndex) 
at PPJ.Runtime.Windows.SalWindow.SendClassMessage(Int32 msg, SalNumber wParam, SalNumber lParam, Type startType) 
at PPJ.Runtime.Sal.SendClassMessage(SalNumber message, SalNumber wParam, SalNumber lParam) 
at Ifs.Application.Appviz.Visualizer.VisualizationTableWindow.VisualizationTableWindow_WindowActions(Object sender, WindowActionsEventArgs e) 
at PPJ.Runtime.Windows.SalWindow.InvokeWindowActions(WindowActionsEventArgs args, SalContext context, Int32 startIndex) 
at PPJ.Runtime.Windows.SalWindow.SendClassMessage(Int32 msg, SalNumber wParam, SalNumber lParam, Type startType) 
at PPJ.Runtime.Sal.SendClassMessage(SalNumber message, SalNumber wParam, SalNumber lParam) 
at Ifs.Application.Shpord.tbwShopOrd.tbwShopOrd_OnPM_DataSourcePopulate(Object sender, WindowActionsEventArgs e) 
at Ifs.Application.Shpord.tbwShopOrd.tbwShopOrd_WindowActions(Object sender, WindowActionsEventArgs e) 
at PPJ.Runtime.Windows.SalWindow.InvokeWindowActions(WindowActionsEventArgs args, SalContext context, Int32 startIndex) 
at PPJ.Runtime.Windows.SalWindow.FireWindowActions(Int32 msgCode, IntPtr wParam, IntPtr lParam) 
at PPJ.Runtime.Windows.SalWindow.DispatchThenProcess(Message& m) at PPJ.Runtime.Windows.SalWindow.ProcessWndProc(Message& m) 
at PPJ.Runtime.Windows.SalForm.WndProc(Message& m) at PPJ.Runtime.Windows.SalFormTableWindow.WndProc(Message& m) 
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) 
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) 
--- End of inner exception stack trace ---

Really would love to see a permanent solution for this. 

Any help is appreciated. 

Userlevel 3
Badge +8

Thank you both for your replies. 

 

I’ve tried clearing the .dll cache in the past when users have had this issue, or similar issues - and it is never a permanent solution. 

 

Is there any other recommendation? Or is clearing the .dll cache intermittently or when the error occurs the only fix?

 

We are about to go to UPD 22 in the upcoming weeks. Is there a release that is better able to regulate these errors?

 

Thanks,

Joy

Reply