Hi Guys,
I'm trying to install Update Manager for Virtual Center 2.5 for newly installed ESX 3.5 clusters and got the above errors and after looking at research, it seems to be a known issue but follow VMware KB didn't seems to work and I've used different types of login and still no luck. VUM install directly on VC server with SQL database backend and during the wizard specified local administrator account + database login credentials and has no luck.
I've seen a lot of this issues on the forum but tried the method still didn't work. Anyone has better suggestions that would be great! Thanks in advance!
If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!
Regards,
Stefan Nguyen
iGeek Systems Inc.
VMware, Citrix, Microsoft Consultant
Are you using non-standard ports? Can you connect to vc without problem? It almost sounds like there is something else listening on the standard vc ports.
-KjB
Believe it or not, we spent 12 hours on phone support with VMware and dealt with 3 different engineers on 2 different shift to resolve this problem. Anyways, to recap the problems and resolution.
1. We had problem finishing VMware Update Manager with error specified and has done pretty much a lot of steps but couldn't solved it for 9 straight hours.
2. We tested clean install virtual center server and components on a virtual machine and things works fine with SQL 2005 Express instead of DB created in SQL 2005 Enterprise.
3. We went back to original physical virtual center server and wipe out all VMware components and didn't work.
4. Eventually we wipe it clean and remove all registries, application data and temp folder and finally able to install Update Manager but problems with license server and always pop up weird message like "vim.Fault.NoHost" etc..
5. We spent time removed cluster, reconfigured HA, disconnect ESX hosts and didn't work always have same error message.
6. Finally 3rd VMware engineer took over for 3 hours and handled it with problems lies to some how license component cached somewhere screw in the systems and finally solved it.
7. Update Manager works fine and ESX clusters works normal and license server doesn't have any issue.
If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!
Regards,
Stefan Nguyen
iGeek Systems Inc.
VMware, Citrix, Microsoft Consultant
Are there any specific details on this? We are having exactly the same issues.
Thanks.
The post would only be useful if there was specific explanation of a working solution
Seeing that 2 of their own guys did not manage it does not bring lots of confidence onto the table
Seb
Guys, I found a solution to this problem. Follow this thread: http://communities.vmware.com/message/1588199#1588199. You will have to use ADSI Edit to make some changes. Hope this helps.