Installation of component VCSServiceManager failed with error code '1603'. Check the logs for more details
I tried to turn on all dot net
Your method didnt work for me
I'm sorry. The error code is very generic.
Can you check if the services start well (via Event viewer) when the vcsservicemanager.msi is proceed ? And if one start and stop ?
Doesnt start
Dear Jbp85
I was working on this issue the last few days and it drove me almost crazy. I had the same error in the wrapper.log but did not have the idea to just delete the files.
So your solution worked for my environment - I modified steps a bit: before starting Setup I stopped all vCenter Services, deleted the Folders and then started Setup.
Perfect! Thanks a lot for sharing your information.
BTW: I have Win2008R2 and adressed the issue while updating my (external) PSC from V6.5d to V6.5U1. I had the issue only in my production Environment... in my development Environment I updated first and has the same configuration like production strangly anything worked without a Problem.
@RLI2013 I tried your method with no luck. Anyone else can suggest something else?
This solved my issue as well.
The entry in the "\ProgramData\VMware\vCenterServer\runtime\vmware-psc-client\logs\wrapper.log" is:
STATUS | wrapper | 2017/08/11 09:44:16 | <-- Wrapper Stopped
STATUS | wrapper | 2017/08/11 09:53:16 | --> Wrapper Started as Service
STATUS | wrapper | 2017/08/11 09:53:16 | Java Service Wrapper Professional Edition 64-bit 3.5.30
STATUS | wrapper | 2017/08/11 09:53:16 | Copyright (C) 1999-2016 Tanuki Software, Ltd. All Rights Reserved.
STATUS | wrapper | 2017/08/11 09:53:16 | http://wrapper.tanukisoftware.com
STATUS | wrapper | 2017/08/11 09:53:16 |
ERROR | wrapper | 2017/08/11 09:53:16 | License Error:
ERROR | wrapper | 2017/08/11 09:53:16 | A valid license was not found in the Wrapper configuration file.
ERROR | wrapper | 2017/08/11 09:53:16 |
ERROR | wrapper | 2017/08/11 09:53:16 | The Java Service Wrapper requires a License Key to activate the
ERROR | wrapper | 2017/08/11 09:53:16 | software. License Keys can be purchased on the Java Service Wrapper
ERROR | wrapper | 2017/08/11 09:53:16 | web site:
ERROR | wrapper | 2017/08/11 09:53:16 | http://wrapper.tanukisoftware.com/purchase
ERROR | wrapper | 2017/08/11 09:53:16 |
ERROR | wrapper | 2017/08/11 09:53:16 | You can also immediately obtain a one-month Free trial license:
ERROR | wrapper | 2017/08/11 09:53:16 | http://wrapper.tanukisoftware.com/trial
ERROR | wrapper | 2017/08/11 09:53:16 |
ERROR | wrapper | 2017/08/11 09:53:16 | License Keys can be generated for the following HostId:
ERROR | wrapper | 2017/08/11 09:53:16 | HostId #1: 000c2983bf51
ERROR | wrapper | 2017/08/11 09:53:16 |
ERROR | wrapper | 2017/08/11 09:53:16 |
ERROR | wrapper | 2017/08/11 09:53:16 | Optional host name for license: XXXXXXXXXXXXXXX
STATUS | wrapper | 2017/08/11 09:53:16 | <-- Wrapper Stopped
Anymore ideas?
IPV6 is on, and no luck
Anymore ideas?
Thanks Jbp85 deleting the bin and conf folders under vmware-psc-client during installation fixed the issue for me as well.
What is current version on vcenter server
Thanks! This fixed my 6.5 to 6.5u1 upgrade problem as well.
I am getting this error as well. Originally I was getting the license error in the wrapper log, but have resolved that, but still failing at the same point, w/ 1603. VMware support wants me to wipe out the vcenter server, and start from scratch.
.net 3.5 is installed
ipv4 stack is good
ipv6 is checked.
This worked for me as well. Curious, I have two vCenter Servers that were upgraded; one worked with out a hitch, the second I had to use your method. I wonder if VMware is doing somehting about this?
Hi all,
I had the same predicament when i tried to upgrade from 6.5 to 6.5u1. The dreaded error came up and the rollback bricked my VCenter.... fun times eh?
After creating a case with VMware support and having them examine log files we moved to a webex. The support guy was thoroughly disappointed that I didn't have a backup, no snapshot (physical server), no system restore also. In hindsight it would have been much easier if I had a snap or backup..but then I would not need their help....
Alas, he examined my configuration and with a regret he advised that I do a clean install and rebuild my VCenter manually.
The upgrade rollback procedure messed up my vmon service and it wasn't starting.
The error 1603 is not exactly a vmware error, it's a generic .msi install error. That is why it is hard to troubleshoot, it has no extensive logging. It simply chooses to fail, and lets vmware do a rollback procedure (with unpredictable outcomes, apparently).
Now, troubleshooting an .msi install is what you could do next but it is overwhelming for me, and it would be of little use at this point.
How I solved my problem is, I manually installed the VCSservicemanager by running the %POINTOFINSTALLATION%\vCenter-Server\Packages\VCSServiceManager.msi
It installed silently, with no user input required, and it properly showed up in the Control Panel\Programs and Features
Afterwards, all I did is rerun the install/upgrade program for VCenter 6.5 U1
Queue some prayers to all of the digital deities... and voila the upgrade procedure completes without a hitch.
Now I have a running VCenter 6.5u1 !!!
Please note: This is not a recommended workaround, this is what a desperate sysadmin does!
Mea culpa:no proper backup.
This worked for me as far as getting the upgrade to complete.
VCenter was still acting goofy so I did a reboot.
I'll see how that works out.
ETA... It didn't. I ended up stepping back, stopping all VM services and deleting the bin and conf folders. We'll see how that works.
ETAA...
Stopping the VM services AND deleting the bin and conf folders allowed the upgrade to proceed. It came up and all ran well.
You are right!!!
That's the only thing that helped me!
I tried all that I found on internet....
Good job mate
Jbp85 Many thanks for your helpful post
I dont understand what you did?