Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
You cannot enable Update ManagerIf 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 enabledIn the vpxclient.log file, you see entries similar to: 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] YYYY-MM-DD TIME.225 Invoke 1 Finish RetrieveVcIntegrityContent on VcIntegrity:Integrity.VcIntegrity [1xx.2xx.1xx.1xx:8084] - Serial:0.001, Server:000.021 [ERROR] Vmomi.Fault.DatabaseError: Database temporarily unavailable or has network problems. In the C:\Documents and Settings\All Users\Application Data\VMware\Update Manager\vmware-vum-server-log4cpp.log file or C:\Users\All Users\VMware\VMware Update Manager\Logs\ vmware-vum-server-log4cpp.log file, you see entries similar to: [<YYYY-MM-DD>T<time>:873 'Activation' 3296 ERROR] [activationValidator, 237] vim.fault.DatabaseError [<YYYY-MM-DD>T<time>:873 'Activation' 3296 ERROR] [activationValidator, 244] No started [<YYYY-MM-DD>T<time>:873 'Activation' 3296 INFO] [activationValidator, 249] Leave Validate. Failed [<YYYY-MM-DD>T<time>:862 'VcIntegrity' 3416 ERROR] [vcIntegrity, 807] ODBC error: (IM002) - [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified </time></time></time></time>Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
This article provides various options to resolve the issue when enabling the Update Manager plug-in fails with the database unavailable or has network problems error.
This issue occurs if: Update Manager is installed with a remote SQL 2005, 2008 or 2012 database using Windows Authentication and the Update Manager Service is set to log in as a Local System Account.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, perform one of these options: Confirm connectivity between Update Manager and the SQL database. Verify that network connectivity exists between the Update Manager server and the vSphere Client in which you want to enable the plugin. For more information, see Cannot connect to the remote server when downloading the vCenter Update Manager or Converter plugins (1004887).Confirm that all required ports between vCenter Server and the Update Manager server are open and are accessible. For more information, see TCP and UDP Ports required to access VMware vCenter Server, VMware ESXi and ESX hosts, and other network components (1012382).Ensure that name resolution works correctly between all machines accessing the vSphere Client and your vCenter/Update Manager server. For more information, see Identifying issues with and setting up name resolution on ESX/ESXi Server (1003735). Update Manager is installed with a remote SQL 2005, 2008 or 2012 database using Windows Authentication and the Update Manager Service is set to log in as a Local System Account. To resolve this issue, change the Update Manager Service to log in 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 at C:\Program Files (x86)\VMware\Infrastructure\Update Manager\vci-integrity.xml) using 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 Note: Spaces in these entries matter, when comparing the vci-integrity.xml file to the ODBC DSN ensure they are identical down to the spaces. 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, see: Update Manager 4.1 Update 1 and later versions – Changing the vCenter Update Manager database password (1034605) Update Manager 4.1 and earlier versions – Cannot enable Update Manager Plug-in after changing database user password (1013508) After making any changes, restart the Update Manager Service and test the plug-in connectivity. If you still get the error, it may be necessary to remove the Update Manager plug-in (by going to Add/Remove Programs), then reinstall it in the Plug-in Manager.
TCP and UDP Ports required to access VMware vCenter Server, VMware ESXi and ESX hosts, and other network componentsEnabling VMware vCenter Update Manager 1.0/4.0 fails with multiple errorsChanging the vCenter Update Manager database passwordデータベースユーザーのパスワードを変更後、Update Manager のプラグイン有効化に失敗する启用 Update Manager 插件失败并显示错误：数据库不可用或网络有问题Update Manager プラグインの有効化がエラー「データベースが使用可能でないかネットワークに問題があります」で失敗する