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.
Clone fails for duplicate records found in the target instance on saml2_update1_properties - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • Clone fails for duplicate records found in the target instance on saml2_update1_properties
KB0714135

Clone fails for duplicate records found in the target instance on saml2_update1_properties


1253 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Description

System clones fail during the pre-flight checks with the error:

'areThereIDPDuplicatesInTargetInstance' activity: IDP column in source table saml2_update1_properties is unique and the IDP: [name of IDP record] has duplicate records in the target instance

No errors or failures are given to indicate data preserver import errors when a column is not unique in the target instance and has duplicate values. One common example of this is the IDP (Identity Provider URL) column on the saml2_update1_properties table.

Steps to Reproduce

 

  1. Set the Unique flag of the IDP (Identity Provider URL) column in saml2_update1_properties to false
  2. Create records on the sso_properties table with duplicate values in the IDP field
  3. Clone over this instance from another instance
  4. One of the duplicate records will become corrupt

Workaround

This behaviour is by design in the current releases. In order to prevent blocking issues after cloning when duplicate values exist, the clone engine will stop execution when duplicate values are detected. Technical Support will then be tasked to intervene via an automatically-generated incident.

The solution is to remove or update the records so that there are no longer duplicate values. For example, in the case of the IDP (Identity Provider URL) column on saml2_update1_properties table, the duplicate IDP (Identity Provider URL) value must be changed to another unique value, or the duplicate record must be removed completely:

1. Go to the clone target.

2. Open the table [saml2_update1_properties].

3. Group the 'Identity Provider URL' column and identify duplicate records.

4. Either delete those duplicate record(s) or update the value to make them not unique.

5. Re-submit the clone.


Related Problem: PRB1183030

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.