Troubleshooting: System errors

INVOICES has an error-handling system that is activated when problems occur. If the error cannot be corrected automatically, INVOICES ends the current process(es) to minimize the consequences and displays an error message on the screen.

Error logs

Sometimes you can easily correct the error—for example, by switching on the scanner or plugging in the printer cable. At other times, the error can be more serious. Simple errors display an error message, and serious errors also contain an error number. When an error occurs that does not require INVOICES to close, a log is created.

If an error occurs that you cannot explain or correct, report it to ReadSoft, including all the error messages, error logs, crash dump (if any), and all available information regarding the situation (for example, what led to the error, screenshots, etc.)

Error reports

Some errors require INVOICES to close. When this occurs, a dialog is displayed. You can use this dialog to create an error report that you can send to ReadSoft to help diagnose the problem and improve INVOICES. The error report is a ZIP file that contains:

The name of the ZIP file is dump_ModuleYYYYMMDD_HHMMSS.hhh.zip, where Module = the name of the module in which the error occurred, YYYYMMDD = the date, HHMMSS = the time, and hhh = milliseconds.

Disabling error messages and creating custom ones

You can prevent specific error messages from appearing to the user in the application. You can also create custom error messages that replace ones that display numbers only. See Errorcodes.ini: Overview (INI File Help topic).

Location and name of error log files