- Use a graceful shutdown approach to stop the core service. - https://support.quest.com/kb/119400
- Note that if MongoDB service continues running, it is possible that it is in an unstable state. If this is so, stop MongoDB service.
- Start the core service.
- Check the core console for previous behavior.
- If there is still an issue (same error message), stop core service again, and run the core installer choosing the "repair" option, and after this is completed, check core console for previous behavior.
- If solution 1 was not successful, stop the core service as in solution 1's first step.
IMPORTANT Warning: Proceeding with the following steps will remove agent protection configuration, this does not affect your backed up data, but you will have to re-add all agents to protection and re-configure any custom protection parameters such as protection schedules, volume exceptions from protection, etc. Please regard the Windows Registry Disclaimer.
- Run REGEDIT as administrator.
- Navigate to this key: HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\Agents
- Right-click on the key and select export to save the original information in case you want to revert actions.
- Delete the Agents key from the registry.
- Start the core service, and confirm on the core console that there is no longer an error message.
- Re-add the agents to protection. Once added, incremental snapshots for these agents will continue. Re-configure protection parameters, schedules, etc... as needed.
Windows Registry Disclaimer:
Quest Software 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.