This documentation supports the 9.1 version of Remedy Action Request System.

To view the latest version, select the version from the Product version menu.

Server error log

The arerror.log file is always active, and logs all BMC Remedy 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 an BMC Remedy 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.

Details of arerror.log file

When you start the AR System server, important information such as, AR Server version, server license information and the various extensions that are loaded are displayed in arerror.log file. These are the important messages shown in arerror.log file for the convenience of the administrators. When the AR System server starts successfully and if there are any important errors, the errors are logged to arerror.log file. These messages indicate whether these are errors or warnings (ARERR, ERROR, WARN). For more information on error codes that are shown in the log files, see 1 to 999 - BMC Remedy 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 

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

Error codeDescription

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
ARERRAR System error
Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Colin Rolls
    • ARAPPERR ,ARNOTE, ERROR and ARERR can all appear in log, explanation of each and what the difference is needed.
    • need explanation that AR error numbers 1-999 can appear in log and a link to this page would be nice which lists server error messages: https://docs.bmc.com/docs/display/public/ars91/1+to+999+-+BMC+Remedy+AR+System+server+messages+and+notifications
    • some text about not being able to modify/rename the file until the ar server is stopped would be good
    • on startup of AR System service entries are written to arerror.log (loading extension, starting arserver etc.starting CMDB, etc) but these are not errors, needs explanation what these are exactly and what is 'normal'
    • examples of some errors would be good, for example if the database goes down and can't connect what is written to log.
    Jun 23, 2016 06:08
    1. Anagha Deshpande

      Hello Colin,

      Thanks for your feedback. I will discuss this with SME and will update the topic soon.

       

      Regards,

      Anagha 

      Jun 29, 2016 06:07
      1. Tushar Khanwalkar

        please update on all types  ARAPPERR ,ARNOTE, ERROR and ARERR that may appear in log, explanation of each and what the difference is needed

        Oct 13, 2016 08:15
        1. Anagha Deshpande

          Hello Tushar,

          Apologies for delayed response.

          I have updated the topic.

          Regards,

          Anagha 

           

          Jul 06, 2017 12:39
      1. Anagha Deshpande

        Hello Colin,

        Apologies for delayed response.

        I have updated the topic.

        Regards,

        Anagha 

        Jul 06, 2017 12:39