Rule entry under cmdb_ci_hardware identifier using non-existent table is ignored during identificati
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2024 11:42 AM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-02-2025 08:47 AM
Thanks, @sergiu_panaite!
For anyone else curious, we're running Yokohama Patch 1 and this workaround solution appears to have worked.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Will it still work if I deactivated the record instead of deleting it? Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-27-2025 09:25 AM
Has anyone found a solution for this? Did the workaround posted by Sergiu work for anyone else?
We just upgraded our dev environment to Yokohama Patch 1 and are seeing this intermittently when viewing incidents, changes, problems, etc. Haven't been able to find a cause for this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2025 03:26 AM
Hello Brian
I'm facing similar issue for change ..did you get any root cause for this ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2025 08:37 AM
Hi,
The workaround posted by Sergiu seems to have worked. It was intermittently showing up. Since I removed the file listed, we haven't had the error appear again.
Hope this helps.
Thanks!
