The server encountered an error while creating . No reason given.

If you have received the error:
“The server encountered an error while creating <virtual machine name>”

When creating a new virtual machine or trying to add a new virtual machine from existing VHD, where there is no reason given for the error other than “Creating the virtual machine failed”.

You will find that there is a lack of info on Google relating to this, as most users would have had a reason under Creating the virtual machine failed.

On top of that, the Event Log ID 16000 doesn’t tell you much other than “The locale specific resource for the desired message is not present”, which is also a generic message with no real reason.

My Fix:

In my case, I retraced some steps and noticed this issue occurred after joining the Hyper-V server to the domain. All virtual machines added before then worked fine, but could not add, import, mount any existing VHD disks.

It appears to be a GPO related problem. In my case, I setup an OU with no inheritance to fix the issue. The server once joined to the domain was dropped into the default “Computers” container.

More info can be found from Microsoft here with alternate fixes:


Hyper-V WordPress Appliance

After my server crash, I moved from Vmware Server to Hyper-V. I wanted to go ESX, but I haven’t got hardware fully support by ESX. Nonetheless, using Hyper-V I’m extremely impressed by it’s speed and reliability.

The problem with Hyper-V is that there is not as many appliances readily available. And those that are available are generally a port of a VMware appliance and not really tested.

I had an issue looking for a WordPress appliance that would work on Hyper-V without too much mucking around as I’m not really a hardcore Linux person. I managed to find a VMware appliance that would port straigh over to Hyper-V with little fuss. It’s the TurnKey WordPress appliance available here:

Just use the StarWind Converter on it to port the vmdk files to a VHD file. Then chuck it into Hyper-V and start it up. Make sure you use the legacy Network Adapter. Everything works error free and without hassle! Great appliance that is ready to go!

VMware to Hyper-V (STOP 0×0000007b)

Been migrating from Vmware to Hyper-V after my server crash. I was pretty damn impressed with Hyper-V. It’s extremely fast and easy to manage. It’s a great hypervisor, with the only draw back being the base OS taking just under 1GB of RAM. But that’s what you pay for to get a highly versatile virtualisation OS that will install onto any hardware.

Just a tip for those migrating from VMware to Hyper-V. It’s highly documented on the net that VMware uses SCSI hard drives to boot off (as this is what VMware suggests). Hyper-V only boots off IDE (even Hyper-V in 2008 R2).

To not get a STOP 0x0000007b BSOD error, you have to add a IDE hard drive into the virtual machine whilst it’s still running in VMware. Make sure you choose IDE Channel 1:0 or 1:1 as this installs the Primary IDE Channel. You probably already have a Secondary IDE Channel from the CDROM drive.

Last but not least, for me anyway I had to go to Computer Management and initialise the newly created IDE Hard Drive in VMware. I found that if I didn’t do this I’d end up with a BSOD in Hyper-V after the migration.

To summarise the steps in full (it’s been done a million times on the net already – but this is for those who want a one stop shop)

  1.  Uninstall VMware tools
  2. Shutdown virtual machine whilst it’s still in VMware
  3. Install an IDE hard drive on channel 1:0 or 1:1
  4. Startup the virtual machine
  5. Initialise the disk in Computer Management
  6. Shutdown virtual machine
  7. Convert from vmdk to vhd using the tool of your choice (I had most success with VDMKtoVHD from
  8. Mount the image into Hyper-V
  9. Using the Legacy Network Card will allow the network to work without drivers but restricts you to 10/100.
  10. Otherwise, use the standard Network Card but make sure you install the Integration Services (requires SP2 or higher if you’re running Windows 2003 Server)
  11. You’ll probably get Service Failed to Start errors, so you’ll have to check in Event Viewer and teeth through those issues. Nothing is perfect right? Just keep in mind that it may be caused by some of the VMware Services still installed on the system (check in Service.msc). For some reason, the VMware Tools uninstall does not get rid of them all.