You receive a "The MOM Server failed to install agent on remote computer" error message when you try to install Microsoft Operations Manager (MOM) agents by using the Push distribution method (909031)



The information in this article applies to:

  • Microsoft Operations Manager 2005

SYMPTOMS

When you try to install Microsoft Operations Manager (MOM) agents by using the Push distribution method, you receive the following error message:

The MOM Server failed to install agent on remote computer <full_computer_name>.
Error Code: -2147467259
Error Description: The Agent could not contact the MOM Server.
Microsoft Installer Error Description: No Description Available


Additionally, the following symptoms occur:
  • A message that is similar to the following appears in the MOM Management Server computer's Application log:

    Event Type: Error
    Event Source: Microsoft Operations Manager
    Event Category: MOM Server
    Event ID: 21083
    Date: date
    Time: time
    User: domain\mom_action_account
    Computer: SERVER_NAME
    Description: The MOM Server failed to install agent on remote computer <full_computer_name>.

    Error Code: -2147467259 Error Description: The Agent could not contact the MOM Server. Microsoft Installer Error Description: No Description Available
  • The following error message is logged in the MOMService.mc8 log file on the MOM agent:

    Err:Unable to open channel to server using the MOMX protocol.
  • The following error message is logged in the MOMService.mc8 log file on the MOM Management Server computer:

    Err:AcceptSecurityContext failed, error = -2146893056
  • MOM agents may not be able to communicate with the MOM Management Server computer.
  • MOM agents may fail over to other MOM Management Server computers.

CAUSE

This problem occurs when the EnablePMTUDiscovery registry entry in the following registry subkey is set to 0:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters



If this entry is set to 0, the MOM agent Kerberos negotiate packets are fragmented because of small packet sizes.

Note By default, this registry value is set to 0 when you install ISA Server 2004.

RESOLUTION

To resolve this problem, use one of the following methods.

Method 1: Set the value of the EnablePMTUDiscover registry entry to 1 on the MOM Management Server computer and on the agents

To set the value of this registry entry to 1, follow these steps:
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate the following registry subkey:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

  3. Right-click EnablePMTUDiscovery, and then click Modify.
  4. In the Value data box, type 1, and then click OK.
  5. Quit Registry Editor, and then restart the computer.

Method 2: Turn off the Mutual Authentication setting for all agents

  1. In the MOM 2005 Administrator console, expand Microsoft Operations Manager (Your Site), expand Administration, and then click Global Settings.
  2. In the details pane, right-click Communications, and then click Properties.
  3. Click the Security tab, click to clear the Mutual Authentication required check box, and then click OK.
  4. When you receive a warning that states that the agents and that MOM Management Server computers must be synchronized, click OK .
  5. In the navigation pane, expand Computers, and then click Agent-managed Computers.
  6. In the details pane, select all the agent-managed computers.
  7. On the Action menu, point to All Tasks, click Update Agent Settings, and then click OK.
    Note Unless you have configured custom accounts, accept the following default settings:
    1. For the Which account do you want to use for updating the agent settings option, select the default setting of Management Server Action Account.
    2. For the Which account do you want to use for the Agent Action Account option, select the default setting of Local System.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Modification Type:MinorLast Reviewed:11/22/2005
Keywords:kberrmsg kbtshoot kbprb KB909031 kbAudITPRO