Troubleshooting Reconciliation Engine aborted jobs

• To troubleshoot classId does not exist error message
• To troubleshoot issues caused due to abrupt restarting of the Reconciliation Engine
• To troubleshoot jobs aborted due to insufficient memory
• Related topics

To troubleshoot classId does not exist error message

You might encounter the Class ID of namespace does not exist error message if the class ID you specified is hidden, if a class with such a name does not exist, or if the class ID field is blank.

1. In Remedy Developer Studio, search for the RE:Precedence form.
2. Double-click the Debug_pag field that contains the Debug tab.
3. Clear the Visible box on the Display page and save the form.
4. Search for the Precedences form from the Object List.
5. Open the Precedences form in Search mode and click Search again.
6. Select the specific precedence from the Search results list and make sure that the Class Instance ID and the Attribute Instance ID fields are not blank.
7. Delete the job entry that is assigned with the given Precedence Group.
8. In the Reconciliation console, create the job entry again and run the job.

To troubleshoot issues caused due to abrupt restarting of the Reconciliation Engine

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.

1. Log in to CMDB Portal and navigate to Jobs > Manage Reconciliation
2. Click the Executed tab in Jobs
3. Make sure that there are no records displayed in the results table.
4. Log on to your Remedy Action Request System server as an Administrator.
5. Open the Reconciliation Job Runs form in Search mode and click the Search button on the toolbar.
6. Select the record that has a value of Started in the Run Status column.
7. From the main menu, choose Actions > Delete.
8. 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.
9. 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 <AR install directory>\AtriumCore\logs subdirectory of by default.

To troubleshoot jobs aborted due to insufficient memory

If your computer does not have enough memory space, your reconciliation jobs might abort.

1. Check the arerror.log file to determine whether problems with the Remedy Action Request System server or arrecond executable occurred.
   For more information about the arerror.log file, see AR System server logging.
2. Monitor the amount of memory available on your computer and check the processes that are consuming large amounts of memory.
3. Add more disk space to the server TEMP disk or redirect TEMP to another disk that has more disk space.
4. Examine arrecond.log and the Reconciliation Engine job log files to determine the operation that the Reconciliation Engine was performing when the insufficient memory error was generated.
   For more information about Reconciliation Engine logs, see Analyzing-Reconciliation-job-logs.
5. Make sure that the server has enough resources, such as virtual memory and space for BMC CMDB tasks.
   Due to intensive data manipulation, the Reconciliation Engine might need to use more virtual memory than available.
6. If the reconciliation job uses the Copy activity, make sure that Copy Relationship field is set to By Qualifier to avoid insufficient memory issues.

Related topics

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

Analyzing-Reconciliation-job-logs