This documentation applies to the 8.1 version of BMC Atrium Core, which is in "End of Version Support." You will not be able to leave comments.

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

AR System server logging

The BMC Remedy AR System server also provides error logs, such as arerror.log and arapi.log. The arerror.log file records all AR System server error messages, such as notifying you that your AR System server stopped responding, and so on.

For example, you might receive an ARERR 92 Timeout during database update error on the BMC Atrium Core client. One of the possible causes for this timeout error might be that the AR System server stopped responding. To troubleshoot this error, try to reproduce the error and examine other logs to identify the cause of the error.

The arapi.log file traces all AR System API calls that are run on the server. Both arerror.log and arapi.log files are located by default in the C:\Program Files\BMC Software\ARSystem\Arserver\Db subdirectory of your AR System server installation directory.

If you enable the Filter and SQL logging options , the log files are created under the Program Files\BMC Software\ARSystem\Arserver\Db subdirectory of your installation directory by default (Windows ) or <serverInstallationDirectory>/db (UNIX ). You can change the file names and location of any of these logs at any time.

Make sure that you examine the arerror.log and cmdbengdebug.log files for any CMDB Engine library loading errors, If any errors occurred when loading the library during AR System server starts up, BMC Atrium Core might not function correctly.

In addition to logging errors to the cmdbengdebug.log file, BMC Atrium Core also writes to the arerror.log file under certain circumstances, such as the following scenarios:

  • If the RPC program was not registered when making a BMC Atrium Core API call from a BMC Atrium Core client, an error is written to arerror.log. This error occurs because the AR System server did not load the CMDB Engine library.
  • If the OBJSTR:Class form that holds BMC Atrium CMDB metadata is not available on the server, an ARERR 9755 error is written to arerror.log, such as the following example, and the CMDB Engine library fails to load:

Thu May 03 15:01:21 2007 390600 : Error encountered while initializing (Initialization routine) the shared library (ARERR 9755) Thu May 03 15:01:21 2007 bmc.cmdb.cmdbEngine Thu May 03 15:01:22 2007 390600 : Form does not exist on server : OBJSTR:Class (ARERR 303)

For more information about these AR System server log files, see Troubleshooting in the BMC Remedy Action Request System online documentation.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments