I came across the following problem a couple of times:
In VirtualCenter, when trying to delete a virtual machine that is switched off, VirtualCenter comes up with:
"Operation failed since another task is in progress"
Also, when trying to use the vmware-cmd command to START, STOP, RESET, SUSPEND or UNREGISTER on the Virtual Machine, the ESX Server responds with:
VMControl error -999: Unknown error: SoapError: ServerFaultCode(1520) : (vim.fault.TaskInProgress)
Yet, when issuing the vmware-cmd
The following solution has always fixed the problem for me:
Just execute the following command on the ESX Server:
service mgmt-vmware restart
- No Host Reboot or Downtime Required
- No Virtual Machine Downtime Required
Ok, so we've looked at installing VMware ESX 3.5 on the ML110 G5. Now it's time to look at installing ESXi 3.5 Installable on the HP Proliant ML110 G5.
This should all work well, providing that you have the correct storage controller settings specified in the BIOS setup of the server.
To install ESXi 3.5 on the ML110 G5, follow these easy steps:
As of VMware VirtualCenter 2.5 Update 1, ESX Server 3i systems can only be added to an HA cluster if the system has swap enabled.
This article applies to:
- VMware ESXi 3.5.x Embedded
- VMware ESXi 3.5.x Installable
- VMware VirtualCenter 2.5.x
ESX 3i Servers with swap not enabled will show the following message(s):
An error occured during configuration of the HA agent of the host.
HA Agent has an error : Host in HA cluster must have userworld swap enabled.
To enable swap on the ESX 3i Server:
We know now that VMware ESX Server 3.5 works well with the HP Proliant ML110 G5. So, I thought I'd try running it on the HP Proliant ML115 G5. This however did not go as well a I thought it would.The integrated NIC in both the ML110 and ML115 is not supported, that I knew, so I installed an Intel Pro1000 GT NIC in the ML115. This card is supported so I was able to install VMware ESX 3.5 on the ML115 with no problems at all.
However, when the server booted up and started loading the VMKernel modules... that was where it all went horribly wrong. The server could not mount the root partition!!! Read on, because there is a fix to this problem.
Those of us who have tried running Veeam FastSCP on 64-bit Windows found that it installs perfectly, but once you try and run the application, it comes up with an error. Someting like "Unable tp connect to (local\VEEAM)".
It's sad to say, but Veeam FastSCP does not support 64-bit operating systems at this moment in time. However I found a little workaround that will allow you to use the application on 64-bit Windows, at your own risk and unsupported it has to be said.
So here's how:
1. Download the Microsoft .NET Framework 2.0 SDK (THE 64-BIT VERSION!) from the Microsoft Website. This download is about 300MB if I remember correctly.
2. Install the SDK on the 64-bit machine that you would like to run Veeam FastSCP on.
3. Now, open a command prompt (Start -> Run -> Type "cmd" -> OK)
4. Change directory to: C:\Program Files\Microsoft.NET\SDK\v2.0 64bit\Bin
5. Now Run: corflags "C:\Program Files (x86)\Veeam\Veeam Backup and FastSCP\VeeamShell.exe" /32BIT+
6. Now when you try and run Veeam FastSCP again, it should work fine.
Just a quick guide to patching a standalone ESX 3.5 Server using esxupdate from the service console:
Download all available patches to your local computer from the following link: (ALSO DOWNLOAD THE FILE CALLED contents.zip)
Decide where to place the patches in a partition with enough space to accommodate the patches on the target ESX Server. It is not recommended to use the root ( / ) partition at all. A good strategy is to create a directory called updates under the /var partition.