Skip to main content
Question

Error when previewing IFS APPS10

  • 11 July 2024
  • 3 replies
  • 22 views

Hello,

On a new user station, we have this error when previewing a report:

Ifs.Fnd.FndSystemException: Explorer: An Unhandled Exception has occurred ---> System.ComponentModel.Win32Exception: Accès refusé
   at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
   at System.Diagnostics.Process.Start()
   at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
   at Ifs.Application.InfoServicesFramework.PDFFileHandler.OpenInExternalViewer()
   at Ifs.Application.InfoServicesFramework.PrintDialog.PreviewReport(PrintInstance instance)
   at Ifs.Application.InfoServicesFramework.PrintDialog.cmdPreview_Execute(Object sender, FndCommandExecuteEventArgs e)
   at Ifs.Fnd.Windows.Forms.FndCommand.OnExecute(Component component)
   at Ifs.Fnd.Windows.Forms.FndCommandButton.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.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 ---

 

The problem seems to come from a missing authorization in a Windows directory, but I can't find the reason.
Have you had this problem before?

Thanks.

3 replies

Userlevel 5
Badge +13

Any ideas?
Thanks in advance

Userlevel 4
Badge +8

It seems Like a permission issue. what is the exact window and the test steps?

 

Userlevel 5
Badge +13

Hi @Shehan Chandrasekara,

This problem is due to a change of computer.

The user is using the same IFS user account with the same permissions.
The problem seems to come from an unauthorized directory...

To trigger the error, simply launch a report preview.

Thanks for your feedback.

Reply