Troubleshooting: System errors

Note: A separate topic describes what to do If an Invoice module crashes.

DOCUMENTS has an error-handling system that is activated in abnormal situations. If the error cannot be corrected automatically, DOCUMENTS ends the current processes to minimize the consequences and displays an error message. Simple errors give an error message, and serious errors also give an error number.

When you see an error message, write down the message and what you were doing when it appeared.

If it is a database error, make a note of all error messages and codes, as well as the situation that preceded the problem, and then try the following steps:

1. Close all modules. Then restart them one by one, noting any error messages.

2. 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.

3. Now restart the module(s), noting any error messages.

4. If the program still fails to run, you can try deleting the first document. (See also Reprocessing documents.)

If you need additional information about the error, check the error logs (see below).

If an error occurs that you cannot explain or correct, report it to ReadSoft Support. Your database's recovery tools may be useful.

Error logs

When an error occurs that does not require DOCUMENTS to close, a log is created:

• Administration and Production modules

• Invoice modules 
   

(Where to find the log files.)

Related topics

Troubleshooting

Unlocking invoice configuration data

Unlocking databases