-
Title
Cannot "replicate to self" message shows when attempting to establish replication between cores. -
Description
Upon attempting to establish replication for the first time, a message shows claiming "Replication to self is not supported." Stack trace: "Replay.Core.Contracts.Replication.Exceptions.ReplicationToSelfNotSupportedException: The replication to self is not supported". -
Cause
The target replication core's ID is the same as the source replication core.
This may happen if you used the same RASR USB key from the source replication core to factory reset / rebuild the target replication core.
This may also happen if you have "cloned" a source core that happens to be virtual to be used as a new target replication core.
-
Resolution
Windows Registry Disclaimer:
Quest does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article ID 256986 “Description of the Microsoft Windows registry” at Microsoft Support.
Use the "graceful shutdown" approach to stop the core service at the target replication core you want to establish replication with.
Use regedit to find the following registry key - HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\CoreId
Export (save) the key for safe keeping, just in case.
Delete the key.
Start the core service you stopped in step 1.
Establish replication from the source replication core.