Windows Server 2012-R2, DataCenter Edition Two boxes.
One has been rebooted, the other not yet. Fully patched as of 11/13 (the unrebooted one) and 11/19 (the other one). The first box was rebooted and none of the VMs booted up. Manually starting the service results in: *>net start vmms* The Hyper-V Virtual Machine Management service is starting. The Hyper-V Virtual Machine Management service could not be started. A system error has occurred. System error 14 has occurred. Not enough storage is available to complete this operation. Uninstalled all patches for November. No dice. Removed and Reinstalled the Hyper-V role. No dice. Performed an in-place re-install of the OS. No dice. Re-applied all patches through last night. No dice. Multiple removals and reinstallations of the Hyper-V role. No dice. Due to this, I did not reboot the other box, but this morning I tried restarting the VMMS service, and it generates the same error. So the VMs are running there, but if I reboot them or reboot the host, I'll have two boxes in the same state. Spent several hours looking at Process Monitor and Dependency Walker looking for DLL/EXE mismatches, but cannot see anything that is useful. One other piece of software was upgraded around the same time (11/12), but disabling and uninstalling it hasn't changed anything. Google has provided similar (and near similar) messages pertaining to Hyper-V on 2008, but nothing on 2012 or 2012-R2. I'm close to reinstalling the OS entirely and seeing if that helps, but I don't know what is going to cause it to break again... So, has anyone seen or heard of this problem? Regards, Reinstalled the OS over the existing install. not start the *ASB **http://XeeMe.com/AndrewBaker* <http://xeeme.com/AndrewBaker> *Providing Virtual CIO Services (IT Operations & Information Security) for the SMB market...*
