We just updated vCenter from 5.0 to 5.0 Update 2. Smooth.
I uninstalled VUM (running on a different server) and reinstalled it. Now, when I launch a client, I get a message saying "There was an error connecting to VMware vSphere Update Manager - [FQDN of vCenter:443]. Database temporarily unavailable or has network problems."
There's a release note here that says that the plug-in might not work after the update, and to check that you're using SQL Authentication for the ODBC connection from VUM to SQL. So, we fixed that and now the ODBC connection is working just fine.
I restarted the SQL server, all VirtualCenter services, and the Update Manager service/servers. No luck.
I've uninstalled the client and client plugin for VUM multiple times. No luck.
I've run the client and the VUM plugin from both vCenter and from the VUM server. No luck.
There is no firewall running on either server.
Both servers are in the same subnet.
What's confusing is that it gives the FQDN of the VirtualCenter server, as if that's what it's trying to connect to. i.e. It thinks that VUM is installed on our VirtualCenter server.
There is very little out there on this particular error, so if anyone has guidance on where to go from here, it would be appreciated.
Thanks,
Frank