Hi,
I finally joined this forum and wanted to reply to Gary's post. Thank you, thank you, thank you! Following your post about altering the startup order of the services solved my problem!
Yesterday I completed my lab setup of upgrading vcenter 5.0 to vcenter 5.1, thought i had it successfully complete, then rebooted and BAM, not able to login to vCenter and SSO was reporting that it could no longer connect to my 1 vCenter instance. But how, why??? This all worked before I rebooted!!!
In my own testing I then uninstalled just vCenter server and then reinstalled, VOILA, vCenter is working again, then rebooted and BAM, same problem, vCenter could not be logged into. I uninstalled and reinstall vCenter again, working fine again, rebooted, gone, not working.
Then I found Gary's post and followed it. Without uninstalling this time, i simply changed the order that the service start in, as Gary mentioned, then rebooted my vCenter server and HOORAY, vCenter and SSO work like a charm. The only problem I had after this was the Update Manager stopped working, I could not enable this pluggin without error in the vSphere client. I then uninstalled Update Manger, reinstalled Update Manger, fired up the vSphere client, connected to vCenter and the Update Manager worked properly, it was now enabled without error.
About my lab environment..
- I upgraded a 2008R2 server that had vCenter 5.0 on it.
- My SQL databases for vCenter, SSO and Update Manager are on a standalone 2008 R2, SQL 2008 standard server.
- I am using Active Directory (so I believe this problem affects more than just non AD users)
- My lab has a primary and secondary Domain Controllers
- DNS is configured properly forward and reverse
- i did not perfom a Simple Install of 5.1, i installed SSO, Inventory Service, vCenter Server, vSphere Client and then Update Manager, in that order.
If I were to comment on this upgrade in general, i must say it has been quite clunky. I have had to fight with this upgrade every step of the way. Changing the start order of services???? That's not a problem I would expect from VMWARE. Considering all my previous upgrades were a piece of cake. I'm very hesitant to put this upgrade into our produciton enviroment. The only thing driving me to do this is the fact that vShield is now included without an addtional license cost. If vshield wasn't motivating me to make this upgrade then I would likely pass for now, until a new upgrade came out with a standard best practise for install.
Thanks again,
Will