Error when adding new scripts
Posted: 21 Jun 2021 11:04
Hi,
We've recently been receiving an error when trying to add new scripts. The error is shown below:
As soon as this error is shown (either when testing a script or trying to save a new script), the application gives me the option to STOP or CONTINUE. If I choose STOP the application hangs completely. I also get this error as soon as I open up the General Settings view.
We have a lot of already working scripts in this setup and we only started receiving this error very recently.
Any help on how I could solve this would be greatly appreciated.
Thanks!
We've recently been receiving an error when trying to add new scripts. The error is shown below:
Code: Select all
19/06/2021 08:37:17 [v4.2.4.2]:********** Error/Exception Information **********
Error Message: The given path's format is not supported.
Error Type: System.NotSupportedException
Error Source: mscorlib.Void EmulateFileIOPermissionChecks(System.String)
********** System Stack Trace **********
at System.Security.Permissions.FileIOPermission.EmulateFileIOPermissionChecks(String fullPath)
at System.Security.Permissions.FileIOPermission.QuickDemand(FileIOPermissionAccess access, String fullPath, Boolean checkForDuplicates, Boolean needFullPath)
at System.IO.FileInfo.Init(String fileName, Boolean checkHost)
at ProppFrexx.ScriptLibrary.Save()
at ProppFrexx.ScriptLibraryConfigDialog.Xw6i()
at ProppFrexx.ScriptLibraryConfigDialog.Pw6O(Object , EventArgs )
at System.Windows.Forms.Control.OnClick(EventArgs e)
at DevExpress.XtraEditors.BaseButton.OnMouseUp(MouseEventArgs e)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at DevExpress.Utils.Controls.ControlBase.BaseWndProc(Message& m)
at DevExpress.XtraEditors.BaseControl.WndProc(Message& msg)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
********** End **********
We have a lot of already working scripts in this setup and we only started receiving this error very recently.
Any help on how I could solve this would be greatly appreciated.
Thanks!