After cloning, connection to the remote instance is no longer possible

[miyu]

I have created clones of the production instance on the development and verification instances respectively.
I then Upgraded the development and verification instances respectively.
I am trying to migrate the post-Upgrade actions done on the development instance to the verification instance.
However, the connection of the remote instance (development instance) that was set up in the verification instance does not work.
The connection fails even though I have set the appropriate user.
What is the problem? Do I need to configure system properties, etc.?

[Filipe Cruz]

Hello miyu,

Can you check this system property in your verification instance:

glide.db.clone.allow_clone_target

Allow this instance to be used as a clone target. Set to false to prevent this instance from being cloned to. Used to provide an additional safeguard which prevents a production instance from being cloned over. Default value is false for production instances and true for sub-prod instances (dev, qa, etc).

Please let me know if this solves your issue.

Please, don't forget to mark my answer as correct if it solves your issue or mark it as helpful if it is relevant for you!

Best Regards,

Filipe Cruz

[Hitoshi Ozawa]

Hi Miyu,

When cloning, was sys_user_has_role ,sys_user_role and sys_user_group tables excluded along with sys_user table?

Check the following Now Support page.

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

[miyu · Accepted solution]

This was due to a bug caused by Upgrae from Quebec to San Diego.
This was resolved by installing the Key Management Framework plugin.
Thank you all very much.