Reconciliation Engine aborted jobs due to being abruptly restarted
If you abruptly restarted the Reconciliation Engine, the Related Runs table might indicate that the job has started, but the job might not be actually running.
To troubleshoot issues caused due to abrupt restarting of the Reconciliation Engine
- Log in to the BMC Atrium Core Console and navigate to:
Application Launcher > Applications > Reconciliation - Click the History tab.
- From the Show all Job Runs With Status list, select Started.
- Specify the start date and end date for the job.
- Make sure that there are no records displayed in the results table.
- Log on to your BMC Remedy AR System server as an Administrator.
- Open the Reconciliation Job Runs form in Search mode and click the Search button on the toolbar.
- Select the record that has a value of Started in the Run Status column.
- From the main menu, choose Actions > Delete.
- Verify that the Application Pending form contains no extra records that instruct the Reconciliation Engine to trigger the same job.
Extra records that trigger the same job might be created when you manually start a job and click the Start Job button several times. - To resolve the unspecified details error, examine the arrecond.log and the Reconciliation Engine log file for errors.
If you did not specify a path for the Reconciliation Engine log file using the Settings option on the Reconciliation Manager console, the arrecond.log and Reconciliation Engine log files are located in the C:\Program Files\BMC Software\AtriumCore\logs subdirectory of by default.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*