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.
MID Server Credentials Overwritten by Clone - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • MID Server Credentials Overwritten by Clone
KB0695150

MID Server Credentials Overwritten by Clone


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

Issue

Symptoms


After a clone is completed, MID server credentials are no longer working on the target instance.

Release


All Supported Releases

Cause


This is usually caused by preserving the sys_user table without excluding it as well. For MID server authentication, a local sys_user record with the 'mid_server' role is used. When you configure a data preserver, it will apply the preserved data on top of the cloned data. Without also excluding the data also, the MID server user will be cloned down from prod, and then the preserved MID server user will be applied right on top of it. Since there is a unique index on the user_name field on the sys_user_table, this insert will be blocked.

Resolution


It is not recommended to preserve or exclude the sys_user table for any reason. If some users must be preserved between instances, it is recommended to export them to XML. The user_name value must also be unique, since you cannot have more than one sys_user record with the same user_name value.

Additional Information


Data Preservation


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.