A few days ago i was asked to look into a failed vCloud Automation Center (vCAC) installation. The failing part was the Windows Server based vCAC Infrastructure as a Service component.
I didn’t have access to the installation log file, which is normally saved in the vCAC IaaS virtual machine directory C:Program Files (x86)VMwarevCACServerConfigToolLog, so i really don’t know what caused the installation failure.
All vCAC IaaS components were to be installed on the same virtual machine. The database was to be created during the installation process on a remote virtual machine.
Below are the steps i took without actually knowing during what section the previous installation failed.
- vCAC IaaS virtual machine
- Removed the vCAC installation directory “C:Program Files (x86)VMware”
- Removed the Internet Information Services (IIS) Application Pool RepositoryAppPool via the IIS Manager. The vCACAppPool and WAPIAppPool Application Pools Directories were not present but you’ll need to remove these as well if the exists.
- Removed the IIS Virtual Directory from the IIS Default Web Site via the IIS Manager. The vCAC and WAPI Virtual Directories were not present but you’ll need to remove these as well if the exists.
- Removed the Default Web Site https/443 port binding.
- MSSQL virtual machine
- Removed the database created during the first installation attempt
After performing the above actions the customer could successfully install the vCAC IaaS components.
You might have to take additional steps depending on type of vCAC IaaS failure.
1 pings