It is recommended to enable exceptions display and logging for GN4 applications. This helps to pinpoint the issues with the software.
Enable exceptions display by a shortcut, on a locally installed software Firstly, create a shortcut to the GN4 application, and then modify it adding the option /showexceptions. Then, run the application from the shortcut: it should display the exception that causes the fault. Click the Copy to Clipboard button, and then paste the error message in the mail to the Miles 33 support desk. An example: D:\TERA\gn4\bin\Fred4.exe /showexceptions Enable exceptions display for ClickOnce run applications This is available only in version 2.0 or newer. See ClickOnce and command-line switches. |
Enable exceptions logging in a file by a shortcut, on a locally installed software Firstly, create a shortcut to the GN4 application, and then modify it adding the option /logexceptions. Then, run the application from the shortcut: it should log all the exceptions that cause the fault. An example: D:\TERA\gn4\bin\Fred4.exe /showexceptions /logexceptions Enable exceptions logging for ClickOnce run applications See the solution B in the Logging GN4 system exceptions in a local file topic. |
See also
•Auto-reporting of GN4 system exceptions via email
•Logging GN4 system exceptions in a local file
•Logging system exceptions for Web interface
•"Client applications e.g. Ted4 or Fred4 may crash at startup..." condition in GN4 may crash when...
•GN4 applications command line parameters