Server error log

The arerror.log file is always active and logs all AR System server error messages. Any message that represents a serious or fatal server error is reported in this file, including messages that cannot be returned to a user, or that are not appropriate for return.

The logged messages include information about termination of or failed server processes. A termination entry about a server process also appears for normal shutdown. For example, any time a AR System server shuts down, a message is written to this file.

On Windows, this file is stored in the ARSystemInstallDir\arserver\Db directory. On UNIX systems, this file is stored in the ARSystemInstallDir/db directory. Check this file regularly to see if your servers are reporting errors.

Related topics

Enabling-and-analyzing-logs

Analyzing-logs

Details of arerror.log file

When you start the AR System server, important information such as, AR System server version, server license information and the various extensions that are loaded are displayed in arerror.log file.

When the AR System server starts successfully and if there are any important errors, they are logged to arerror.log file. For more information on error codes that are shown in the log files, see 1-to-999-AR-System-server-messages-and-notifications.

Example — Error
2025-03-04T00:50:15.340+0000 Error parsing Form AR System Administration: DeleteEntryAuditConfiguration
2025-03-04T00:50:15.341+0000 ERROR (402): Incorrect format in the definition file; Decoding error; Inconsistent data: 20 items found, 21 expected

Escalation failures in the arerror.log file

The arerror.log file also contains information about failed escalation errors, such as cleanup escalations or auto-close escalations. It includes details about the failed escalations and the reasons for the failure. This information helps in troubleshooting escalation failures without having to enable the escalation logs. 

The following example shows an escalation error in the server error log file:

Example — Escalation Error
2025-04-17T22:33:41.741+0000  Error while performing escalation action Escalation Error (Overlay Group 0) on
form EscalationError for entry 000000000000001 ERROR (303): Form does not exist on server; noform

The following table lists the various error codes shown in the logs:

Error code

Description

ARAPPNOTE

Application note

ARAPPWARN

Application warning

ARAPPERR

Application error

ARDSNOTE

DSOnote

ARDSWARN

DSOwarning

ARDSERR

DSOerror

ARNOTE

AR Systemnote

ARWARN

AR Systemwarning

ARERR

AR Systemerror

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*