Error Connecting to VMware vCenter Update Manager

I got the following error message when I logged to the vSphere Client.

There was an error connecting to VMware vCenter Update Manager -
[servername:443]./
Database temporarily unavailable or has network problems.

I checked the “VMware vCenter Update Manager Service” and it started.  I also verified that the database is intact.

So I went into the “Plug-in Manager” and tried to enable the “VMware vCenter Update Manager Extension” but was threw with another error message.

There was an error connecting to VMware vCenter Update Manager -
[servername:443]./
:Vmomi.Fault.NotAuthenticted : The session is not authenticated.

I took a look at the vmware-vum-server-log4cpp.log located in “ProgramData\VMware\VMware Update Manager\Logs”.  For Windows Server 2003, the log will be in “C:\Documents and Settings\All Users\Application Data\VMware\VMware Update Manager\Logs”.

The following error messages were found in the log.

[2012-01-26 08:04:32:783 'lib.vdb.vdbStatement' 2596 INFO]  [440] SQL execution failed: SELECT version_id, version_string, db_schema_version_id FROM VCI_VERSION
[2012-01-26 08:04:32:783 'lib.vdb.vdbStatement' 2596 INFO]  [441] Bind parameters:
[2012-01-26 08:04:32:784 'VcIntegrity' 2596 ERROR]  [vcIntegrity, 794] "ODBC error: (08S01) - [Microsoft][SQL Server Native Client 10.0]TCP Provider: An existing connection was forcibly closed by the remote host." is returned when executing SQL statement "SELECT version_id, version_string, db_schema_version_id FROM VCI_VERSION"
[2012-01-26 08:04:32:785 'Activation' 2596 ERROR]  [activationValidator, 245] vim.fault.DatabaseError
[2012-01-26 08:04:32:785 'Activation' 2596 ERROR]  [activationValidator, 253] No started
[2012-01-26 08:04:32:786 'Activation' 2596 INFO]  [activationValidator, 258] Leave Validate. Failed

Following the KB Article, Enabling Update Manager fails with the error: database unavailable or has network problems, I verified that the service account, vci-integrity.xml and ODBC settings are all correct.  I tried to re-enable the “VMware vCenter Update Manager Extension” but still got the same error.

Trying my luck, I restarted the “VMware vCenter Update Manager Service” and was able to enable the “VMware vCenter Update Manager Extension” without any error.

I suspect the “VMware vCenter Update Manager Service” was still “holding” on to an invalid bad session since the server hosting the database was rebooted unexpectedly last night.