Troubleshooting a failed vCenter Server installation
search cancel

Troubleshooting a failed vCenter Server installation

book

Article ID: 302230

calendar_today

Updated On:

Products

VMware

Issue/Introduction

This article provides steps to troubleshoot a failed vCenter Server installation. The article helps you eliminate common causes for your problem.

Symptoms:
  • vCenter Server installation fails to complete
  • Unable to complete a vCenter Server installation
  • Installing vCenter Server fails
  • You may see one or more of these errors during vCenter Server installation:
    • Invalid Virtual Infrastructure Web Service https port number or TCP/IP port in use
    • Error 25036.VMware VirtualCenter Server could not be installed.
    • Error 25060. Setup failed to execute sqlcmd.exe
    • This installation package is not supported by this processor type. Contact your product vendor.
    • re-configure your DSN to use one of the supported drivers
    • An error occurred, please try again in another vSphere session.


Resolution

Validate that each troubleshooting step below is true for your environment. Each step will provide instructions or a link to a document, in order to eliminate possible causes and take corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Please do not skip a step.
  1. Verify that the minimum system requirements for vCenter Server have been met. For more information, see Supported host operating systems for VMware vCenter Server installation (2091273). If you are installing vCenter Update Manager as part of your installation, see Minimum system requirements for installing VMware vCenter Update Manager (1037494) and Minimum requirements for installing VMware vCenter Update Manager 5.0 (2005084).

  2. Verify that you have followed any specific instructions outlined in the release notes. For more information, see Known issues when installing or upgrading to vCenter Server 4.x and below (1003949) and Known
    issues when installing or upgrading to vCenter Server 5.x (2031082).

  3. Verify the problem is not being caused by the installation media. For more information, see Checking media integrity for VirtualCenter Installations and Upgrades (1003904) .

  4. Verify the ODBC Data Source is configured correctly. For more information, see vCenter Server installation fails with ODBC and DNS errors (1003928) .

  5. Verify the health of the Database server that is to be used for VirtualCenter. If the hard drives are out of space, the database transaction logs are full, or if the database is heavily fragmented VirtualCenter may complete the installation. For more information, see Investigating the health of a vCenter database server (1003979) .

  6. Verify that ports 902, 80, and 443 are not being used by any other application. If another application such as Microsoft Internet Information Server (IIS), is utilizing any of the ports VirtualCenter may fail to install. For more information on troubleshoot port conflict issues, see Port already in use when installing vCenter Server (4824652) .

  7. Verify that your database configuration is correct. For more information, see Troubleshooting vCenter Server database configuration issues (1003960) .

  8. Confirm that your virtual machine's anti-virus, anti-malware or IDS programs are not blocking or interfering with the install. Consult the manufacturer's documentation for instructions on disabling.
Note: If your problem still exists after trying the steps in this article:


Additional Information

Checking media integrity for vCenter Server installations and upgrades
Known issues when installing or upgrading to vCenter Server 4.x and below
Collecting diagnostic information for VMware products
Minimum requirements for installing vCenter Update Manager 5.x
How to file a Support Request in Customer Connect
Known issues when installing or upgrading to VMware vCenter Server 5.x
Supported host operating systems for VMware vCenter Server installation (including vCenter Update Manager and vRealize Orchestrator)

Powered by Wolken Software