vCAC 6.0 most annoying installation error
During my POC on vCAC I had to struggle with different type of issues but he most annoying one was during IaaS component installation. I don’t know how many times I performed IaaS components installation however I fount at least 4 reasons why IaaS installation failed.
Cause #1
Outdated build of Windows server – some of the Windows OS patches were missing on my IaaS Windows VM – before deploying vCAC IaaS services apply all latest security patches (recommended and optional) to Windows box
Reason #2
Installed .Net 4.5 SP1 – DO NOT install SP1 for .NET4.5 on Windows IaaS server – it might happen during Windows updates (exclude .NET4.5.1 from patches installation list), .NET4.5 is the only one supported with vCAC 6.0 and vCAC 6.1
Reason #3
Lack of communication between vCloud Automation Center Appliance and vCloud Automation Server (Windows IaaS box) – make sure that there is a required communication available between all vCAC components
Reason #4
When I used vCenter SSO instead of vCloud Identity Appliance – even though vCenter SSO in version 5.5b is officially supported as and SSO endpoint for vCloud Automation Center services it might happen from time to time that you might experience some unexpected problems. I spoke with VMware engineers and with support and they said that safer is to use vCloud Identity Appliance than vCenter server SSO.
MANAGERSERVICE_HOSTNAME="vca02.lab.local" Execution time:49.36 Executing:"C:\Users\AP-VCL~1\AppData\Local\Temp\2\vCAC\Msi\vCAC-Wapi-Setup.exe" /s /w /V"/qn ADDLOCAL=All" Execution time:6.875 Executing:"C:\Program Files (x86)\VMware\vCAC\Web API\ConfigTool\Wapi-Config.exe" /S "/P:C:\Users\AP-VCL~1\AppData\Local\Temp\2\vCAC\Msi\ConfigToolProperties.WAPI-ConfigTool.xml" Execution time:5.859 Failed to register catalog types. Error message Executing:C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\Cafe\Vcac-Config.exe RegisterCatalogTypes -v System.AggregateException: One or more errors occurred. ---> System.Threading.Tasks.TaskCanceledException: A task was canceled. --- End of inner exception stack trace --- at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken) at VMware.Cafe.Client.Registration.RegisterWithServiceCatalog() at VMware.VcacConfig.ServiceCatalogCommands.RegisterCatalogTypes.Execute(CommandLineParser parser) ---> (Inner Exception #0) System.Threading.Tasks.TaskCanceledException: A task was canceled.<--- Warning: Non-zero return code. Command failed.
Yet another error, not directly related to above but worth to mention. Below you can see that vCloud Automation Center Appliance can’t reach out vCenter Orchestrator. What had happen, in order to perform online upgrade of vCAC appliance proxy server was set, after successful update of the vCAC services proxy settings wasn’t removed so, when I’ve tried to add vCenter Orchestrator as an vCAC endpoint – it always failed saying Can’t connect to vCO url. I didn’t know how to handle it so I SSH’ed to vCAC appliance VM and tried to do wget and guess what ? http request was sent through web proxy server. What you have to do it disable proxy in vCAC appliance WebUI and remove proxy settings from appliance configuration file.
[box type=”warning”] Note: if your proxy requires authentication password, it is stored in open text in the appliance (SLES 11) configuration file.[/box]
vca01:~ # wget vco01.lab.local --2014-02-24 10:55:04-- http://vco01.lab.local/ Resolving proxy.lab.local... 192.168.137.55 Connecting to proxy.lab.local|192.168.137.55|:8080... connected. Proxy request sent, awaiting response... 403 Forbidden 2014-02-24 10:55:04 ERROR 403: Forbidden.
