Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

vCenter operation times out with the error: Operation failed since another task is in progress (1004790)

Purpose

The default time-outs in VMware Infrastructure (VI) Client may not be long enough for certain long operations, such as deleting snapshots. This article provides information on how to prevent these timeouts. 

Resolution

vCenter has a default 15 minute timeout for any task. Starting with the vCenter 2.5 Update 4 release, to prevent VI Client from displaying unnecessary timeout error messages, you can configure the timeout values by editing the vpxd.cfg file and the vpxa.cfg file of the source and destination ESX host.
 
Note: If you are using VCB, and your backup failed due to a timeout, check your virtual machine for a backup snapshot which has been left behind.

Lengthy Tasks which Time Out

When a task is reported to timeout within vCenter, the task may continue to run in the ESX host level. Certain tasks (such as a snapshot consolidation) may take a long time to complete and should not be interrupted. For information on how to identify tasks within a VMware ESX host, see Collecting information about tasks in VMware ESX (1013003).
 
Note: In the case of snapshot consolidation, even though the VI Client timeout occurs, the operation on the ESX host is still running. You can verify by observing the .vmdk file for the virtual machine. It is updated every minute which means the delta files are being committed to the .vmdk file.

vCenter Timeout Settings

To change the timeout value in the vCenter Server, update vpxd.cfg on vCenter and vpxa.cfg on the ESX: 
  1. Log into the vCenter Server with the appropriate permissions.
  2. Open the vpxd.cfg file in a text editor. The default location for the file is:

    C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\vpxd.cfg
  3. For Windows 7 and Windows 2008, the default location for the file is:

    C:\ProgramData\VMware\VMware VirtualCenter\vpxd.cfg
  4. To increase the timeout values for the virtual machine migration task, add the following timeout parameter in the vpxd.cfg file:

    <config>
    ..
    <task>
    <timeout>10800</timeout>
    </task>
    ..
    </config>

    Note: The value 10800 can be changed based on your requirements. This example uses 10800 seconds, or 3 hours.

  5. To increase the SOAP layer blocking call timeout, add the following values in the vpxd.cfg file:

    <config>
    ..
    <vmomi>
    <soapStubAdapter>
    <blockingTimeoutSeconds>10800</blockingTimeoutSeconds>
    </soapStubAdapter>
    </vmomi>
    ..
    </config>

    Note: The value 10800 can be changed based on your requirements. This example uses 10800 seconds, or 3 hours. This line may not be present in ESX 4.0.

  6. Restart the vCenter Server service. For more information, see Starting, stopping, and restarting vCenter services (1003895).

ESX or ESXi timeout settings

  1. Log in to the ESX host as root via the console or an SSH session. For more information, see Unable to connect to an ESX host using Secure Shell (SSH) (1003807). For information about ESXi, see Tech Support Mode for Emergency Support (1003677).
  2. Open the vpxa.cfg file in a text editor. The default location for the file is:

    /etc/opt/vmware/vpxa/vpxa.cfg

    Note: ESX and ESXi come with open source tools which can be used for troubleshooting. The nano editor can be used in ESX , while the vi editor can be used in ESX or ESXi.  For more information on these tools, see GNU nano and Vim.
     
  3. To increase the timeout values for the virtual machine migration task (both source and destination hosts), add the following timeout parameter in the vpxa.cfg file:

    <config>
    ..
    <task>
    <timeout>10800</timeout>
    </task>
    ..
    </config>

  4. To increase the SOAP layer blocking call timeout, add the following values in the vpxa.cfg file :

    <config>
    ..
    <vmomi>
    <soapStubAdapter>
    <blockingTimeoutSeconds>10800</blockingTimeoutSeconds>
    </soapStubAdapter>
    </vmomi>
    ..
    </config>

    Note: The value 10800 can be changed based on your requirements. This example uses 10800 seconds or 3 hours.

  5. Configure the timeout value for the time that VirtualCenter waits to capture the virtual machine's ID at ESX destination. Add a new configurable parameter in the vpxa.cfg file:

    <config>
    ..
    <vpxa>
    ..
    <vmotion>
    <vmIdAcquireTimeout>600</vmIdAcquireTimeout>
    </vmotion>
    ..
    </vpxa>
    ..
    </config>

    Note: The value 600 can be changed based on your requirements. This example uses 600 seconds or 10 minutes.
     
  6. Restart the vmware-vpxa service on the ESX host. For more information, see Restarting the Management agents on an ESX Server (1003490).

See Also

This Article Replaces

This article replaces KB 1002308, 1008906, 1008675, 1009670, 1010814

Update History

10/06/2011 - Added vCenter 4.X to the product list 10/06/2011 - Added additional step for path to vpxd.cfg for win7 and win 2008.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 17 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 17 Ratings
Actions
KB: