Invoice modulesIf an Invoice module crashes
If an Invoice module terminates abnormally:
-
Start the module that crashed.
-
If the problem is still there, there may still be items locked in the database. Unlock any locked invoice profiles or invoice definitions.
-
If the problem persists, there may still be items locked in the database. Use the procedure described in Searching for documents to find any locked objects. (Sort hits using the Locked by or Lock time filter to find locked objects.) Then select locked items, right-click them, and select Unlock.
Or, if you were processing batches, follow the instructions in Ways of handling locked batches.
-
If some documents are now corrupt, you may need to reprocess them.
If the above steps fail, please contact your local distributor or ReadSoft Support.
An error report (crash dump) is generated
If an Invoice module terminates abnormally, an error report is generated. It contains:
-
A Windows mini-dump file.
-
Information about which files and versions were run.
-
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 crash dump can be switched off by setting this flag in Eiglobal.ini:
[Options]
EnableCrashReport=0
In most invoice solutions, Invoice Interpret (eiitrp.exe) runs in the background during production. Depending on the respective
Error logs for Invoice modules