KMF startup errors after changing instance_id on target cloned on-premises instanceIssue After cloning an on-premises (self-hosted) instance, the source and target instances may have the same instance_id value in the System Properties [sys_properties] table. The target instance’s property must be updated to a unique value to distinguish it from the source instance. ServiceNow Support However, changing this property without updating the associated Key Management Framework (KMF) metadata may cause KMF initialization errors and prevent the instance from starting. The instanceID needs to be changed to a unique value because both test and production servers currently have the same instanceID shown in the instance system properties. Symptoms The following error may appear in the startup logs: Only found KMF instance keys belonging to other instances in the database --system may not start Release N/A Cause The cloned KMF instance-key metadata remains associated with the original instance identifier. Changing the instance_id system property does not automatically update that association. When the new instance identifier does not match the identifier stored in the KMF metadata, KMF may identify the existing instance keys as belonging to another instance. This mismatch can interfere with KMF initialization during startup. Update the source_instance_id field in the KMF instance-key metadata to match the unique value assigned to the target instance’s instance_id system property. Important: This procedure involves direct database changes. Have a qualified database administrator review and perform the update, and ensure that a recoverable database backup is available. Keep the affected instance stopped while updating the KMF metadata. Resolution Confirm the target instance identifier.Verify that the target instance’s instance_id property in sys_properties contains the intended unique value. Record this value for use in the database update.Stop the affected instance.Ensure that all application nodes belonging to the target instance are stopped before proceeding.Update the KMF metadata in the target database.Connect to the database associated with the affected target instance. Replace <new_instance_id> in the following statement with the exact value of that instance’s instance_id property, retaining the surrounding single quotation marks. -- Update the source_instance_id field for all matching -- instance-key metadata records to the specified instance ID. UPDATE sys_kmf_key_metadata M INNER JOIN sys_kmf_instance_key I ON M.sys_id = I.sys_id SET M.source_instance_id = '<new_instance_id>'; Restart and validate the instance. Related Links KB0551693 - Manage On-Premise Instance - Now Support Service CatalogKB1122086 - Update Instance ID for Clone of instanceKB2034392 - Guidance: KMF - On-Premises Instance Cloning in Air Gap Environments