Configuring HA on an ESXi 5.x host fails with the error: Cannot install the vCenter agent service. Unknown installer error
search cancel

Configuring HA on an ESXi 5.x host fails with the error: Cannot install the vCenter agent service. Unknown installer error

book

Article ID: 311166

calendar_today

Updated On:

Products

VMware vCenter Server VMware vSphere ESXi

Issue/Introduction

Symptoms:
  • Cannot configure High Availability (HA) on an ESXi 5.x host.
  • Configuring HA on an ESXi 5.x host fails.
  • You see the error:

    Cannot install the vCenter agent service. Unknown installer error

  • In the %ALLUSERSPROFILE%\Application Data\VMware\VMware VirtualCenter\Logs\vpxd log file, you see entries similar to:

    Note: In Windows 2008 R2, the vpxd.log file is located at %ALLUSERSPROFILE%\Program Data\VMware\VMware VirtualCenter\Logs\.

    verbose 'Default'] [FdmClientAdapter] Logging in to host 192.168.0.150
    error 'HttpConnectionPool'] [ConnectComplete] Connect error A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
    error 'Default' opID=3544ed68] [HttpUtil::ExecuteRequest] Error in sending request - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
    error 'Default' opID=3544ed68] [ServerAccess] Exception while invoking remote login: vim.fault.HttpFault
    error 'DAS'] [FdmManager::ScanForMaster] Failed to get cluster info from 192.168.0.156 (cluster=Cluster): class
    error 'Default'] [FdmClientAdapter] Unexpected error logging into host 192.168.0.156: Invalid response code: 400 Bad Request
    error 'DAS'] [FdmManager::ScanForMaster] Failed to get cluster info from 192.168.0.156 (cluster=Cluster): class

  • In the fdm-installer.log/var/log file or syslog.log/var/log file, you see entries similar to:

    • fdm-installer: Installing the VIB
      fdm-installer: Result of esxcli software vib install -v=/tmp/vmware-root/ha-agentmgr/vpx-upgrade-installer/vmware-fdm.vib: [DependencyError]
      fdm-installer: VIB LSI_bootbank_vmware-esx-sas2flash_1.0-03's acceptance level is unsigned, which is not compliant with the ImageProfile acceptance level partner

    • [NoMatchError]
      BIOS vendor HP is required but host BIOS vendor is
      BIOS vendor Hewlett-Packard Company is required but host BIOS vendor is
      BIOS vendor Hewlett-Packard is required but host BIOS vendor is
      BIOS vendor hp is required but host BIOS vendor is
      id = (Updated) HP-ESXi-5.1.0-standard-iso
      Please refer to the log file for more details.vmware
    • [12912283] 2016-01-13 10:19:54: status = 0
      fdm-installer: [12912283] 2016-01-13 10:19:54: Installing the VIB
      fdm-installer: [12912283] 2016-01-13 10:19:57: Result of esxcli software vib install -v=/tmp/vmware-root/ha-agentmgr/vpx-upgrade-installer/vmware-fdm.vib: [InstallationError]
      fdm-installer: Error in running rm /tardisks/vmware-f.v00:
      fdm-installer: Return code: 1
      fdm-installer: Output: rm: cannot remove '/tardisks/vmware-f.v00': Device or resource busy -----> Error
      fdm-installer:
      fdm-installer: It is not safe to continue. Please reboot the host immediately to discard the unfinished update.
      fdm-installer: Please refer to the log file for more details.


  • Running the esxcli software vib remove -n vmware-fdm command fails with the error:

    [DependencyError]
    VIB VMware_bootbank_ilfu_1.23-4.56's acceptance level is community, which is not compliant with the ImageProfile acceptance level partner
    To change the host acceptance level, use the 'esxcli software acceptance set' command.
    Please refer to the log file for more details.


Environment

VMware vSphere ESXi 5.0
VMware vSphere ESXi 5.5
VMware vCenter Server 5.5.x
VMware vSphere ESXi 5.1
VMware vCenter Server 5.0.x
VMware vCenter Server 5.1.x

Cause

This issue occurs due to acceptance level issues with the vSphere Installation Bundle (VIB) and the host.

Resolution

To resolve this issue, use one of these options:

  • Remove the VIB causing the issue.

    To remove the VIB causing the issue:
    1. Identify the VIB using this command:

      esxcli software vib list

    2. Remove the VIB using this command:

      esxcli software vib remove -n VIBname

      For example:

      esxcli software vib remove -n vmware-fdm
    3. Configure HA on the host again:

      1. Right-click on the affected host(s).
      2. Click Reconfigure for vSphere HA.

  • Change the host acceptance level to the VIB's acceptance level.

    To change the host acceptance level to the VIB's acceptance level, run this command:

    esxcli software acceptance set --level VIB_acceptance_level

    For example:

    esxcli software acceptance set --level CommunitySupported

  • If the BIOS is reported as invalid, update the BIOS to the latest version.

Note: If the preceding information does not resolve the issue, see Cannot configure HA after disabling the Host Welcome login page on an ESXi host (2009546).

Additional Information

Cannot configure HA after disabling the Host Welcome login page on an ESXi host
ESXi 5.x ホストでの HA の構成が次のエラーで失敗する: vCenter エージェント サービスをインストールできません。不明なインストーラ エラー
在 ESXi 5.x 主机上配置 HA 失败，并出现错误“无法安装 vCenter 代理服务。未知安装程序错误”

Powered by Wolken Software