What version of vcenter are you running?
This is all vcenter 4. This is a new update manager database. The rest of vcenter 4 is fully installed and functional.
Please check if the name is getting Upgrade Manager system name is getting resolved properly. Normally this issues will pop up when there is problem accessing host which actually even error message is pointing out.
Other option you can try is while installing use IP address instead of hostname.
Let us know if this solves your issue.
1 person found this helpful
Which version of SQL 2008 do you have?
Not all version are supported for VUM DB, see page 12 of: https://www.vmware.com/pdf/vsphere4/r40/vsp_compatibility_matrix.pdf
**if you found this or any other answer useful please consider allocating points for helpful or correct answers
Could you please try the following:
1. Check Status of Update Manager Service. If it is not running,
start it and then try enabling the plug-in.
2. If the proxy is enabled without the option
to bypass the local addresses, enable that setting in IE, restart VIClient and
try enabling Update Manager.
3. Try restarting the Update Manager and DB services.
Also, if you could send us the logs, it would be really helpful.
If you use Windows Authentication to login to the database you've to change the user with which the Update Manager service start on the virtual center. You've to put the username/password of the user that can connect to the database (by default Update Manager start with Local System account. When installing if the vCenter Server is on Windows 2008 I think you should also use the FQDN of the vCenter server (or the ip address) to be sure it get the right address (something to do with IPv6 on Windows 2008) . At least this worked for me.
We are actually using SQL 2008 Standard 64 bit - which oddly enough is not supported? Can't quite understand why since that version is supported for vcenter. And SQL 2005 standard was supported for update mananger.
It does seem to work with SQL 2008 Std 64bit though. Once we changed the service to use the domain account (See post below). That's not noted anywhere I could find.
Thanks, that was it (Changing the Service Account)! And the fix is something I should have tried I didn;t see any mention of it in the install guide though and I didn't make note of how the previous version was set. Since vcenter itself changes the service, you think update mananger would as well. Go figure. Thanks again!
BTW, Update Manager on SQL 2008 Standard 64bit seems to work just fine, even though it appears it is not supported.
This fixed my problem. New to using Windows Authentication with VMware... I used the same DB User account to install VUM as I did VC...
But the installer didn't set the Service Account Settings. Resetting the Service Account Settings fixed the problem...
Author of the SRM Book: http://www.lulu.com/content/4343147
Switching the logon account for the Update Manager service from Local System to the AD account we're using for the VUM DSN did NOT address the issue we are having here. The service will not start....we get an error that the service Terminated Unexepectedly. This is the same AD account that the VCenter service is set to log on with.
We worked with vmware support for several hours and got nowhere. Their next suggestion is to try switching to SQL Auth for the DSN for Update Manager and reinstall Update Manager We're going to try that now, but it's not the ideal solution.
We uninstalled Update Manager, reconfigured the DSN to use SQL Auth, reinstalled Update Manager, reinstalled the PlugIn and everything is working fine now. This was not an ideal solution, but we're living with it for now for the sake of progress.
I am having the same problem (I think).
I am upgrading to vSphere 4.
We are using a remote DB for vCenter and Update Manager that is SQL Server 2005.
I have upgraded the vCenter to 4.0 and installed the new 4.0 client.
I also installed Converter Enterprise 4.0 and enabled the plugin.
I created a new DSN connection to our SQL Server 2005 DB using SQL Native Client driver that
matched the old Upd Mgr connection that used the SQL Server driver. The test connect works to the SQL Server 2005 DB connecting with Windows NT authentication using the network login ID.
I installed Update Manager 4.0 from the CD and the service is running.
When I go to install Update Manager the plug-in in vCenter, I get an error –
There was an error connection to VMware vCenter Update Manager 172.xx.xx.xx:8084 Database temporarily unavailable or network problems.
This is the same SQL Server database that vCetner is using and the DSNs are configured the same.
It appears during the plug-in installation, Update Manager is trying to connect to the SQL Server DB but fails..
I have tried uninstalling Update Manager and client and reinstalling.
When I reconfigured the DSN to use SQL Authentication, I entered the SQL Server DB User and the password.
The test connect works. I saved it. But, if I go back and do a reconfigure, the password field is blank, so I am not sure what is going on.
Any ides what may be happening or a suggestion to try?
I have been on client site and ran into this similar issue. Like most, I attempted all things stated here without resolution. The fix was shortly determined to be ensuring the service account's (AD User) default database was set to the Update Manager database within SQL. I did NOT need to change the Update Manager service to run under the service account's ID. Setting the service account to run under the service account only made the service fail to start.
It should probably be noted that after I made the SQL changes I did remove and reinstall Update Manager along with resetup the DSN. During the reinstall of Update Manager, I utilized the service account ID/PW during the entire install process.
Good luck and hope this helps everyone going forward!
Same issue as Ron. I either get the service started with the builtin SYSTEM user and a database login failure message using NT/anonymous or I change the service to start with the db owner account (which is how it was working with 2.5 u4) and the service won't start. SQL Auth is not an option for our shop. The logs i believe are just showing a crash and dump when the service fails to start correctly.