Audit errors

The audit server uses error messages. See $BSE/log/log.audit for more information about the cause of the error.

You can receive one of these error messages:

E_AUD_SETUP 251 The audit setup is not correct.

This error can occur if the specification in the $BSE/lib/audit_spec file is not in the proper format.

TOSEQ 6 SECURITY 28 MAXSEQSIZE 25K or

No table/company number combination.

aa:00a:TOSEQ 6 SECURITY 28 MAXSEQSIZE 25K

Incorrect company number.

*:*:TOSEQ 6 SECURITY 28 MAXSEQSIZE 5K

The maximum sequence size limit is less than the specified limits. For details about the format of this file, refer to Format of audit files. This error can also mean that the current sequence file was illegally removed, or that the sequence files were removed without using the 4GL interface. Audit files that are used during the first run can also cause this error.

E_AUD_CORRUPT 252 An audit file is corrupt.

Some corruption of the information file has occurred. A mismatch exists in sequence headers in the information file and the sequence file.

E_AUD_LOCKED 253 Another user has locked the audit file.

Multiple users are trying to use the same audit file at the same time. The audit file is locked before the file can be modified and, as a result, the next user receives an error message.

E_AUD_ABORT 254 Commit transaction has failed in audit server.

The audit file is changed when the audit-data is written to the audit file. When too many files are opened and the maximum limit is reached, the LRU file is closed. This error can refer to the file used in the transaction. When the file is reopened, the starting date time of the sequence header is checked with memory data structure. If the times do not match, the E_AUD_ABORT error is returned.