Home
  •  

Microsoft.SystemCenter.VirtualMachineManager.2007.Library.AgentNotResponding.rule (Rule)

Knowledge Base article:

Summary

Virtual Machine Manager was unable to contact the library server at the indicated date and time. When a VMM agent stops responding, a single alert is raised in the Operations Console. Check the status of the library server in Virtual Machine Manager for more information.

Causes

Possible causes for a Virtual Machine Manager agent not responding on a library server include:

1

WS-Management, also known as Windows Remote Management (WinRM) on the library server has stopped.

2

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

3

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

4

Windows Firewall is enabled on the library server, 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

5

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

Resolutions

To troubleshoot these issues:

1

Ensure that you can connect to the library server from the VMM server.

2

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

3

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

  • Administrators

  • Virtual Machine Manager Servers

4

If Windows Firewall is enabled on the library server, 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

5

Check whether the WinRM listener is present on the library server. 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 in sample.)

Hostname

Enabled = true

URLPrefix = wsman

CertificateThumbprint

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

In you updated any configurations in steps 3-5, you must uninstall and re-install the Virtual Machine Manager agent on the library server.

7

Remove the Virtual Machine Manager agent locally on the library server by using Add or Remove Programs.

8

Reinstall the Virtual Machine Manager agent on the library server. In any view in the VMM Administrator Console, click Add library server in the Actions pane, and follow the wizard instructions to add the library server and the existing library shares to VMM.

Additional

Windows NT Event 436, 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
Library server agent 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.Library.AgentNotResponding.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>436</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.Library.AgentNotResponding_Rule.AlertMessage"]$</AlertMessageId>

      <AlertParameters>

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

      </AlertParameters>

    </WriteAction>

  </WriteActions>

</Rule>