Error message "AHD05541: CI creation terminated because the CI (xxxx) already exists" when the field/s CORA is checking for duplicates against has NULL values.
search cancel

Error message "AHD05541: CI creation terminated because the CI (xxxx) already exists" when the field/s CORA is checking for duplicates against has NULL values.

book

Article ID: 51456

calendar_today

Updated On:

Products

CA IT Asset Manager CA Software Asset Manager (CA SAM) ASSET PORTFOLIO MGMT- SERVER SUPPORT AUTOMATION- SERVER CA Service Desk Manager - Unified Self Service CA Service Desk Manager CA Service Management - Asset Portfolio Management CA Service Management - Service Desk Manager

Issue/Introduction

The CA Service Desk Manager performs a duplicate check of the Configuration Item(CI) using CORA. Even if the serial number is unique and the CI name is duplicated, a duplicate error message occurs as follows:

AHD05541: CI creation terminated because the CI (xxxx) already exists.

The attached PDF suggests it should handle the above CIs as unique ones. Why does the error occur?

Environment

CA Service Desk 17.1 and higher.

Resolution

As the attached PDF states, CORA is checking the following fields as part of its check for duplicate CI's.

  • Serial Number
  • Alt Asset ID
  • Host Name
  • DNS Name
  • MAC Address
  • Asset Label

However, if the CI that is being newly created or is already registered has one or more of the above fields with a value of NULL then CORA will ignore it as part of a duplicate check and only use the remaining fields to see if there is a CI with the same properties that already exist. For example, if a CI has been registered with a value of NULL for the Serial number, CORA will not check the serial number field during a duplicate check. As a result, CORA will check the following fields only and not the Serial number.

  • Alt Asset ID
  • Host Name
  • DNS Name
  • MAC Address
  • Asset Label

When you then attempt to create another asset where the serial number is not null, unique but with the remaining fields containing the same values as those of a registered CI the above error message is the result. It is considered a duplicate and the behavior is a by design not a bug.

Attachments

1616789618629__CORA_MDB_and_Assets_SC.pdf get_app