CMDB or Discovery Error: "Rule entry under cmdb_ci_unclassed_hardware identifier using non-existent table is ignored during identification"<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Issue During Discovery or CMDB identification, the following error is logged: Rule entry under cmdb_ci_unclassed_hardware identifier using non-existent table is ignored during identification! This prevents proper identification and reconciliation of Configuration Items (CIs) classified as Unclassed Hardware. Symptoms The error message appears in Discovery logs or CMDB identification logs.Unclassed Hardware CIs may fail to be properly identified or reconciled.Duplicate CIs may be created in the cmdb_ci_unclassed_hardware table. Facts Affected Table: Unclassed Hardware [cmdb_ci_unclassed_hardware]The Unclassed Hardware CI class does not have its own CI Identifier by default.Out of the box, Unclassed Hardware inherits and uses the Hardware Rule CI Identifier for identification and reconciliation. Cause A custom CI Identifier was created for the Unclassed Hardware [cmdb_ci_unclassed_hardware] table and was configured with custom fields as Identifier Entries. These custom Identifier Entries reference fields or tables that do not exist or are not valid for the identification process, resulting in the error. Solution Navigate to CMDB Identifiers by going to Configuration > Identification/Reconciliation > CI Identifiers.Search for any CI Identifier associated with the cmdb_ci_unclassed_hardware table.Review the Identifier Entries configured on the custom CI Identifier and confirm whether the referenced fields and tables are valid.Take one of the following corrective actions: Remove the custom CI Identifier to allow Unclassed Hardware to revert to the inherited out-of-box Hardware Rule identifier.Correct the Identifier Entries on the custom CI Identifier to reference valid, existing fields and tables if a custom identifier is required. After making changes, re-run Discovery or identification to confirm the error no longer occurs and CIs are properly reconciled. Note: The out-of-box Hardware Rule identifier is the expected and supported configuration for the Unclassed Hardware CI class. Creating custom identifiers for this class should only be done when there is a clear business requirement, and all Identifier Entries must reference valid tables and fields. If assistance is needed, consider engaging ServiceNow Professional Services or ServiceNow Technical Support.