Update Manager - Error connecting to VMware vCenter Update Manager - Database temporarily unavailable or has network problems.

[John_S1]

I have uninstalled and reinstalled, I've triple checked that I can log on to the VCenter server using the Update Manager account that is DB Owner on the Update Manager database. I can connect to SQL using the ODBC SQL 2008 native client under that same account. But we get the same error from multiple machines when we install and run the VCenter plugin.

Any Ideas?

[nickmtc]

Hello, Thank You, I have reinstalled Update Manager and all works ok, (I don't see this error anymore)

[dericvenra]

I am not sure if anyone still needs this information but incase anyone else comes across this page in search for answers the way I solved it was to update the 32bit OBDC DSN. This is what the update manager plugin uses and not the 64bit ODBC DSN.

All one needs to do is run C:\windows\SysWOW64\odbcad32.exe and verify the DSN works and connects.

[Dip999]

I think I may have found a better solution, well it seemed to work for me.

I went to the VMWare Update manager SQL instance, and added my VCenter Server machine name$ as a db owner. ie. domain\VCCServer$ as a dbowner for the VMWare Update Manager database. This did the trick.

I noticed in the log files that the machine name needed access..

\Application Data\VMware\VMware Update Manager\Logs:

[2012-01-23 08:08:13:033 'VcIntegrity' 8876 ERROR]  [vcIntegrity, 829] Error initializing database: ODBC error: (28000) - [Microsoft][SQL Server Native Client 10.0][SQL Server]Login failed for user 'CORP\MACH$'.

[2012-01-23 08:08:13:033 'VcIntegrity' 8876 ERROR]  [vcIntegrity, 767] vim.fault.DatabaseError

Hope this helps!

[vmwaredownload]

Make sure you are using 32bit ODBC connection. If you are, and testing the connection of ODBC works then you may have an issue with DNS resolution.

[jfh777]

Thanks, Dip999!  That worked perfectly for me.  One million points for you!

Justin

[Cyberfed27]

I was having the same exact issues as you guys. It happened after we installed vCenter on a new server.

I was getting the same ODBC DOMAIN\COMPUTERNAME$ logon failures.

All my ODBC connection tests were working fine.

Here's why:

On our old vCenter server VUM was using a service account to run, that service account had the correct permissions in the VUM DB.

When another admin installed the new vCenter server + VUM he had set VUM to run as local system. Hence it was trying to authenticate to the SQL DB as DOMAIN\COMPUTERNAME$.

The SQL server of course did not have the permissions set for the computer object to interact with the DB.

I changed the VUM service to use the service account instead of local system. Restarted the services and sure enough update manager began to work.

In short, whatever account the VUM windows service is running as needs to have rights on the VUM DB.