Home
  •  

DPM: Agent unreachable - Cannot map machine account

Microsoft.SystemCenter.DataProtectionManager.2011.Discovery.DPMAgentUnreachable_AMCannotMapMachineAccount (DependencyMonitor)

Knowledge Base article:

Summary

This is a consolidated infrastructure alert (logical consolidation) that represents one or more infrastructure issues that have happened on the DPM server. The infrastructure items affected may not share the same root cause. Since the failures have similar symptoms and resolution steps, they are logically consolidated under this alert. To view the items affected by this issue, click on the action View Affected Items.

Causes

See the alert details pane for more information about the cause of this alert.

Resolutions

See the alert details pane for steps to resolve this alert. After the root cause is understood, resolve the root cause for each affected item.

Additional

Additional information for this failure is available on the DPM website. To view this, select the alert in the alert view and click on the action Get more information

External

To learn more about consolidated infrastructure alerts (logical consolidation) and how you can use the DPM tools to troubleshoot and resolve issues, see Working with Consolidated Infrastructure Alerts (Logical Consolidation) (http://go.microsoft.com/fwlink/?LinkId=230559).

Element properties:

TargetMicrosoft.SystemCenter.DataProtectionManager.2011.Library.DPMServer
Parent MonitorSystem.Health.ConfigurationState
AlgorithmWorstOf
Source MonitorMicrosoft.SystemCenter.DataProtectionManager.2011.Discovery.AgentUnreachable_AMCannotMapMachineAccount
RelationshipMicrosoft.SystemCenter.DataProtectionManager.2011.Library.DPMServerHostsProductionServer
CategoryCustom
EnabledTrue
Alert GenerateTrue
Alert SeverityWarning
Alert PriorityNormal
Alert Auto ResolveTrue
RemotableTrue
AccessibilityPublic
Alert Message
DPM: Agent unreachable - Can not map machine account
DPM agents on some of the protected servers are not reachable because machine account cannot be mapped.
DPM Server: {0}

Resolution steps:
Verify that both protected server and the domain controller are responding. Then in Microsoft Management Console (MMC), open the Group Policy Object Editor snap-in for the local computer and verify the local DNS client settings in Local Computer Policy\Computer Configuration\Administrative Templates\Network\DNS Client.

Source Code:

<DependencyMonitor ID="Microsoft.SystemCenter.DataProtectionManager.2011.Discovery.DPMAgentUnreachable_AMCannotMapMachineAccount" Accessibility="Public" Enabled="true" Target="SCDPM!Microsoft.SystemCenter.DataProtectionManager.2011.Library.DPMServer" ParentMonitorID="Health!System.Health.ConfigurationState" Remotable="true" Priority="Normal" RelationshipType="SCDPM!Microsoft.SystemCenter.DataProtectionManager.2011.Library.DPMServerHostsProductionServer" MemberMonitor="Microsoft.SystemCenter.DataProtectionManager.2011.Discovery.AgentUnreachable_AMCannotMapMachineAccount">

  <Category>Custom</Category>

  <AlertSettings AlertMessage="Microsoft.SystemCenter.DataProtectionManager.2011.Discovery.DPMAgentUnreachable_AMCannotMapMachineAccount_AlertMessageResourceID">

    <AlertOnState>Warning</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertSeverity>Warning</AlertSeverity>

    <AlertParameters>

      <AlertParameter1>$Target/Property[Type="SCDPM!Microsoft.SystemCenter.DataProtectionManager.2011.Library.DPMServer"]/DPMServerName$</AlertParameter1>

    </AlertParameters>

  </AlertSettings>

  <Algorithm>WorstOf</Algorithm>

  <MemberUnAvailable>Error</MemberUnAvailable>

</DependencyMonitor>