Enabling reconciliation job logs

The log file might be saved to the incorrect log path.

Solution:

When you specify the log file path, make sure that:

1. • The directory exists on the Remedy Action Request System server.
   • It is a directory and not a file name.
   • The Reconciliation Engine has permissions to create files in that directory.
     For testing purpose, specify a short log file path with no spaces.
     For example, 
     (Windows)C:\RELog.
     (UNIX)/tmp/RELog/.

If you do not specify a log file path or if the log file path is empty, the Reconciliation Engine log is generated in the Db subdirectory of your AR System server installation directory by default.

The server configuration settings are not updated on the Remedy Action Request System server.

If you change the server configuration settings and these settings are not updated in the ar.cfg or ar.conf file.

Solution:

The ar.cfg configuration file contains Remedy Action Request System server configuration changes. This file is located at <AR System installation directory>\ARSystem\Conf>.

To check if the settings are updated in the ar.cfg or ar.conf file:

1. Query the Application Pending form for records where 'Category' = "Reconciliation".
2. Verify that the Application Pending form contains an Update-Config record for the Reconciliation Engine.

You can also manually update the ar.cfg or ar.conf file to match the entries in the Modify Server Configuration window of the Reconciliation Manager and restart the Reconciliation Engine to configure the settings.

For more information about the ar.cfg file, see  ar.cfg or ar.conf  in the Remedy Action Request System online documentation.

When the Reconciliation Engine process stops abruptly, the armonitor configuration file restarts the process and a new process ID is assigned to it. Therefore, if you notice that the process ID changes frequently, it indicates that the reconciliation engine is constantly restarted.

Solution:

To verify if the process ID frequently changes, note its value every few minutes.

Verify the following on the Remedy AR System server:

• The Reconciliation Engine is running.
  The process name for the Reconciliation Engine is arrecond.exe on Windows and arrecond on UNIX.
• The value in the process ID field is not changing.

The arrecond.log file fails to log all activities related to the Reconciliation Engine schedule such as when the reconciliation engine started and stopped.

Solution:

Confirm that the arrecond.log file exists on the Remedy AR System server.

Solution:

1. Open the armonitor.cfg (armonitor.conf ) file on the Remedy AR System server.
   The armonitor.cfg file contains the commands that the armonitor binary executes. 

   (Windows) <AR System server installation Directory>\ARSystem\Conf 
   (UNIX) /etc/arsystem/<ARInstanceName>/

   For more information about the armonitor.cfg file, see  armonitor.conf or armonitor.cfg  in the Remedy Action Request System online documentation.

2. In the configuration file, search for the line entry that runs the 
   (Windows) arrecond.exe 
   (UNIX) arrecond.sh.
To view the arrecond.sh script, open it in a UNIX editor.

3. Note the value that is specified for the -i parameter. 
   The value specified for this parameter is a directory name, which must be the same as the Remedy AR System server installation directory.

4. If the directory name for the -i parameter is different than the Remedy AR System server installation directory, change it to match the Remedy AR System directory name.