Cannot Delete a Virtual Machine(Another task is already in progress)

KB ID 0000376 

Problem

When you try and delete a Virtual Machine from ESX or VSphere you see the following error.

Error: Another task is already in progress.

In addition, if you try and remove the VM from the inventory you will see the following error.

Error: Call “VirtualMachine.Unregister” for object “{vm name}” on vCenter Server “{VCenter name}” failed.

 

Solution

In my case the VM in question was in the middle of a hardware upgrade (from version 4 to Version 7) that had failed/stalled.

Select the VM in question then open its summary tab. Simply cancel the the stalled upgrade and click OK.

You can now remove the VM as normal.

 

Related Articles, References, Credits, or External Links

NA

Using Openfiler and vSphere ESX / ESXi 5

KB ID 0000380

Problem

Openfiler is a free NAS / SAN prebuilt Linux distribution, that can provide iSCSI storage to your VMware environment, it’s ideal for small setups (This video was made with all the devices running in VMware workstation 7, on my laptop. That’s two ESXi servers, a vCenter server, and the Openfiler iSCSI target server).

Solution

Related Articles, References, Credits, or External Links

Openfiler Thanks to VMware for the free copy of VMware Workstation.

 

Backup Exec – Error “0xe0009585 – Unable to open a disk of the virtual machine”

KB ID 0000349 

Problem

Seen while using Backup Exec 2010 R2, while attempting to backup an Exchange 2010 server (on Windows server 2008 R2) in a VMware virtualised environment (using the VMware Backup Exec Agent).

Click for Larger Image

Errors Read

Job Completion Status

Completed status: Failed
Final error: 0xe0009585 – Unable to open a disk of the virtual machine.
Final error category: Resource Errors

Errors

Backup- VMVCB::”Virtual infrastructure”
V-79-57344-38277 – Unable to open a disk of the virtual machine.

VixDiskLib_Open() reported the error: You do not have access rights to this file
V-79-57344-38277 – Unable to open a disk of the virtual machine.

VixDiskLib_Open() reported the error: You do not have access rights to this file

Solution

This involves two reboots of the target machine start planning downtime, or warning your users.

1. Go to the Virtual Machine that you are trying to backup (in my case the Exchange server)

2. Start > run > appwiz.cpl > Locate and uninstall the VMware tools > when prompted to > reboot.

3. Reinstall the VMware tools but this time choose “CUSTOM INSTALL” > Locate the “Volume shadow Copy Service”.

4. Change the drop down so that this option will not be installed > complete the VMware tools installation and reboot when prompted.

 

Related Articles, References, Credits, or External Links

NA

Is Exchange 2010 Supported on VMware?

KB ID 0000333 

Problem

At time of writing (30/09/10) it seems I cant get a definitive answer! My colleague tried to log a third line support call with Microsoft this week, as soon as they found out that Exchange 2010 was running in a VMware environment, they (literally) hung up on him.

Solution

Well Microsoft’s own documentation says it IS

Reference:

Fair enough Exchange 2010 is supported on a “Third party Hypervisor ONLY if its been validated in the “Windows Server Virtualization Validation Program“”.

Lets check that then,

Reference:

Quote ” Products that have passed the SVVP requirements for Windows Server 2008 R2 are considered supported on Windows Server 2008 and Windows Server 2003 SP2 and later Service Packs, both x86 (32-bit), and x64 (64-bit).”

And The platform it was running on IS listed (ESXi 4.0 U1).

When presented with this evidence the response was “We will try and fix it on a “Best Endeavour” basis” and the problem (which had nothing to do with VMware, it was actually Microsoft Threat Management Gateway that caused the problem!) was resolved.

Sorry Microsoft that is just not good enough! My company pay handsomely for their gold partnership status, and we expect to get third line support on the products we sell. The product is either supported or it is NOT, don’t publish that it is, then use the fact that is running on third party virtualisation to get the problem off your support call queue. Because somewhere there is an Engineer/Consultant who has persuaded THEIR client to part with money to buy YOUR product.

I openly invite Microsoft – Third Line Exchange Support, The Exchange Development team and anyone else to respond to me. I will publish any pertinent response.

Related Articles, References, Credits, or External Links

Technet Exchange 2010 Requirements Windows Server Virtualization Validation Program VMware Platforms Supported and passed SVVP