11 Replies Latest reply on Jun 19, 2018 7:30 AM by CERKYR

    vCenter 6.5 : failed to stat the service "vpxd"

    CERKYR Enthusiast

      Hello,

       

      I have this error message :
      "

      Cmd "sc queryex vpxd" failed with exit code 1060

        Cmd "sc qfailure vpxd" failed with exit code 1060

      "

      I just finish to install the vCenter 6.5 (ESXi 6.5 Essential Plus) wit success, and I just restart the Windows server.

       

      ------------

      From :

      c:\Program Files\VMware\vCenter Server\bin\

       

      I try :

      service-control --start vpxd-svcs

       

      and the result is :

      Perform start operation. vmon_profile=None, svc_names=['vpxd-svcs'], include_coreossvcs=False, include_leafossvcs=False

      2018-06-11T15:47:19.793Z   Service vpxd-svcs state STOPPED

      ------------

       

       

      How to fix this problem ?

       

      Regards,

        • 1. Re: vCenter 6.5 : failed to stat the service "vpxd"
          msripada Expert
          vExpert

          As this is windows vcenter 6.5, you might worth checking this KB VMware Knowledge Base

           

          Second is to check the vpxd-svcs.log under programdata\vmware\vcenter\logs and vmon-syslog.log file

           

          Thanks,

          MS

          • 2. Re: vCenter 6.5 : failed to stat the service "vpxd"
            CERKYR Enthusiast

            Hello,

            There is no Domain GPO because we are not inside a Windows Domain, just workgroup.
            And I just make a change inside the Local Security Policy, inside the "Open a session as a service", add the account used to run vCenter Services.

             

            I'm going ot check the logs ...I come back to you in few minutes ...

             

             

            --

            i have this error message :


            "Service VMwareDNSService does not seem to be registered with vMon. If this is unexpected please make sure your service config is a valid json. Also check vmon logs for warnings."

             

            and also :

             

            "Caused by: java.net.ConnectException: Connection refused: connect"

             

            My feeling is that the JAVA client is not configured ......

             

            Regards,

            • 3. Re: vCenter 6.5 : failed to stat the service "vpxd"
              daphnissov Guru
              Community WarriorsvExpert

              To start with, do not use a Windows based vCenter Server. Always stick to the appliance from now forward.

              • 4. Re: vCenter 6.5 : failed to stat the service "vpxd"
                CERKYR Enthusiast

                I try to reinstall the JAVA client (plugin) on my windows 2016.

                I also check the "local Policy Object" to allow session to start as service, with my dedicated account "administrator".

                ''

                And I stop the Vmware services

                 

                and start them.

                 

                Then, I catch the log from these starts :

                --

                Perform start operation. vmon_profile=ALL, svc_names=None, include_coreossvcs=True, include_leafossvcs=True

                2018-06-12T12:38:13.930Z   Service vmware-cis-config does not seem to be registered with vMon. If this is unexpected please make sure your service config is a valid json. Also check vmon logs for warnings.

                2018-06-12T12:38:13.930Z   State for service vmware-cis-config: STOPPED

                Successfully started service vmware-cis-config

                2018-06-12T12:38:15.055Z   Service VMWareAfdService does not seem to be registered with vMon. If this is unexpected please make sure your service config is a valid json. Also check vmon logs for warnings.

                2018-06-12T12:38:15.055Z   State for service VMWareAfdService: STOPPED

                Successfully started service VMWareAfdService

                2018-06-12T12:38:17.149Z   Service VMWareDirectoryService does not seem to be registered with vMon. If this is unexpected please make sure your service config is a valid json. Also check vmon logs for warnings.

                2018-06-12T12:38:17.149Z   State for service VMWareDirectoryService: STOPPED

                Successfully started service VMWareDirectoryService

                2018-06-12T12:38:20.201Z   Service VMWareCertificateService does not seem to be registered with vMon. If this is unexpected please make sure your service config is a valid json. Also check vmon logs for warnings.

                2018-06-12T12:38:20.201Z   State for service VMWareCertificateService: STOPPED

                Successfully started service VMWareCertificateService

                2018-06-12T12:38:22.299Z   Service VMwareIdentityMgmtService does not seem to be registered with vMon. If this is unexpected please make sure your service config is a valid json. Also check vmon logs for warnings.

                2018-06-12T12:38:22.299Z   State for service VMwareIdentityMgmtService: STOPPED

                Successfully started service VMwareIdentityMgmtService

                2018-06-12T12:38:24.339Z   Service VMwareSTS does not seem to be registered with vMon. If this is unexpected please make sure your service config is a valid json. Also check vmon logs for warnings.

                2018-06-12T12:38:24.339Z   State for service VMwareSTS: STOPPED

                Successfully started service VMwareSTS

                2018-06-12T12:38:30.688Z   Service VMwareDNSService does not seem to be registered with vMon. If this is unexpected please make sure your service config is a valid json. Also check vmon logs for warnings.

                2018-06-12T12:38:30.688Z   State for service VMwareDNSService: STOPPED

                Successfully started service VMwareDNSService

                2018-06-12T12:38:33.328Z   Service vmware-psc-client does not seem to be registered with vMon. If this is unexpected please make sure your service config is a valid json. Also check vmon logs for warnings.

                2018-06-12T12:38:33.328Z   State for service vmware-psc-client: STOPPED

                Successfully started service vmware-psc-client

                 

                Service-control failed.

                Error Failed to start vmon services.vmon-cli RC=2, stderr=Failed to start cm, rhttpproxy, sca services.

                Error: Service crashed while starting

                 

                --

                 

                I plan to study this link :
                VMware Knowledge Base

                • 5. Re: vCenter 6.5 : failed to stat the service "vpxd"
                  CERKYR Enthusiast

                  We don't plan to buy a vCenter Appliance Licence.

                  • 6. Re: vCenter 6.5 : failed to stat the service "vpxd"
                    CERKYR Enthusiast

                     

                    I just apply this KB : https://kb.vmware.com/s/article/2148054

                    VMware Knowledge Base

                     

                    c:\Program Files\VMware\vCenter Server\bin>service-control --start --all

                    ------------

                    Perform start operation. vmon_profile=ALL, svc_names=None, include_coreossvcs=True, include_leafossvcs=True

                    2018-06-12T13:01:35.357Z   Service vmware-cis-config does not seem to be registered with vMon. If this is unexpected please make sure your service config is a valid json. Also check vmon logs for warnings.

                    2018-06-12T13:01:35.357Z   State for service vmware-cis-config: STOPPED

                    Successfully started service vmware-cis-config

                    2018-06-12T13:01:36.419Z   Service VMWareAfdService does not seem to be registered with vMon. If this is unexpected please make sure your service config is a valid json. Also check vmon logs for warnings.

                    2018-06-12T13:01:36.419Z   State for service VMWareAfdService: STOPPED

                    Successfully started service VMWareAfdService

                    2018-06-12T13:01:38.517Z   Service VMWareDirectoryService does not seem to be registered with vMon. If this is unexpected please make sure your service config is a valid json. Also check vmon logs for warnings.

                    2018-06-12T13:01:38.517Z   State for service VMWareDirectoryService: STOPPED

                    Successfully started service VMWareDirectoryService

                    2018-06-12T13:01:41.579Z   Service VMWareCertificateService does not seem to be registered with vMon. If this is unexpected please make sure your service config is a valid json. Also check vmon logs for warnings.

                    2018-06-12T13:01:41.579Z   State for service VMWareCertificateService: STOPPED

                    Successfully started service VMWareCertificateService

                    2018-06-12T13:01:43.689Z   Service VMwareIdentityMgmtService does not seem to be registered with vMon. If this is unexpected please make sure your service config is a valid json. Also check vmon logs for warnings.

                    2018-06-12T13:01:43.689Z   State for service VMwareIdentityMgmtService: STOPPED

                    Successfully started service VMwareIdentityMgmtService

                    2018-06-12T13:01:45.759Z   Service VMwareSTS does not seem to be registered with vMon. If this is unexpected please make sure your service config is a valid json. Also check vmon logs for warnings.

                    2018-06-12T13:01:45.759Z   State for service VMwareSTS: STOPPED

                    Successfully started service VMwareSTS

                    2018-06-12T13:01:50.004Z   Service VMwareDNSService does not seem to be registered with vMon. If this is unexpected please make sure your service config is a valid json. Also check vmon logs for warnings.

                    2018-06-12T13:01:50.004Z   State for service VMwareDNSService: STOPPED

                    Successfully started service VMwareDNSService

                    2018-06-12T13:01:52.957Z   Service vmware-psc-client does not seem to be registered with vMon. If this is unexpected please make sure your service config is a valid json. Also check vmon logs for warnings.

                    2018-06-12T13:01:52.957Z   State for service vmware-psc-client: STOPPED

                    Successfully started service vmware-psc-client

                     

                     

                    Service-control failed. Error Failed to start vmon services.vmon-cli RC=2, stderr=Failed to start cm, rhttpproxy, sca services. Error: Service crashed while starting

                    ------------

                    • 7. Re: vCenter 6.5 : failed to stat the service "vpxd"
                      daphnissov Guru
                      Community WarriorsvExpert

                      There is no such thing as a license to the vCenter Server Appliance. It's just a regular vCenter license. Besides, Windows vCenter is gone in the next major release, so there is zero reason to deploy a new Windows-based vCenter at this time.

                      • 8. Re: vCenter 6.5 : failed to stat the service "vpxd"
                        CERKYR Enthusiast

                        Hello,

                        Then, we bought a Vcenter licence few months ago, and VMware plan to stop this tool, and the only way to obtain the vCenter fonctionnalities is to buy a other licence dedicated for VCSA ?
                        is it correct ?

                        Can we believe to use the same licence vCenter with VCSA ?

                        Regards,

                        • 9. Re: vCenter 6.5 : failed to stat the service "vpxd"
                          daphnissov Guru
                          Community WarriorsvExpert

                          No, as I said, there is only a license called "vCenter". There is not a license called "vCenter Server Appliance". The license is the same regardless of whether you install the Windows version or appliance.

                          • 10. Re: vCenter 6.5 : failed to stat the service "vpxd"
                            msripada Expert
                            vExpert

                            As one of our community members explained, you can use the VCSA with same license. If you want to continue with windows installation which is currently exisitng, then please follow the below steps and check if that resolves

                             

                            Okay, from the logs everytime it fails with cm service and rhttproxy. I believe it is because, you have port 80 or 443 being used by another software on that machine.

                             

                            open cmd -> netstat -anob |findstr 80 -> check the pid number

                            Open task manager -> services -> PID (tab) -> find which service is being used.

                             

                            If it is showing as PID 4 , one of the Microsoft services are using that port which usually is IIS service or a list of other conflicting services mentioned in this.

                            VMware Knowledge Base

                            VMware Knowledge Base

                             

                            Thanks,

                            MS

                            • 11. Re: vCenter 6.5 : failed to stat the service "vpxd"
                              CERKYR Enthusiast

                              Considering that vCenter for Windows is plnned to disapear for the next version (6.8 ?); I decide to use the VCSA instead with success.

                              (it's more easy to install)