Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

My Subscriptions

Loading

Knowledge Base

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

Last Updated: 3/20/2024Categories: How toTotal Views: 144972Language:
Chinese (Simplified)Portuguese (European)JapaneseSpanishEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

vCenter Server tasks time out or stop responding.

If you are using VMware Consolidated Backup (VCB), the backup fails, but snapshots are left behind.

Long warm or cold migrations time out.

If the task runs for more than 15 minutes, vCenter Server forces it to time out, but the task continues the execution on ESXi/ESX host.

Next attempt to re-run the task returns the error:

Operation failed since another task is in progress

Unable to delete snapshot.

vCenter Server times out when deleting snapshots.

Snapshots growing indefinitely.

If an alarm is configured to send an email, you see the message:

Alarm Host connection state on esx.example.com sent e-mail to [email-masked]

Operations that rely on vCenter Server connectivity, such as vMotion, Storage vMotion, VMware Site Recovery Manager, and VCB, fail.

Lengthy VMware Update Manager tasks have also been known to time out.

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 Server has a default 15 minute timeout for any task. Starting with the vCenter 2.5 Update 4 release, to prevent vSphere 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 ESXi/ESX host.

Note: If you are using VCB and your backup failed due to a timeout, check your virtual machine for a backup snapshot that 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 ESXi/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 ESXi/ESX host, see Collecting information about tasks in VMware ESXi/ESX (1013003).

Note: In the case of snapshot consolidation, even though the vSphere Client timeout occurs, the operation on the ESXi/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 Server Timeout Settings
To change the timeout value in the vCenter Server, update vpxd.cfg on vCenter and vpxa.cfg on the ESXi/ESX:

Log in to the vCenter Server with the appropriate permissions.

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

For Windows 7 and Windows 2008, the default location for the file is:

C:\ProgramData\VMware\VMware VirtualCenter\vpxd.cfg

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.

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.

Restart the vCenter Server service. For more information, see Stopping, starting, or restarting vCenter services (1003895).

ESXi/ESX timeout settings

Log in to the ESXi/ESX host as root via the console or an SSH session. For more information about ESX, 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).

Open the vpxa.cfg file in a text editor.

By default, this file is located at:

ESX - /etc/opt/vmware/vpxa/vpxa.cfg

ESXi - /etc/vmware/vpxa/vpxa.cfg

Note: ESXi and ESX hosts 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 ESXi or ESX. For more information on these tools, see GNU nano and Vim.

Note: The preceding links were correct as of May 5, 2015. If you find a link is broken, provide feedback and a VMware employee will update the link.

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>

To increase the SOAP layer blocking call timeout, add these 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.

Configure the timeout value for the time that vCenter Server waits to capture the virtual machine's ID at ESX/ESXi 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.

Restart the vmware-vpxa service on the ESXi/ESX host. For more information, see Restarting the Management agents on an ESXi or ESX host (1003490).

Related Information

Restarting the Management agents in ESXi
Tech Support Mode for Emergency Support
Unable to connect to an ESX host using Secure Shell (SSH)
How to stop, start, or restart vCenter Server services
Collecting information about tasks in VMware ESXi/ESX
A operação do vCenter atinge o tempo limite com o erro: Operação falhou porque há outra tarefa em execução
Culmina el tiempo de espera para la operación de vCenter y aparece el error: Error en la operación porque hay otra tarea en progreso
vCenter 操作超时并出现错误： 由于正在处理另一个任务，操作失败
vCenter の操作が次のエラーでタイムアウトする： 別のタスクが進行中のため操作に失敗しました

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)Portuguese (European)JapaneseSpanishEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
vMA および vCLI による個々の仮想マシン ディスクのクローン作成 (1027872)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware VirtualCenter

VMware vCenter Server

VMware ESX Server

Related Versions:

VMware vSphere ESXi 5.5

VMware vSphere ESXi 5.1

VMware vSphere ESXi 5.0

VMware VirtualCenter 2.5.x

VMware vCenter Server 5.5.x

VMware vCenter Server 5.1.x

VMware vCenter Server 5.0.x

VMware vCenter Server 4.1.x

VMware vCenter Server 4.0.x

VMware ESXi 3.5.x Installable

VMware ESXi 3.5.x Embedded

VMware ESX Server 3.5.x

VMware ESX Server 3.0.x

VMware ESX 4.0.x

view all

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant