Enabling the Update Manager plug-in fails with the error: database unavailable or has network problems
search cancel

Enabling the Update Manager plug-in fails with the error: database unavailable or has network problems

book

Article ID: 338377

calendar_today

Updated On:

Products

VMware vCenter Server VMware vSphere ESXi

Issue/Introduction

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.

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
  • In 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. 　
     
     


Environment

VMware vSphere Update Manager 5.5.x
VMware vCenter Update Manager 4.0.x
VMware vCenter Update Manager 5.1.x
VMware vCenter Update Manager 1.0.x
VMware vCenter Update Manager 6.0.x
VMware vCenter Update Manager 5.0.x
VMware vCenter Update Manager 4.1.x

Cause

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.

Resolution

To resolve this issue, perform one of these options:

  1. Click Start > Run, type services.msc, and click OK.
  2. Right-click VMware Update Manager and click Properties.
  3. Click the Log on tab.
  4. Select This account, specify the Windows account along with the appropriate password, then click OK.
  5. 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:
     
    1. Open the vci-integrity.xml file (located at C:\Program Files (x86)\VMware\Infrastructure\Update Manager\vci-integrity.xml) using a text editor.
    2. Locate the database parameters:

      <database>
      <dbtype>SQL Native Client</dbtype>
      <dsn>VMware Update Manager</dsn>
      <InitialConnections>20</initialConnections>
      <maxConnections>40</maxConnections>
      </database>
       
    3. 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.
         
    4. 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.
    5. If you cannot enable the Update Manager plug-in after changing the password for the Update Manager database, see:
    6. 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.


Additional Information

TCP and UDP Ports required to access VMware vCenter Server, VMware ESXi and ESX hosts, and other network components
Enabling VMware vCenter Update Manager 1.0/4.0 fails with multiple errors
Changing the vCenter Update Manager database password
データベースユーザーのパスワードを変更後、Update Manager のプラグイン有効化に失敗する
启用 Update Manager 插件失败并显示错误：数据库不可用或网络有问题
Update Manager プラグインの有効化がエラー「データベースが使用可能でないかネットワークに問題があります」で失敗する

Powered by Wolken Software