×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')

   

This documentation supports the 20.02 version of BMC CMDB.

To view an earlier version, select the version from the Product version menu.
BMC CMDB 20.02 ... Troubleshooting Error messages

Reconciliation Engine error messages

The following table lists the error number, message type, message text, description, and solution for each Reconciliation Engine error.

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...

Reconciliation Engine error messages

Error number

Message type

Error mesasgeExplanation

User response

101000

Error

Cannot create a new thread of execution.An error in the operating system might have occurred.

Contact your CMDB administrator.

101008

Error

The job is already running.You are trying to start a job that is already running.

Wait until the current job run is completed and then restart the job.

101010

Error

Cannot find job definition with this name.The job definition name that you specified does not exist.

To resolve this issue:

  1. Make sure that the job definition name is correct.
  2. Stop the Reconciliation Engine (arrecond.exe ) process and start it again.
  3. If you still encounter this error after performing step 1 and 2 above, enable Remedy Action Request System API logging to verify any Remedy AR System issues.

    Note: If you do not see any problems in the API log, you might need to restart the Remedy AR System server.

101011

Error

Cannot find job definition with this ID.The job definition ID that you specified does not exist.

To resolve this issue:

  1. Make sure that the job definition ID is correct.
  2. Stop the Reconciliation Engine (arrecond.exe ) process and start it again.
  3. If you still encounter this error after performing step 1 and 2 above, enable Remedy AR System API logging to verify any Remedy AR System issues.

    Note: If you do not see any problems in the API log, you might need to restart the Remedy AR System server.

101012

Error

The job is not active.The job that you are trying to run is not available.

Set the Change Pending job status to Active before you run it again.

101013

Error

Activity run failed because in the object store cache class does not exist.The activity that you attempted to run failed because the cache data for the Reconciliation Engine job definition does not exist.

To resolve this issue:

  1. Make sure that the job definition is correct.
  2. Stop the Reconciliation Engine (arrecond.exe ) process and start it again.
  3. If you still encounter this error after performing step 1 and 2 above, enable Remedy AR System API logging to verify any Remedy AR System issues.

    Note: If you do not see any problems in the API log, you might need to restart the Remedy AR System server.

101014

Error

Error in loading datasets.

An error occurred in the Reconciliation Engine cache data for job definitions or with BMC CMDB class metadata.

To resolve this issue:

  1. Make sure that the job definition is correct.
  2. Stop the Reconciliation Engine (arrecond.exe ) process and start it again.
  3. If you still encounter this error after performing step 1 and 2 above, enable Remedy AR System API logging to verify any Remedy AR System issues.

    Note: If you do not see any problems in the API log, you might need to restart the Remedy Action Request System server.

101015

Error

Error in creating dataset entry.

An error occurred in the Reconciliation Engine cache data for job definitions or with BMC CMDB class metadata.

To resolve this issue:

  1. Make sure that the job definition is correct.
  2. Stop the Reconciliation Engine (arrecond.exe ) process and start it again.
  3. If you still encounter this error after performing step 1 and 2 above, enable Remedy AR System API logging to verify any Remedy AR System issues.

    Note: If you do not see any problems in the API log, you might need to restart the Remedy AR System server.

101016

Error

Rename failed, dataset name <{1}> already exists.You are trying to rename a dataset with a name that already exists for a different dataset.

Specify a unique name for the dataset.

101017

Error

Rename failed, dataset <{1}> does not exist.The dataset that you are trying to rename does not exist.

To resolve this issue:

  1. Make sure that the job definition is correct.
  2. Stop the Reconciliation Engine (arrecond.exe ) process and start it again.
  3. If you still encounter this error after performing step 1 and 2 above, enable Remedy AR System API logging to verify any Remedy AR System issues.

    Note: If you do not see any problems in the API log, you might need to restart the Remedy AR System server.

101018

Error

Error in loading job definitions.

An error occurred in the Reconciliation Engine cache data for job definitions or with BMC CMDB class metadata.

To resolve this issue:

  1. Make sure that the job definition is correct.
  2. Stop the Reconciliation Engine (arrecond.exe ) process and start it again.
  3. If you still encounter this error after performing step 1 and 2 above, enable Remedy AR System API logging to verify any Remedy AR System issues.

    Note: If you do not see any problems in the API log, you might need to restart the Remedy AR System server.

101019

Error

Loading of configuration definition failed as there is no previous steps.

An error occurred in the Reconciliation Engine cache data for job definitions or with BMC CMDB class metadata.

To resolve this issue:

  1. Make sure that the job definition is correct.
  2. Stop the Reconciliation Engine (arrecond.exe ) process and start it again.
  3. If you still encounter this error after performing step 1 and 2 above, enable Remedy AR System API logging to verify any Remedy AR System issues.

    Note: If you do not see any problems in the API log, you might need to restart the Remedy AR System server.

101020

Error

Error in loading activity definitions.

An error occurred in the Reconciliation Engine cache data for job definitions or with BMC CMDB class metadata.

To resolve this issue:

  1. Make sure that the job definition is correct.
  2. Stop the Reconciliation Engine (arrecond.exe ) process and start it again.
  3. If you still encounter this error after performing step 1 and 2 above, enable Remedy AR System API logging to verify any Remedy AR System issues.

    Note: If you do not see any problems in the API log, you might need to restart the Remedy AR System server.

101021

Error

Error in loading job schedules.

An error occurred in the Reconciliation Engine cache data for job definitions or with BMC CMDB class metadata.

To resolve this issue:

  1. Make sure that the job definition is correct.
  2. Stop the Reconciliation Engine (arrecond.exe ) process and start it again.
  3. If you still encounter this error after performing step 1 and 2 above, enable Remedy AR System API logging to verify any Remedy AR System issues.

    Note: If you do not see any problems in the API log, you might need to restart the Remedy AR System server.

101022

Error

Error in loading activity qualifications

An error occurred in the Reconciliation Engine cache data for job definitions or with BMC CMDB class metadata.

To resolve this issue:

  1. Make sure that the job definition is correct.
  2. Stop the Reconciliation Engine (arrecond.exe ) process and start it again.
  3. If you still encounter this error after performing step 1 and 2 above, enable Remedy AR System API logging to verify any Remedy AR System issues.

    Note: If you do not see any problems in the API log, you might need to restart the Remedy AR System server.

101023

Error

Error in loading group definitions.

An error occurred in the Reconciliation Engine cache data for job definitions or with BMC CMDB class metadata.

To resolve this issue:

  1. Make sure that the job definition is correct.
  2. Stop the Reconciliation Engine (arrecond.exe ) process and start it again.
  3. If you still encounter this error after performing step 1 and 2 above, enable Remedy AR System API logging to verify any Remedy AR System issues.

    Note: If you do not see any problems in the API log, you might need to restart the Remedy AR System server.

101024

Error

Error in loading attribute precedences

An error occurred in the Reconciliation Engine cache data for job definitions or with BMC CMDB class metadata.

To resolve this issue:

  1. Make sure that the job definition is correct.
  2. Stop the Reconciliation Engine (arrecond.exe ) process and start it again.
  3. If you still encounter this error after performing step 1 and 2 above, enable Remedy AR System API logging to verify any Remedy AR System issues.

    Note: If you do not see any problems in the API log, you might need to restart the Remedy AR System server.

101025

Error

Error in loading activity to group associations

An error occurred in the Reconciliation Engine cache data for job definitions or with BMC CMDB class metadata.

To resolve this issue:

  1. Make sure that the job definition is correct.
  2. Stop the Reconciliation Engine (arrecond.exe ) process and start it again.
  3. If you still encounter this error after performing step 1 and 2 above, enable Remedy AR System API logging to verify any Remedy AR System issues.

    Note: If you do not see any problems in the API log, you might need to restart the Remedy AR System server.

101026

Error

Error in loading identification rules.

An error occurred in the Reconciliation Engine cache data for job definitions or with BMC CMDB class metadata.

To resolve this issue:

  1. Make sure that the job definition is correct.
  2. Stop the Reconciliation Engine (arrecond.exe ) process and start it again.
  3. If you still encounter this error after performing step 1 and 2 above, enable Remedy AR System API logging to verify any Remedy AR System issues.

    Note: If you do not see any problems in the API log, you might need to restart the Remedy AR System server.

101027

Error

Error in loading comparison rules.

An error occurred in the Reconciliation Engine cache data for job definitions or with BMC CMDB class metadata.

To resolve this issue:

  1. Make sure that the job definition is correct.
  2. Stop the Reconciliation Engine (arrecond.exe ) process and start it again.
  3. If you still encounter this error after performing step 1 and 2 above, enable Remedy AR System API logging to verify any Remedy AR System issues.

    Note: If you do not see any problems in the API log, you might need to restart the Remedy AR System server.

101028

Error

Activity run failed because there are no datasets.

An error occurred in the Reconciliation Engine cache data for job definitions or with BMC CMDB class metadata.

To resolve this issue:

  1. Make sure that the job definition is correct.
  2. Stop the Reconciliation Engine (arrecond.exe ) process and start it again.
  3. If you still encounter this error after performing step 1 and 2 above, enable Remedy AR System API logging to verify any Remedy AR System issues.

    Note: If you do not see any problems in the API log, you might need to restart the Remedy AR System server.

101029

Error

Activity run failed because there is no object store class cache.

An error occurred in the Reconciliation Engine cache data for job definitions or with BMC CMDB class metadata.

To resolve this issue:

  1. Make sure that the job definition is correct.
  2. Stop the Reconciliation Engine (arrecond.exe ) process and start it again.
  3. If you still encounter this error after performing step 1 and 2 above, enable Remedy AR System API logging to verify any Remedy AR System issues.

    Note: If you do not see any problems in the API log, you might need to restart the Remedy AR System server.

101032

Error

 Error in loading unique datasets from the association Table. You specified incorrect job definitions for the Reconciliation Engine job.

Specify appropriate job definitions in the identification rule.

101033

Error

 Class id of one endpoint is NULL for relationship class. The class ID attribute for one of the endpoints in the relationship class contains a NULL value.

This error occurs because of incorrect data. Specify a value for the class ID attribute.

101034

Error

Reconciliation identity of one endpoint is NULL for relationship class. The reconciliation ID attribute for one of the endpoints in the relationship class contains a NULL value.

This error occurs because of incorrect data. Specify a value for the class ID attribute.

101036

Error

Activity run because dataset id not found for target dataset name.

An error occurred in the Reconciliation Engine cache data for job definitions or with BMC CMDB class metadata.

To resolve this issue:

  1. Make sure that the job definition is correct.
  2. Stop the Reconciliation Engine (arrecond.exe ) process and start it again.
  3. If you still encounter this error after performing step 1 and 2 above, enable Remedy AR System API logging to verify any Remedy AR System issues.

    Note: If you do not see any problems in the API log, you might need to restart the Remedy AR System server.

101037

Error

Attribute name <{1}> not found in class <{2}> of namespace <{3}>.

An error occurred in the Reconciliation Engine cache data for job definitions or with BMC CMDB class metadata.

To resolve this issue:

  1. Make sure that the job definition is correct.
  2. Stop the Reconciliation Engine (arrecond.exe ) process and start it again.
  3. If you still encounter this error after performing step 1 and 2 above, enable Remedy AR System API logging to verify any Remedy AR System issues.

    Note: If you do not see any problems in the API log, you might need to restart the Remedy AR System server.

101038

Error

Attribute id <{1}> not found in class <{2}> of namespace <{3}>.

An error occurred in the Reconciliation Engine cache data for job definitions or with BMC CMDB class metadata.

To resolve this issue:

  1. Make sure that the job definition is correct.
  2. Stop the Reconciliation Engine (arrecond.exe ) process and start it again.
  3. If you still encounter this error after performing step 1 and 2 above, enable Remedy AR System API logging to verify any Remedy AR System issues.

    Note: If you do not see any problems in the API log, you might need to restart the Remedy AR System server.

101039

Error

Attribute of AR field id <{1}> not found in class <{2}> of namespace <{3}>.

An error occurred in the Reconciliation Engine cache data for job definitions or with BMC CMDB class metadata.

To resolve this issue:

  1. Make sure that the job definition is correct.
  2. Stop the Reconciliation Engine (arrecond.exe ) process and start it again.
  3. If you still encounter this error after performing step 1 and 2 above, enable Remedy AR System API logging to verify any Remedy AR System issues.

    Note: If you do not see any problems in the API log, you might need to restart the Remedy AR System server.

101040

Error

Class name <{1}> of namespace <{2}> does not exist. Within the specified dataset, the class name does not exist.

To resolve this issue:

  1. Make sure that the job definition is correct.
  2. Stop the Reconciliation Engine (arrecond.exe ) process and start it again.
  3. If you still encounter this error after performing step 1 and 2 above, enable Remedy AR System API logging to verify any Remedy AR System issues.

    Note: If you do not see any problems in the API log, you might need to restart the Remedy AR System server.

101041

Error

Class id <{1}> of namespace <{2}> does not exist. Within the specified dataset, the class ID does not exist.

To resolve this issue:

  1. Make sure that the job definition is correct.
  2. Stop the Reconciliation Engine (arrecond.exe ) process and start it again.
  3. If you still encounter this error after performing step 1 and 2 above, enable Remedy AR System API logging to verify any Remedy AR System issues.

    Note: If you do not see any problems in the API log, you might need to restart the Remedy AR System server.

101042

Error

Relationship <{1}> of namespace <{2}> has no lead class. Within the specified dataset, the relationship does not exist.

To resolve this issue:

  1. Make sure that the job definition is correct.
  2. Stop the Reconciliation Engine (arrecond.exe ) process and start it again.
  3. If you still encounter this error after performing step 1 and 2 above, enable Remedy AR System API logging to verify any Remedy AR System issues.

    Note: If you do not see any problems in the API log, you might need to restart the Remedy AR System server.

101043

Error

Error in opening log file. The Reconciliation Engine cannot access the log file.

Confirm that you have sufficient disk space on your system and that you have the appropriate permissions to write to the file system.

101044

Error

In merge activity <{1}>, dataset merge precedence set value is empty. Error in opening log file.

An error occurred in the Reconciliation Engine cache data for job definitions or with BMC CMDB class metadata.

To resolve this issue:

  1. Make sure that the job definition is correct.
  2. Stop the Reconciliation Engine (arrecond.exe ) process and start it again.
  3. If you still encounter this error after performing step 1 and 2 above, enable Remedy AR System API logging to verify any Remedy AR System issues.

    Note: If you do not see any problems in the API log, you might need to restart the Remedy AR System server.

101045

Error

Dataset merge precedence set <{1}> has no entry.

An error occurred in the Reconciliation Engine cache data for job definitions or with BMC CMDB class metadata.

To resolve this issue:

  1. Make sure that the job definition is correct.
  2. Stop the Reconciliation Engine (arrecond.exe ) process and start it again.
  3. If you still encounter this error after performing step 1 and 2 above, enable Remedy AR System API logging to verify any Remedy AR System issues.

    Note: If you do not see any problems in the API log, you might need to restart the Remedy AR System server.

101046

Error

 In merge activity <{1}>, there is no source dataset specified.

An error occurred in the Reconciliation Engine cache data for job definitions or with BMC CMDB class metadata.

To resolve this issue:

  1. Make sure that the job definition is correct.
  2. Stop the Reconciliation Engine (arrecond.exe ) process and start it again.
  3. If you still encounter this error after performing step 1 and 2 above, enable Remedy AR System API logging to verify any Remedy AR System issues.

    Note: If you do not see any problems in the API log, you might need to restart the Remedy AR System server.

101047

Error

Error in loading dataset merge precedence sets.

An error occurred in the Reconciliation Engine cache data for job definitions or with BMC CMDB class metadata.

To resolve this issue:

  1. Make sure that the job definition is correct.
  2. Stop the Reconciliation Engine (arrecond.exe ) process and start it again.
  3. If you still encounter this error after performing step 1 and 2 above, enable Remedy AR System API logging to verify any Remedy AR System issues.

    Note: If you do not see any problems in the API log, you might need to restart the Remedy AR System server.

101048

Error

Memory allocation failed.

The Remedy AR System server failed to allocate the memory that you are trying to allocate.

Perform the following steps to resolve this issue:

  1. Make sure that the Remedy AR System server has allocated enough system resources to support both Remedy AR System and Reconciliation Engine operations.
  2. In Remedy Developer Studio, reduce the number of concurrent Reconciliation Engine threads.
  3. Increase the virtual memory.

No error number

Error

Found multiple matches in the dataset: Cannot identify the instance of class <className> with instance ID <instanceId> . More than one instance of the specified class was found in the dataset.

See Reconciliation Engine multiple CI match issues.

ARERR 120092

Error

ARERR [120092] The dataset ID and Reconciliation Identity combination is not unique. You are trying to merge a CI that has more than one instance with the same dataset ID and Reconciliation ID combination.

See Troubleshooting reconciliation based on error messages.

No error number

Error

Cannot find the endpoint of relationship::<className>:Merging of record failed. You are trying to merge an orphan instance.

See Troubleshooting reconciliation based on error messages.

No error number

Error

Algorithm: Including child CIs and committing together. The option that you specified in the Include child CIs? menu is complicated.

See Troubleshooting reconciliation based on error messages  .

No error number

Error

The Reconciliation Engine log only shows two unique TIDs (Thread IDs). The number of activities that you are trying to run require more than the total number of threads that you allocated.

See Improving performance of reconciliation.

No error number

Error

The Reconciliation Engine demonstrates performance issues due to incorrect database settings. You encounter Reconciliation Engine performance issues, such as the job takes a long time to complete or the Reconciliation Engine freezes.

See Improving performance of reconciliation.

Was this page helpful? Yes No Submitting... Thank you
Last modified by IDD Robot on Apr 23, 2024
reconciliation_engine error_messages

Comments

Log in or register to comment.

BMC CMDB C API error messages
BMC CMDB Console filter error messages
© Copyright 2005-2007, 2009-2021 BMC Software, Inc. © Copyright 2011-2021 BladeLogic, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.