Unable to start vCenter service.Failed to start vapi-endpoint services. "Service—control failed. Error: Failed to start services in profile ALL. while starting RC=2 , stderr=FaiIed to start vapi—endpoint services. Error : Service crashed"
search cancel

Unable to start vCenter service.Failed to start vapi-endpoint services. "Service—control failed. Error: Failed to start services in profile ALL. while starting RC=2 , stderr=FaiIed to start vapi—endpoint services. Error : Service crashed"

book

Article ID: 391682

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

  • Unable to perform backups for the VMs residing on the vCenter.
    service-control --start --all 
    
    Performing start operation on service vmdird...
    Successfully started service vmdird 
    Performing start operation on service vmcad... 
    Successfully started service vmcad 
    Performing start operation on service vmware-sts-idmd... 
    Successfully started service vmware-sts-idmd
    Performing start operation on service vmware-stsd... 
    Successfully started service vmware-stsd 
    Performing start operation on service vmdnsd... 
    Successfully started service vmdnsd 
    Performing start operation on profile: ALL...
    Successfully started service vmware-vmon 
    Service—control failed. Error: Failed to start services in profile ALL. while starting RC=2 , stderr=FaiIed to start vapi—endpoint services. Error : Service crashed
  • When reviewing the Tenant configuration in VMDir (Services > Identity Managers > Tenants > vsphere.local) using JXplorer or after exporting an LDIF DUMP (see How to export VMDir information from vCenter Server Appliance or Platform Service Controller using the JXplorer or ldapsearch) , there are multiple STS TenantCredential tokens and TrustedCertChain chains seen, despite vCenter running as standalone

Environment

VMware vCenter Server 7.0.x

VMware vCenter Server 8.0.x

Resolution

  • To fix this issue, ensure that a fresh offline snapshot of the vCenter Server exists, then run the fixsts script attached in kb 76719.