I uninstalled Update Manager Client and then goto vCenter Plug-in click download Update Manager Client, but pop-up the following meesage:
The basic connection was closed: Received an unexpected error occurred
I re-installed Windows XP and then want to install VUM plug-in but shown "Cannot connect to remote server"
Fixed it with reinstall update manager.
We are currently on vmware vsphere 5.5. and recieved the following error when trying to enable the update manager plugin in plugin manager:
There was an error connecting to VMware vSphere Update Manager – [Server Name:443]. Database temporarily unavailable or has network problems.
No blog site or website was able to help me resolve this annoying problem which I had for 3 days and could not find a resolution. I tried everything every website suggested. I finally fixed the problem after digging further into the "vmware-vum-server-log4cpp.log" log file and determined that my Update Manager database VIM_UMDB transaction log file was full. It was set to 2048. To resolve the problem I changed it to 4096 and I finally got to enable the Update Manager plugin. Now I have to resolve the transaction log filling up. I have weekly jobs set to run, however, not sure went wrong. I am still investigating.
My SQL database resides on a separate server. There were no problems with the ODBC driver connectivity from the vCenter server to the remote SQL server or the update manager service user and password, changing these did nothing to help, the real problem was the transaction log filling up on the Update Manager database. Hope this bit of information helped.
Thanks a lot Hayden,
looking on log "vmware-vum-server-log4cpp.log" I find another kind of error and I resolve my problem using "VMwareUpdateManagerUtility"VCAP-DCV
I fixed it by running "VMware vSphere Update Manager Service" as a VPXUser (instead of Local account). User account who can access and modify VUM database.