1 Reply Latest reply on Jul 16, 2020 3:14 AM by calale

    Error after upgrade vcenter windows 6.5 last release (VCSServiceManager failed)

    calale Lurker

      Hello,

      i tried to upgrade my vcenter 6.5 to last release available for my installation : VMware vCenter Server v6.5.0.6430.

      The installation start but after few minutes stuck on this problem : "Installation of component VCSServiceManager failed with error code '1603'

      Now the old installation does not start with this problem related on vmon.log

       

      Service cm api-health command's stderr: ERROR:root:CM search failed. ProductId=com.vmware.cis, TypeId=cs.identity

       

       

      2020-07-16T00:46:44.116+02:00| vthread-5| W115:

      2020-07-16T00:46:44.116+02:00| vthread-5| W115: Service cm api-health command's stderr: ERROR:root:Error connecting to CM: {

       

       

      2020-07-16T00:46:44.116+02:00| vthread-5| W115+     "resolution": {

      2020-07-16T00:46:44.116+02:00| vthread-5| W115+         "id": "install.default.failure.resolution",

      2020-07-16T00:46:44.116+02:00| vthread-5| W115+         "localized": "This is an unrecoverable error, please retry install. If you encounter this error again, please search for these symptoms in the VMware Knowledge Base for any known issues and possible resolutions. If none can be found, collect a support bundle and open a support request.",

      2020-07-16T00:46:44.116+02:00| vthread-5| W115+         "translatable": "This is an unrecoverable error, please retry install. If you encounter this error again, please search for these symptoms in the VMware Knowledge Base for any known issues and possible resolutions. If none can be found, collect a support bundle and open a support request."

      2020-07-16T00:46:44.116+02:00| vthread-5| W115+     },

      2020-07-16T00:46:44.116+02:00| vthread-5| W115+     "detail": [

      2020-07-16T00:46:44.116+02:00| vthread-5| W115+         {

      2020-07-16T00:46:44.116+02:00| vthread-5| W115+             "args": [

      2020-07-16T00:46:44.116+02:00| vthread-5| W115+                 "CM search failed. ProductId=com.vmware.cis, TypeId=cs.identity:[Errno 10061] No connection could be made because the target machine actively refused it"

      2020-07-16T00:46:44.116+02:00| vthread-5| W115+             ],

      2020-07-16T00:46:44.116+02:00| vthread-5| W115+             "id": "install.ciscommon.internal.error",

      2020-07-16T00:46:44.116+02:00| vthread-5| W115+             "localized": "Encountered an internal error.\n\nCM search failed. ProductId=com.vmware.cis, TypeId=cs.identity:[Errno 10061] No connection could be made because the target machine actively refused it",

      2020-07-16T00:46:44.116+02:00| vthread-5| W115+             "translatable": "Encountered an internal error.\n\n%(0)s"

      2020-07-16T00:46:44.116+02:00| vthread-5| W115+         }

      2020-07-16T00:46:44.116+02:00| vthread-5| W115+     ],

      2020-07-16T00:46:44.116+02:00| vthread-5| W115+     "componentKey": null,

      2020-07-16T00:46:44.116+02:00| vthread-5| W115+     "problemId": null

      2020-07-16T00:46:44.116+02:00| vthread-5| W115+ }

      2020-07-16T00:46:44.116+02:00| vthread-5| W115:

       

      Some ideas for fix this problem ?

      Thank you so much


      Alessandro.

        • 1. Re: Error after upgrade vcenter windows 6.5 last release (VCSServiceManager failed)
          calale Lurker

          When i am try to start the service i receive this output :

           

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

          2020-07-16T09:27:29.191Z   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 warn

          ings.

          2020-07-16T09:27:29.191Z   State for service vmware-cis-config: STOPPED

          Successfully started service vmware-cis-config

          2020-07-16T09:27:30.238Z   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 warni

          ngs.

          2020-07-16T09:27:30.238Z   State for service VMWareAfdService: STOPPED

          Successfully started service VMWareAfdService

          2020-07-16T09:27:32.348Z   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.

          2020-07-16T09:27:32.348Z   State for service VMWareDirectoryService: STOPPED

          Successfully started service VMWareDirectoryService

          Service VMWareCertificateService startup type is not automatic. Skip

          2020-07-16T09:27:36.410Z   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.

          2020-07-16T09:27:36.410Z   State for service VMwareIdentityMgmtService: STOPPED

          Successfully started service VMwareIdentityMgmtService

          2020-07-16T09:27:39.628Z   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.

          2020-07-16T09:27:39.628Z   State for service VMwareSTS: STOPPED

          Successfully started service VMwareSTS

          2020-07-16T09:27:45.704Z   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 warni

          ngs.

          2020-07-16T09:27:45.704Z   State for service VMwareDNSService: STOPPED

          Successfully started service VMwareDNSService

          2020-07-16T09:27:46.751Z   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 warn

          ings.

          2020-07-16T09:27:46.751Z   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=1, stderr=Failed to start cis-license, cm, eam, sca, vsphere-ui, vsphere-client services. Error: Operation timed out