Home
  •  

Microsoft.SystemCenter.VirtualMachineManager.2007.Engine.HostAgentNotResponding.rule (Rule)

Knowledge Base article:

Summary

The Virtual Machine Manager agent on the virtual machine host did not respond to a communication from the VMM server. This alert is generated the first time that the host does not respond, and is not repeated.

Causes

Possible causes for a host not responding include:

1

WS-Management, also known as Windows Remote Management (WinRM), is stopped on the host.

2

The Virtual Server service is not present on the host or the service is stopped.

3

The machine account for the VMM server is not in the local Administrators group on the host computer.

4

The machine account for the VMM server is not in Virtual Machine Manager Servers group on host computer.

5

Windows Firewall is enabled on the host computer, and the following firewall exceptions have not been added:

  • Port exceptions - HTTP (80), HTTPS (443) (These are the default port assignments for HTTP and HTTPS and may differ from the ports that are in use.)

  • Program exception - VMMAgent

6

The WinRM listener is not present or is not listening on all IP addresses on the host. This can happen if WS-Management is uninstalled and then re-installed.

7

A proxy server is preventing communication with the host.

Resolutions

To troubleshoot these issues:

1

Ensure that you can connect to the host computer from the VMM server.

2

Ensure that the Virtual Machine Manager Agent service and the WS-Management service (formerly known as WinRM) are running on the host computer. If not, restart the services.

3

Ensure that Virtual Server is installed on the host computer, and that the Virtual Server service is running.

4

Ensure that the machine account for the VMM server is in the following groups on the host computer:

  • Administrators

  • Virtual Machine Manager Servers

5

If Windows Firewall is enabled on the host computer, check whether the following firewall exceptions have been added. Location: Control Panel\Windows Firewall, Exceptions tab.

  • Port exceptions - HTTP (80), HTTPS (443) (These are the default ports, and may not be the ports that you are using.)

  • Program exception - VMMAgent

6

Check whether the WinRM listener is present on the host computer. To do this, enter the following at a command prompt:

winrm enum winrm/config/listener

If WinRM is present, the command returns something like this:

Address = *

Transport = HTTP

Port = 80 (Default port used here.)

HostnameEnabled = true

URLPrefix = wsman

CertificateThumbprint

ListeningOn = 127.0.0.1, 172.30.190.61 (All IP addresses of the host)

If you updated any configurations in steps 4-6, you must uninstall and re-install the Virtual Machine Manager agent on the host.

7

Remove the Virtual Machine Manager agent locally on the host computer by using Add or Remove Programs in Control Panel.

8

Reinstall the Virtual Machine Manager agent on the host:

  • If the host is in a trusted Active Directory Domain Services (AD DS) domain, from any view in the VMM Administrator Console, click Add hosts in the Actions pane, and follow the wizard instructions to add the host to VMM.

  • If the host is on a perimeter network, install the Virtual Machine Manager agent locally on the host computer, and then add the host to VMM by using the Add hosts action. For agent installation instructions, see Installing a VMM Agent Locally (http://go.microsoft.com/fwlink/?LinkId=98830) in the Microsoft TechNet Library.

9

If the host is still not available, refresh the host in Virtual Machine Manager. To do this, in the VMM Administrator Console, display Hosts view, select the host, and then click Refresh in the Actions pane.

Additional

Windows NT Event 435, Param6=3

External

Virtual Machine Manager TechNet Library (http://go.microsoft.com/fwlink/?LinkId=99096)

Element properties:

TargetMicrosoft.SystemCenter.VirtualMachineManager.2007.Engine
CategoryAvailabilityHealth
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
RemotableTrue
Alert Message
Managed host not responding
{0}
Event LogVM Manager

Member Modules:

ID Module Type TypeId RunAs 
DS DataSource Microsoft.Windows.EventProvider Default
GenerateAlert WriteAction System.Health.GenerateAlert Default

Source Code:

<Rule ID="Microsoft.SystemCenter.VirtualMachineManager.2007.Engine.HostAgentNotResponding.rule" Enabled="true" Target="Microsoft.SystemCenter.VirtualMachineManager.2007.Engine">

  <Category>AvailabilityHealth</Category>

  <DataSources>

    <DataSource ID="DS" TypeID="Windows!Microsoft.Windows.EventProvider">

      <ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>

      <LogName>VM Manager</LogName>

      <Expression>

        <And>

          <Expression>

            <SimpleExpression>

              <ValueExpression>

                <XPathQuery>PublisherName</XPathQuery>

              </ValueExpression>

              <Operator>Equal</Operator>

              <ValueExpression>

                <Value>Virtual Machine Manager</Value>

              </ValueExpression>

            </SimpleExpression>

          </Expression>

          <Expression>

            <SimpleExpression>

              <ValueExpression>

                <XPathQuery>EventDisplayNumber</XPathQuery>

              </ValueExpression>

              <Operator>Equal</Operator>

              <ValueExpression>

                <Value>435</Value>

              </ValueExpression>

            </SimpleExpression>

          </Expression>

          <Expression>

            <SimpleExpression>

              <ValueExpression>

                <XPathQuery>Params/Param[6]</XPathQuery>

              </ValueExpression>

              <Operator>Equal</Operator>

              <ValueExpression>

                <Value>3</Value>

              </ValueExpression>

            </SimpleExpression>

          </Expression>

        </And>

      </Expression>

    </DataSource>

  </DataSources>

  <WriteActions>

    <WriteAction ID="GenerateAlert" TypeID="SystemHealth!System.Health.GenerateAlert">

      <Priority>1</Priority>

      <Severity>2</Severity>

      <AlertMessageId>$MPElement[Name="Microsoft.SystemCenter.VirtualMachineManager.2007.Engine.HostAgentNotResponding_Rule.AlertMessage"]$</AlertMessageId>

      <AlertParameters>

        <AlertParameter1>$Data/EventDescription$</AlertParameter1>

      </AlertParameters>

    </WriteAction>

  </WriteActions>

</Rule>