The LMU does not list the agents under the Core name when run from either the Core server or another machine. Furthermore, you receive the following error when you attempt to right click the Core name and select “Reconnect to Core.”
“Retrieving protected Agents: Could not connect to core.”
This error is the result of an improperly configured repository on the affected agent, which in turn causes AppAssure to repeatedly find a reference to an object that does not exist.
To resolve this issue, complete the following steps.
1. After a failed attempt to reconnect to the Core, open the AppRecovery.log file and search for the following error.
2. This error indicates that one of your agents does not contain a configured repository, which causes AppAssure to repeatedly search for an object that does not exist.
3. Open the registry on your Core machine and navigate to HKEY_LOCAL_MACHINE_\SOFTWARE\AppRecovery\Core\Agents
4. Stop the AppAssure core and AppAssure MongoDB services.
5. Export a copy of the HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Core\Agents recovery branch to a memorable location
6. Expand each agent GUID and expand AgentProtectionConfiguration. Search for the StorageConfiguration registry branch
7. When you find an agent that lacks the StorageConfiguration registry branch, delete that Agent’s GUID registry branch
8. Start the AppAssure Core and AppAssure MongoDB services
9. Open the LMU, right-click on the core name and select “Reconnect to Core”. Your agents should all populate in the LMU
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center