Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Discovery via pattern fails with "Identification CI errors: Abandoned due to too many errors" - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Discovery via pattern fails with "Identification CI errors: Abandoned due to too many errors"
KB0715696

Discovery via pattern fails with "Identification CI errors: Abandoned due to too many errors"


5763 Views Last updated : Jul 19, 2023 public Copy Permalink
KB Summary by Now Assist

Issue

The Discovery process may fail with an error on the pattern logs where you can see: 

"Identification CI Errors: Abandoned due to too many errors".

Cause

This is possibly caused by duplicates on the relationship type table [cmdb_rel_type].

Resolution

1 - Enable the Debug for the CI Identification parameter on the Discovery properties ( glide.discovery.debug.ci_identification ).

2 - Quick discovery the affected device.

3 - Check the logs on the syslog_list.do, the CI Identification ones would be like: 

identification_engine : DUPLICATE_RELATIONSHIP_TYPES Duplicate relationship type records exists with name [Master of::Stack Member of] 

4 - Figure out which relationship type has got duplicates. Go to cmdb_rel_type_list.do and filter by name, there should be only one record for the same type.

5 - Check on the cmdb_rel_ci_list.do if there is any relationship using that particular type, in which case a deletion would break the link.

6 - Delete the record that is not being used.


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.