Just to be clear, I am not using the Windows vcenter server by choice. I would rather use the appliance
C:\Users\raub> "C:\Program Files\VMware\vCenter Server\bin\service-control" --start vspherewebclientsvc Operation not cancellable. Please wait for it to finish... Performing start operation on service vsphere-client... Error executing start on service vsphere-client. Details { "detail": [ { "id": "install.ciscommon.service.failstart", "translatable": "An error occurred while starting service '%(0)s'", "localized": "An error occurred while starting service 'vsphere-client'", "args": [ "vsphere-client" ] } ], "resolution": null, "problemId": null, "componentKey": null } Service-control failed. Error: { "detail": [ { "id": "install.ciscommon.service.failstart", "translatable": "An error occurred while starting service '%(0)s'", "localized": "An error occurred while starting service 'vsphere-client'", "args": [ "vsphere-client" ] } ], "resolution": null, "problemId": null, "componentKey": null } C:\Users\raub>I understand that "An error occurred while starting service 'vsphere-client'", but what is it?
Maybe the log file is more helpful. https://kb.vmware.com/s/article/2121043 claims log dir is
C:\ProgamData\VMware\vCenterServer\logs\vsphere-client\logs\
But I can see lots of directories in there but the log one:
C:\Users\raub>dir "C:\Program Files\VMware\vCenter Server\logs" Volume in drive C has no label. Volume Serial Number is F020-F58F Directory of C:\Program Files\VMware\vCenter Server File Not Found C:\Users\raub>
Where can I find where vcenter thinks the log files are at?
UPDATE: Since my post got all mangled, I posted a human readable version at Record of the UNIX Wars: VMWare ESXI Gripes: service-control error message not particularly useful
