alex1002
Enthusiast
Enthusiast

Vsphere 6.5 U1 update on Windows fails

Jump to solution

Installation of component VCSServiceManager failed with error code '1603'. Check the logs for more details

I tried to turn on all dot net

1 Solution

Accepted Solutions
Jbp85
Contributor
Contributor

I found the problem.

In fact the vcsservicesmanager.msi finish to start all VMware services. The "VMware Platfom Service Controller Client" service start and stop.

In the wrapper.log of VMware-psc-client (C:\ProgramData\VMware\vCenterServer\runtime\vmware-psc-client\logs\wrapper.log), I noticed there was a wrapper license problem.

During the upgrade the java wrapper of vmware-psc-client is updated but the wrapper.conf is not replaced. The new wrapper version need a license which is not in the old wrapper.conf file.

During the upgrade (after the services stopped) I removed the bin and conf folder in : C:\ProgramData\VMware\vCenterServer\runtime\vmware-psc-client.

The upgrade finished well !

It took me 3 days !!!

View solution in original post

41 Replies
rcporto
Leadership
Leadership

Can you confirm if .NET 3.5 is installed before you start the vCenter installation? Check the following VMware KB article: "Installation of component VCSServiceManager failed with error code '1603' " error (2127519) | VMwar...

---

Richardson Porto
Senior Infrastructure Specialist
LinkedIn: http://linkedin.com/in/richardsonporto
0 Kudos
vijayrana968
Virtuoso
Virtuoso

Make sure the IPv4 stack is installed. If the command netsh interface ipv4 show interfaces results in a message: The request is not supported., the IPv4 stack has been uninstalled and should be reinstalled. To reinstall the IPv4 stack, run the netsh interface ipv4 install command and reboot the machine.

0 Kudos
alex1002
Enthusiast
Enthusiast

Checked for dot net all good

Checked upv4 stack all 

Good

0 Kudos
Camero
VMware Employee
VMware Employee

Would you be able to provide the install logs here ?

0 Kudos
i5rov
Contributor
Contributor

I am having exact same issue, I can provide install logs, where should I send them

0 Kudos
Camero
VMware Employee
VMware Employee

Attach the logs to this thread ...

If you need to scrub/change any confidential info like IP's, system name etc.. please do before attaching the logs here ..

alex1002
Enthusiast
Enthusiast

Im trying to add here, but says file is too large.

File 'VMware-VCS-logs-20170803104305.zip' is too large.

0 Kudos
destevez54
Contributor
Contributor

I found that the installation of KB4025339's delta update had failed on my Server 2016 system. Installing the full update from the Microsoft Catalog allowed me to get past this error.

0 Kudos
Jbp85
Contributor
Contributor

Hi,

I got exactly the same issue.

I tried every KB !

JB

0 Kudos
NetxRunner
Enthusiast
Enthusiast

Have you tried disabling the Syslog Collector Service? I had the same issue updating vCenter Server 6.0 to U2 and this worked out for me.

0 Kudos
alex1002
Enthusiast
Enthusiast

how to disable this service?

0 Kudos
alex1002
Enthusiast
Enthusiast

Attached the logs

0 Kudos
Camero
VMware Employee
VMware Employee

the problem is VMwareSTS service is not starting during the update.

Can you please attach the VMwareSTS logs at the time 2017-08-09T18:15:13 from the SSO folder  at C:\ProgramData\VMware\vCenterServer\runtime\VMwareSTSservice\logs\

from vminst-con.log

===

2017-08-09T18:15:13.346Z   ERROR Starting service: VMwareSTS, Exception: (2, 'StartService', 'The system cannot find the file specified.')

Error executing start on service VMwareSTS. Details {

    "resolution": null,

    "detail": [

        {

            "args": [

                "VMwareSTS"

            ],

            "id": "install.ciscommon.service.failstart",

            "localized": "An error occurred while starting service 'VMwareSTS'",

            "translatable": "An error occurred while starting service '%(0)s'"

        }

    ],

    "componentKey": null,

    "problemId": null

}

Service-control failed. Error {

    "resolution": null,

    "detail": [

        {

            "args": [

                "VMwareSTS"

            ],

            "id": "install.ciscommon.service.failstart",

            "localized": "An error occurred while starting service 'VMwareSTS'",

            "translatable": "An error occurred while starting service '%(0)s'"

        }

    ],

    "componentKey": null,

    "problemId": null

}

===

0 Kudos
Anil0210
Contributor
Contributor

What is your operating system ? Is it Windows 2016 ?

0 Kudos
Jbp85
Contributor
Contributor

This STS error is logged after the upgrade failed and after we have to click on OK in the 1603 error message box.

It's when the setup try to rollback.

0 Kudos
Jbp85
Contributor
Contributor

In my case 2008R2

0 Kudos
NetxRunner
Enthusiast
Enthusiast

In your vCenter Windows Appliance navigate to "Services" and find "VMware Syslog Collector". Right click and press stop.

Also, this article implies that 1603 error can be caused by Syslog Collector Service unable to start automatically: vCenter 6.0u1b to 6.0u2 Upgrade Error: VMware Syslog Component – Virtual Chris

Try both options:

- disable it

- follow the article and change the cfg file

0 Kudos
alex1002
Enthusiast
Enthusiast

Attached are the logs from VMwareSTSService.

0 Kudos
Jbp85
Contributor
Contributor

I found the problem.

In fact the vcsservicesmanager.msi finish to start all VMware services. The "VMware Platfom Service Controller Client" service start and stop.

In the wrapper.log of VMware-psc-client (C:\ProgramData\VMware\vCenterServer\runtime\vmware-psc-client\logs\wrapper.log), I noticed there was a wrapper license problem.

During the upgrade the java wrapper of vmware-psc-client is updated but the wrapper.conf is not replaced. The new wrapper version need a license which is not in the old wrapper.conf file.

During the upgrade (after the services stopped) I removed the bin and conf folder in : C:\ProgramData\VMware\vCenterServer\runtime\vmware-psc-client.

The upgrade finished well !

It took me 3 days !!!

View solution in original post