Thanks, but I had already tried that one without success... :)
*ASB **http://XeeMe.com/AndrewBaker* <http://xeeme.com/AndrewBaker> *Providing Virtual CIO Services (IT Operations & Information Security) for the SMB market...* On Wed, Nov 19, 2014 at 3:57 PM, J- P <[email protected]> wrote: > another one that may help > > > http://www.edugeek.net/forums/enterprise-software/106082-system-centre-virtual-machine-manager-2012-error-2911-a.html > > > > > > > ------------------------------ > From: [email protected] > To: [email protected] > Subject: RE: [NTSysADM] Cannot Start the Hyper-V Management Service > Date: Wed, 19 Nov 2014 15:31:29 -0500 > > here's one related to CPU core count- (i know it's reaching ) > > > http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Windows_Server_2012/Q_28506159.html > > > > > > ------------------------------ > From: [email protected] > Date: Wed, 19 Nov 2014 15:12:30 -0500 > Subject: Re: [NTSysADM] Cannot Start the Hyper-V Management Service > To: [email protected] > > Yeah, I'm less inclined to believe it is patch related at this point, but > that's somewhat scarier, frankly. Something changed since the last reboot > on 10/19, and I can't figure our what the change was that has an impact > like this, and an over-the-top reinstall didn't help. > > Regards, > > > > > > > > *ASB **http://XeeMe.com/AndrewBaker* <http://xeeme.com/AndrewBaker> > *Providing Virtual CIO Services (IT Operations & Information Security) for > the SMB market...* > > > > > > On Wed, Nov 19, 2014 at 12:34 PM, Richard Stovall <[email protected]> > wrote: > > No real help, but I did completely patch and restart my three Hyper-V > servers without incident after the first iteration of 2992611 from 11/11. > > On Wed, Nov 19, 2014 at 11:53 AM, Andrew S. Baker <[email protected]> > wrote: > > 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...* > > > > > > >
