Knowledge Base
The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides

|
Enabling Update Manager fails with the error: database unavailable or has network problems (1015223)
Symptoms
- You cannot enable Update Manager
- If you try to enable Update Manager, you see the error:
There was an error connecting to VMware vCenter Update Manager <server name>:8084. Database temporarily unavailable or has network problems.
- The Update Manager plug-in can be installed but not enabled
- The vpxclient.log contains the error:
Loaded plugin from : C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Plugins\Update Manager 4.0\vimIntegrityClient.dll Extension.Key - com.vmware.vcIntegrity
[Update M:SoapTran] 2009-10-26 10:19:54.225 Invoke 1 Finish RetrieveVcIntegrityContent on VcIntegrity:Integrity.VcIntegrity [167.237.115.104:8084] - Serial:0.001, Server:000.021 [ERROR]
Vmomi.Fault.DatabaseError: Database temporarily unavailable or has network problems.
- The vmware-vum-server-log4cpp.log (located at C:\Documents and Settings\All Users\Application Data\VMware\Update Manager or C:\Users\All Users\VMware\VMware Update Manager\Logs) contains the error:
[2009-10-05 14:06:17:873 'Activation' 3296 ERROR] [activationValidator, 237] vim.fault.DatabaseError
[2009-10-05 14:06:17:873 'Activation' 3296 ERROR] [activationValidator, 244] No started
[2009-10-05 14:06:17:873 'Activation' 3296 INFO] [activationValidator, 249] Leave Validate. Failed
[2009-10-06 10:32:58:862 'VcIntegrity' 3416 ERROR] [vcIntegrity, 807] ODBC error: (IM002) - [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
[2009-10-05 14:06:17:873 'Activation' 3296 ERROR] [activationValidator, 244] No started
[2009-10-05 14:06:17:873 'Activation' 3296 INFO] [activationValidator, 249] Leave Validate. Failed
[2009-10-06 10:32:58:862 'VcIntegrity' 3416 ERROR] [vcIntegrity, 807] ODBC error: (IM002) - [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
Resolution
This issue may occur if:
- Update Manager is installed with a remote SQL 2005 or 2008 database using Windows Authentication and the Update Manager Service is set to log on as a Local System Account.
To resolve this issue, change the Update Manager Service to log on to the remote database as a Windows account with Administrator privileges:- Click Start > Run, type services.msc, and click OK.
- Right-click VMware Update Manager and click Properties.
- Click the Log on tab.
- Select This account, specify the Windows account along with the appropriate password, then click OK.
- Right-click VMware Update Manager and click Restart.
- The Update Manager configuration file contains an incorrect database entry or if DSN does not match the Update Manager configuration file.
To resolve this issue, ensure that the entries in the Update Manager configuration file match:- Open the vci-integrity.xml file (located in C:\Program Files\VMware\Infrastructure\Update Manager\vci-integrity.xml) in a text editor.
-
Locate the database parameters:
<database>
<dbtype>SQL Native Client</dbtype>
<dsn>VMware Update Manager</dsn>
<InitialConnections>20</initialConnections>
<maxConnections<40</maxConnections>
</database>
-
Verify that ODBC DSN and driver match the <dsn> and <dbtype> entries:
-
If the system is 32-bit, go to Administrative Tools > Data Sources ODBC > System DSN.
-
If the system is 64-bit, launch %SystemRoot%\syswow64\odbcad32.exe from Start > Run.
-
-
If the DSN does not exist, recreate it with the same entries as the vci-integrity.xml file and ensure to apply appropriate permissions to the database. For more information, see the ESX/ESXi and vCenter Server Installation Guides.
-
If you cannot enable the Update Manager Plug-in after changing the password for the Update Manager Database:
-
Changing the vCenter Update Manager database password (1034605) for Update Manger 4.1 Update 1 and above.
-
Cannot enable Update Manager Plug-in after changing database user password (1013508) for earlier verisons of Update Manager
-
-
After making any changes, restart the Update Manager Service and test the plug-in connectivity.
-
If you still get the error, it may be necessory to remove the Update Manager plug-in (by going to Add/Remove Programs), then reinstall it in the Plug-in Manager.
- Open the vci-integrity.xml file (located in C:\Program Files\VMware\Infrastructure\Update Manager\vci-integrity.xml) in a text editor.
Tags
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.
Actions
KB:
- Updated:
- Categories:
- Languages:
- Product Family:
- Product(s):
- Product Version(s):

