Conflicting configuration objects prevent installation

The import of a Compliance Content component template fails if the BMC Server Automation system already has a conflicting configuration object — a configuration file with the same name and path or an extended object with the same name and operating system — as that of any Compliance Content configuration object included in the import.

Similarly, if an existing property has the same name as a Compliance Content property but its other attributes (such as type, or default value) are not identical, the template cannot be imported.

To resolve this issue, perform the following steps:

  1. Check the installation log file for details regarding the conflicting configuration object or property.
  2. Do one of the following:
    • In the case of a conflicting property, modify the attributes of the existing property through the Property Dictionary to match those of the Compliance Content property.
      For more details about Compliance Content properties, see Configuring properties for Compliance Content templates.
    • For a conflicting configuration object, locate the conflicting configuration file or extended object through the Configuration Object Dictionary or through the Local Configuration Objects settings of an existing component template. Create a duplicate of the configuration object under a different a name and then delete the original, conflicting configuration object.
Was this page helpful? Yes No Submitting... Thank you