MISSING_DEPENDENCY: In payload no relations defined for dependent class
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2025 02:40 PM
Hi All, My Discovery Errors dashboard is present multiple common errors. How can we solve that pls?
MISSING_DEPENDENCY:
In payload no relations defined for dependent class [cmdb_ci_iisdirectory] that matches any containment/hosting rules: [cmdb_ci_appl >> Runs on >> cmdb_ci_hardware]
MISSING_DEPENDENCY:
In payload no relations defined for dependent class [cmdb_ci_db_mssql_database] that matches any containment/hosting rules: [cmdb_ci_appl >> Runs on >> cmdb_ci_hardware
MISSING_DEPENDENCY:
In payload no relations defined for dependent class [cmdb_ci_network_adapter] that matches any containment/hosting rules: [cmdb_ci_network_adapter >> Owned by >> cmdb_ci_hardware]
MISSING_DEPENDENCY:
In payload no relations defined for dependent class [cmdb_ci_compute_template] that matches any containment/hosting rules: [cmdb_ci_compute_template >> Hosted on >> cmdb_ci_logical_datacenter]
MISSING_DEPENDENCY:
In payload no relations defined for dependent class [cmdb_ci_disk_type] that matches any containment/hosting rules: [cmdb_ci_disk_type >> Hosted on >> cmdb_ci_logical_datacenter]
MISSING_DEPENDENCY:
In payload no relations defined for dependent class [cmdb_ci_web_application] that matches any containment/hosting rules: [cmdb_ci_appl >> Runs on >> cmdb_ci_oslv_container,cmdb_ci_appl >> Runs on >> cmdb_ci_hardware]
Thank you!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-27-2025 08:31 AM
I am getting the same error did you manage to resolve this?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-27-2025 08:58 AM
Hi - Yes. The solution is very simple.
Instance of your client
=================
1. cmdb_metadata_containment.list of instance with issues
2. Find the tables, related to the class with problem,
3 - Take a full backup in XML of your affect items (Recommended)
Your PDI
=======
4. cmdb_metadata_containment.list of fresh PDI with same ServiceNow version of your client
Instance of your client
=================
5. Export the records (via XML) related to the records of your CI Class you are having problem
6. Import them records (via XML) to cmdb_metadata_containment.list
7 - Retry Discovery from Discovery errors , it will fix all them.
If some errors still remains in the card, just wait the OOTB runs the clean-up erros , and it will clean automatically the remaining errors.
> https://XXXX.service-now.com/nav_to.do?uri=sysauto_script.do?sys_id=81c17c7467813300d88fa0119585ef6b
> <https://url.de.m.mimecastprotect.com/s/MUTBC6Wn4wIrr9mNMHmiLU56wpp?domain=csf.service-now.com>
Any other questions let me know
Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-27-2025 11:31 PM
Thanks for the response I will let you know if this does not work.