Skip to Content
Information
This documentation supports the 20.02 version of BMC CMDB.To view an earlier version, select the version from the Product version menu.

Reconciliation Engine jobs that do not start

Perform the following procedure when you notice that Reconciliation Engine jobs are not running even though they were scheduled to run or triggered manually.

Parameter or component

Troubleshooting information

Reconciliation job

Verify that the Job status for the specific job is set to Active.

arrecond.exe

Verify that the arrecond.exe process (Reconciliation Engine) is running and that its process ID (PID) is not changing every minute.
The Reconciliation Engine process ID must remain the same, which denotes that the dispatcher is not abruptly restarting.

armonitor.log file

Check whether there is an entry indicating that the arrecond.exe process is restarting every few seconds.

If the armonitor.log file shows frequent entries indicating that thearrecond.exe process is restarting every few seconds, then there is an issue with the reconciliation engine process. Check the arrecond.log file for details.

Reconciliation Engine

Verify that the Reconciliation Engine is connected to the correct  BMC Remedy AR System server instance.
For information about how to verify that the Reconciliation Engine is connected to the correct AR System server instance see Reconciliation-job-logging.

Success

Tip

To verify that a specific process is running on a Microsoft Windows computer, view the Processes tab on the Task Manager. On UNIX, use the ps - ef | grep <processName> command.

arerror.log, and armonitor.cfg (armonitor.conf ) files

If the Reconciliation Engine is not running or if it is not connecting to the AR System server, search the arerror.log, and armonitor.cfg (armonitor.conf ) files for errors.

Application Pending form

Wait for a few seconds for the record in the Application Pending form to be processed and the job to start.
The job usually starts within a few seconds when the dispatcher is running correctly. The dispatcher instructs the Reconciliation Engine to perform tasks based on the entry in the Application Pending form.

Success

Tip

Search for the Application Pending form and open it in Search mode to view the job record.

In case of server group configuration, confirm if the reconciliation process is running on the server where its ranked in application ranking form.

Dispatcher


  1. Perform the following steps to verify that the dispatcher is running:
    1. To verify that the dispatcher is configured to run, search for the arsvcdsp.exe process in the armonitor.cfg file.
    2. From the Microsoft Windows Task Bar or UNIX console, verify that the dispatcher process is running and that its process ID is not changing every minute.
      The dispatcher process ID must remain the same, which denotes that the dispatcher is not abruptly restarting.

  2. If the dispatcher is not running, wait for the amount of time specified in the Polling Interval field on the Server Configuration Editor dialog box.

    Success

    Tip

    You can also reduce the Polling Interval time. This ensures that the arrecond.exe process polls the Reconciliation Engine job queue more often.


arrecond and arsvcdsp processes

If the arrecond and arsvcdsp processes are running, but the Application Pending entry is not processed, perform the following steps to enable dispatcher logging.

  1. In the ar.cfg (ar.conf ) configuration file, set the Dispatch-Log-File entry to <fullPath>/dispatch.log.
  2. Restart the AR System server.

 Execute Job activities

For jobs that are started by way of workflow or Execute Job activities, verify that the job name is correct and that the status of the specified job is Active on the Job History Console.

arerror.log

Examine arerror.log to verify that the server was down for maintenance during a scheduled run of the Reconciliation Engine Job.


Related topics

Configuring-core-CMDB-components-and-plug-ins

Reconciliation-job-logging




 

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

BMC CMDB 20.02