If INVOICES terminates abnormally, an error report is generated. It contains a crash dump, information about which files and versions were run, and Eilocal.ini and Eiglobal.ini. This information is vital if you contact ReadSoft Support.
You are prompted to save this file. When you do, it is saved to the Log directory. The file name is dump_module_yyyy-mm-dd_HHMMSS.hhh.zip, where yyyy = year, mm = month, dd = day, HH = hour, MM = minute, SS = second, and hh = hundredths of a second.
The crash dump can be switched off by setting this flag in Eiglobal.ini:
[Options]
EnableCrashReport=0
Note: Depending on your EnableCrashReport setting, crash dumps are not necessarily generated if Interpret or Transfer crashes while running as a Windows service.
An Interpret crash can be caused by a specific invoice.
Create a Verify job that has only Scanned selected in the Status settings. Exclude other invoices from the job by deselecting other settings.
Run this job. The first invoice that is displayed is the one that is corrupt.
Delete this invoice and stop the job.
Try running the Interpret job again.
Starting a module after a crash
Our system crashed and we cannot process the invoices that were in the system at the time