Failed to acquire exclusive access to remote registry Monitor

  • ID:  Microsoft.SystemCenter.AgentManager.RegistryLockFailed.Monitor
  • Description:  Monitor for when the management server failed to acquire the appropriate exclusive access to the remote registry on the target computer.
  • Target:  Agent Manager
  • Enabled:  Yes

Operational States

Name State Description
Failed Error  
Success Success  

Alert Details

Monitor State Message Priority Severity Auto Resolution
Failed (Error) Failed Agent Push/Repair - Could not acquire exclusive access to remote registry Medium Critical Yes

Run As Profiles

Name
Default

Monitor Knowledgebase

Summary

The Management Server was unable to obtain an exclusive lock on the Registry.

Causes

This can happen when another Management Server is also attempting to install the agent or when anti-virus or other spyware detection software has locked the registry for its scan or quarantine feature.

Resolutions

Ensure that only one Management Server is attempting to remotely install the agent. If you are sure that there is only one server that is pushing an agent, temporarily add an exclusion to your anti-virus software or spyware software to exclude the MOMAgentInstaller.exe process during the installation.

For more information on troubleshooting agent installation, see Troubleshooting Issues When You Use the Discovery Wizard to Install an Agent(http://go.microsoft.com/fwlink/?LinkId=181932).

External References
This monitor does not contain any external references.

See Also for System Center 2016 Operations Manager inbox MP hotfix for WMI health monitor issue Management Pack


Downloads for System Center 2016 Operations Manager inbox MP hotfix for WMI health monitor issue Management Pack

AZURE OPTIMIZATION ASSESSMENT GET STARTED
MIGRATION TO AZURE GET STARTED
SYSTEM CENTER MIGRATION TO AZURE GET STARTED
MIGRATION TO AZURE FOR SQL AND WINDOWS 2008 GET STARTED