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.
If you intend to keep replicating:
- While in the source Core, stop the Core service
- Open Registry Editor in Windows
- Navigate to HKLM\SOFTWARE\AppRecovery\Core\Replication\RemoteCores\Slaves
- Make a backup (export) of the Slaves key to revert changes if needed
- Delete the Core ID(s) found underneath this key
- Start the Core service
- Log into the target Core, stop the Core service
- Open the Windows Registry Editor
- Navigate to HKLM\SOFTWARE\AppRecovery\Core\Replication\RemoteCores\Masters
- Make a backup (export) of the Masters key to revert changes if needed
- Delete the Core ID(s) found underneath this key
- Start the Core service
- Return to your source Core and recreate replication task(s)
- Test replication; if it works fine, your rollup jobs will now be successful
If you're no longer going to replicate:
- Stop the Core service
- Open Registry Editor in Windows
- Navigate to HKLM\SOFTWARE\AppRecovery\Core\Replication\RemoteCores
- Verify if there are any Core ID entries under either Masters or Slaves keys
- Delete the keys found under either key mentioned above
- Start the Core service
- Check under each agent in HKLM\SOFTWARE\AppRecovery\Core\Agents\{agent ID} if there is any key inside called ReplicationService
- If the key is present, delete it from under each agent where it can be found. Restart the Core to enact the changes.