Task management is an important part of vSphere API. It enables asynchronous calls by returning a Task back before the work is actually done at the server side. If a task takes too long (for example, more than 15 minutes to create a virtualmachine snapshot from VirtualCenter), however, it can time out before it finishes. It means you lose tracking of the task.
You can easily fix this issue by changing the configurations. On the ESX server, add the following to the /etc/opt/vmware/vpxa/vpxa.cfg file:
Bothered by SLOW Web UI to manage vSphere? Want to manage ALL your VMware vCenters, AWS, Azure, Openstack, container behind a SINGLE pane of glass? Want to search, analyze, report, visualize VMs, hosts, networks, datastores, events as easily as Google the Web? Find out more about vSearch 3.0: the search engine for all your private and public clouds.
<task> <timeout>7200</timeout> </task>
<vmomi> <soapStubAdapter> <blockingTimeoutSeconds>7200</blockingTimeoutSeconds> </soapStubAdapter> </vmomi>
Remember to restart the service:
$ service vmware-vpxa restart
On the VirtualCenter server, add the following to the C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\vpxd.cfg file:
<task> <timeout>7200</timeout> </task> <vmomi> <soapStubAdapter> <blockingTimeoutSeconds>7200</blockingTimeoutSeconds> </soapStubAdapter> </vmomi>
After you save the configuration file, don’t forget to restart the VMwareVirtualCenter Server service from the Control Panel. The change increases the timeout to 2 hours, and you can increase it asneeded.