Rule entry under cmdb_ci_hardware identifier using non-existent table is ignored during identificati

edharris
Tera Contributor

Getting this error and I am not familiar on how to fix it. I went to the cmdb_entry_related table and the sys_object_source tables and could not find a record with the sys_id 73b8c48e8d707110f8778302d753bcd2 to delete. Open to any suggestions or if anyone has any workarounds. Thank you 

11 REPLIES 11

ankita-jagannat
Tera Contributor

I am also facing the same error . Did you get any fix for this ? Please let me know .

Shree123
Tera Contributor

Were you able to resolve this? I am facing the same issue. Don't see any record with the mentioned sys_id.

sergiu_panaite
ServiceNow Employee
ServiceNow Employee

We do have an internal PRB opened for this and the workaround would be to delete the following record:

 

cmdb_related_entry_list.do?sysparm_query=identifier%3Da1d19344c3b33100d8d4bea192d3aedc%5Etable%3Dcmdb_file_information&sysparm_view=

 

Before doing that, check in your instance that table cmdb_file_information does not exist:

 

sys_db_object_list.do?sysparm_query=nameSTARTSWITHcmdb_file_information&sysparm_view=

 

The issue is caused by the fact that table `cmdb_file_information` does not exist therefore deleting that record would prevent the error.

 

 

 

ankitajagannat_0-1732283295892.png

 

No record here .