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

Wed Aug 31 03:32:09 2016 390695 : An error has occurred while loading a plug-in. (ARERR 8756)
Tue Sep 13 03:42:49.343 2016 ERROR (8760): Cannot establish a network connection to the AR System Plug-In server;
clm-pun-016351.bmc.com:9998

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

Mon Jan 22 10:27:16.210 2024 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	DSO note
ARDSWARN	DSO warning
ARDSERR	DSO error
ARNOTE	AR System note
ARWARN	AR System warning
ARERR	AR System error

Server error log

On this page