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.
Unable to request clone due to error message "Destination returned error status = 500" - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Unable to request clone due to error message "Destination returned error status = 500"
KB0681148

Unable to request clone due to error message "Destination returned error status = 500"


6187 Views Last updated : Apr 9, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

Unable to request a new clone even if the correct username and password are provided. 

After providing username and password, the error message "Destination returned error status = 500" is observed.

Frame to create a new record in ServiceNow Instance with the Destination returned error, status = 500 error at the top of the frame

Cause

This issue can be caused by more than one issue:

  • The user requesting the clone does not have the admin or clone_admin roles.
  • The user on the target instance who is used for authentication does not have the admin role.
  • The system property glide.soap.require_ws_security is set to true.

Resolution

  • Make sure that the user who requests the clone on the source instance has the admin or clone_admin role, and that the user on the target instance who is used for authentication has the admin role. See Create a clone target for more information about configuring target instances.
  • If the system property glide.soap.require_ws_security is set to true you will need to enable the 'Internal Integration User' flag for the clone user as per Mark service accounts as internal integration users

"When WS-Security is enabled, authentication is required for all SOAP requests including internal integration communications such as the MID Server, ODBC Driver, Remote Update Sets, and high availability cloning. SOAP requests for these internal integration communications cannot implement WS-Security due to technical implications. If your instance uses these SOAP interfaces, you can allow them to bypass the WS-Security authentication requirement by marking their user accounts as internal integration users."


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.