Skip to main content

"Failed to configure vAPI Endpoint Service at the firstboot time" while installing Windows VC 6.5

 

Symptoms
While configuring the vAPI EndPoint Service, you experience these symptoms:
  • Windows vCenter Server 6.5 installation fails while configuring the vAPI EndPoint Service
  • vCenter Server 6.5 installation on a Windows Server fails during the vAPI EndPoint Service during the firstboot time.
  • You see the error:

    Error: An error occurred while starting service 'vapi-endpoint'. Failed to start the vAPI Endpoint Service. Failed to configure vAPI Endpoint Service at the firstboot time. Please file a bug against VAPI
     
  • In vapi_firstboot.py_2948_stderr.log file, you see entries similar to:

    No valid files with pathname: C:\ProgramData\VMware\vCenterServer\logs\vapi\endpoint* found.
    ERROR starting vapi-endpoint rc: 2, stdout: , stderr: Start service request failed. Error: Service crashed while starting^M
    vapi firstboot failed
    Traceback (most recent call last):
    File "C:\Program Files\VMware\vCenter Server\firstboot\vapi_firstboot.py", line 536, in sys.exit(Main())
    File "C:\Program Files\VMware\vCenter Server\firstboot\vapi_firstboot.py", line 514, in Main vapi_firstboot()
    File "C:\Program Files\VMware\vCenter Server\firstboot\vapi_firstboot.py", line 502, in vapi_firstboot actionFirstboot(fbObj)
    File "C:\Program Files\VMware\vCenter Server\firstboot\vapi_firstboot.py", line 480, in actionFirstboot actionStart(fbObj)
    File "C:\Program Files\VMware\vCenter Server\firstboot\vapi_firstboot.py", line 485, in actionStart startService(msg, fbObj)
    File "C:\Program Files\VMware\vCenter Server\firstboot\vapi_firstboot.py", line 361, in proxy return func(args, *kwargs)
    File "C:\Program Files\VMware\vCenter Server\firstboot\vapi_firstboot.py", line 429, in startService fbObj.start_services()
    File "C:\Program Files\VMware\vCenter Server\firstboot\vapi_firstboot.py", line 225, in start_services self.start_service()
    File "C:\Program Files\VMware\vCenter Server\python-modules\cis\firstboot.py", line 272, in start_service service_start(self.get_eff_service_name())
    File "C:\Program Files\VMware\vCenter Server\python-modules\cis\utils.py", line 742, in service_start
    "localized": "Failed to configure vAPI Endpoint Service at the firstboot time",
    "translatable": "Failed to configure vAPI Endpoint Service at the firstboot time"
     
  • In the Firstbootinfrastructure logs file, you see entries similar to:

    WARNING firstbootInfrastructure Bug component info file does not exist
    INFO firstbootInfrastructure Firstboot duration: 178 sec
    INFO firstbootInfrastructure First boot is a failure
     
  • LDAP client receives this error:

    com.vmware.identity.interop.ldap.WinLdapClientLibrary, error code: 32
Cause
This issue occurs if there is a restriction in running Java.
 
Resolution
To resolve this issue:
  1. Ensure that the Domain login used to install vCenter Server has full Administrator privilege.
  2. Modify the group policies under the Software Restriction Policies section in the group/machine policy and allow permissions for Java.

Comments

Post a Comment

Popular posts from this blog

Error [403] The maximum number of sessions has been exceeded in the H5 client during login or logout

  Symptoms In virgo log, you see messages similar to: [2020-05-19T07:25:45.285Z] [ERROR] http-nio-5090-exec-130 72026859 142953 501051 com.vmware.vise.security.spring.DefaultAuthenticationProvider logout failed for sessionId 142953, clientId 501051 java.lang.IllegalStateException: The specified cardinality of 1..1 for osgi:reference implementing com.vmware.vcenter.apigw.api.ApiGatewaySessionManager in bundle com.vmware.h5ngc requires that exactly one OSGI service satisfies the filtering criteria but no such service was found.         at com.vmware.o6jia.context.ExternalServiceTargetSource.getTarget(ExternalServiceTargetSource.java:99)         at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:192)         at com.sun.proxy.$Proxy159.logout(Unknown Source)         at com.vmware.vise.security.spring.DefaultAuthenticationProvider.logoutInternal(DefaultAuthenticationProvider.java:548)         at c
Post a Comment
Read more

Investigating virtual machine file locks on ESXi

      Details Adding an existing virtual machine disk (VMDK) to a virtual machine that is already powered on fails.                 Failed to add disk scsi0:1. Failed to power on scsi0:1   Powering on the virtual machine results in the power on task remaining at 95% indefinitely. Cannot power on the virtual machine after deploying it from a template. Powering on a virtual machine fails with an error: Unable to open Swap File Unable to access a file since it is locked Unable to access a file <filename> since it is locked Unable to access Virtual machine configuration In the /var/log/vmkernel log file, you see entries similar to: WARNING: World: VM xxxx: xxx: Failed to open swap file <path>: Lock was not free WARNING: World: VM xxxx: xxx: Failed to initialize swap file <path>   When opening a console to the virtual machine, you may receive the error: Error connecting to <path><virtual machin
Post a Comment
Read more

"Performance data is currently not available for this entity" viewing the performance tab

  Symptoms While accessing the performance tab and navigating to Overview, you see: No data available   The data for Real time, but fails to retrieve it for past 1 day, week, month or year.  While selecting the advance parameter in performance tab, you see: Performance data is currently not available for this entity Cause This issue is caused by the vCenter Server database (Postgress) containing a stale/future time stamp reference for the ESXi host when the data was collected. For vCenter Servers using SQL, see  "Performance data is currently not available for this entity" error after updating rollup in vSphere Resolution Backup the vCenter database. For more info
Post a Comment
Read more