Hi,
I'm trying to upgrade our vCenter server from version 5.5 to 6.0, but its a boxing match, and so far the vCenter server has won I'm afraid...
The problem is that I get a error when installing saying, "unable to install the syslog collector servie", and list's a few files, then an error saying "Installtion of component VCSServiceManager failed with error code 1603".
Our set up: Windows server 2008 R2, all vcenter services including sql is on the same server. Only one vcenter server as well.
I have read a lot on this problem and tested some stuff, but havent found any solution yet.
Things I've tryied:
What more can I check? What could be the issue here?
Thanks in advance! See attached file's on the error
Problem is now solved.
Read today that vmware released a new release, vcenter 6.0 update 1, build 3040890. After tying to install with that instead of build 2656757 it worked like a charm. No errors and no warings, worked right away.
HI ,
please go in the temp directory by typing %temp% from run and checkek the install file to get the correct failure message in the log file . If possible please share the file and we can have a look.
Thanks.
please fix issue with below details
VMware KB: Modifying the VMware Syslog Collector settings after it is installed
and then follow below given steps
Hi, thanks for anserwing.
I found some install logs, I've attached them to the origninal message.
I will also try what you,IBM_IndiaIBM_India , said and get back to you. I know I have no trailing white space in the ODCB, but I will try the other thing you mentioned.
I dident get it to work with your solution either IBM_India, same error. I will give it a couple of more tryies, but I dont know what more to try.
Any other ideés are much appreciated.
Thanks,
Please check before installation that your virtual or physical vCenter Server meets the following hardware requirements:
Thanks for anserwing.
My vCenter has 2vCPU's, 10GBG of RAM, and I have now also raised the freespace on the server to more than 44gb free. but I'm sorry to say that its still the same error as mentioned before.
Anyone that has any clue on why this is happening? We are still having this issue.
Thanks.
Hi theire,
could you have a look to that KB and trying out please.
Maybe a Permission Issue
thx
Max
HI, thanks for anserwing.
I've read that KB as well, and the user doing the upgrade has sysadmin over the database, so it seeams that that isent the issue here either.
Problem is now solved.
Read today that vmware released a new release, vcenter 6.0 update 1, build 3040890. After tying to install with that instead of build 2656757 it worked like a charm. No errors and no warings, worked right away.