Red alerts in HAM Rule entry under cmdb_ci_* ident. using non-existent table is ignored during ident

[DamandeepS]

Hi Community,

When I open Hardware Asset records or the Hardware list view, I keep getting red alerts like these:

Rule entry under cmdb_ci_power_eq identifier using non-existent table is ignored during identification! Rule entry under cmdb_ci_appl identifier using non-existent table is ignored during identification! Rule entry under cmdb_ci_network_function_instance identifier using non-existent table is ignored during identification!

• I checked Identification Rules and Identification Inclusion Rules but couldn’t find any related entries.

• cmdb_identification_rule.list does not open in my instance.

• It looks like these classes don’t exist in my environment, so the rules are orphaned.

Questions:

1. How can I safely remove or deactivate these invalid rules?

2. Is there another way to clean up orphaned CMDB classes/rules without installing the full Identification & Reconciliation Engine (IRE) plugin?

3. Has anyone handled this before in a Hardware Asset–only implementation (without Discovery)?

Any guidance would be appreciated. Thanks!

[Ken29]

We had this issue after upgrading the Discovery and Service Mapping Patterns plugin to version 1.28.0. Running cache.do seems to have resolved the issue in our instance.

It looks like the error messages are being posted by Script Include IdentificationRuleValidator which is called by one of the Rule validation on Identifier*  Business Rules. I stopped looking into it after cache.do cleared up the problem, though.

Good luck,

Ken

[Trevor Muhl]

Hello. I was experiencing the same errors. I found the following article on the topic -- KB1573799. The workaround provided there is as follows:

To fix in any instance that already has the problem, please delete records in cmdb_related_entry table where related table = tni_entity:

https://instance_name.service-now.com/cmdb_related_entry_list.do?sysparm_query=table%3Dtni_entity&sy...

Subsequent installation of higher version (1.53 and above) of CMDB CI Class Models where the defect is fixed will not remove the above records and will not resolve the issue.  The records needs to be manually deleted.

---

I have not seen the errors again since doing this. Hopefully this helps you!

[Zack Hilacan1]

Hello @DamandeepS ,

The ITOM Content Service might be outdated.

Go to the Plugins and look for the ITOM content Service[sn_smart_content], check the version if it is lower than 1.5.1 then update it to 1.5.1 or preferably to its latest version.

Regards,

Zack

Hopefully this helps 🙂