Unable to clone

[Andrew Pickles]

Hi all, id be very glad of a little help with a strange issue.

I am trying to clone PROD over DEV .. I have done this before fine.

Now when trying to create the clone request record i get the error :

Destination returned error, status = 500

The user account IS admin on the target, And i can log into the target with those credentials.

It IS a local account (on the target)

The system property to allow clone is set to yes

No SSO, MFA or LDAP is switched on on the target

I seem to remember seeing somewhere that the target username must have some SOAP role, or similar .. But maybe i am wrong on this .

Anyway i am out of ideas and would really appreciate a nudge in the right direction.

Many thanks

[Saurav11]

Hello,

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 here 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 the documentation:

"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."

Please refer the below support article if you have not read already.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0681148

Please mark answer/correct/helpful based on Impact.

[Andrew Pickles]

Thanks for the reply - however as stated in my original question , I have tried all those things

[Andrew Pickles · Accepted solution]

The answer to this, for anyone interested, was that our admin role is an elevated role in our instances.

And the clone request wasnt able to elevate the role.

I fixed it by temporarily turning off the "elevated privillage" check box on the admin role