Awesome news - and thank you for breaking down your troubleshooting and resolution!
-- Espi On Thu, Nov 20, 2014 at 10:57 AM, Andrew S. Baker <[email protected]> wrote: > Problem resolved > > Somehow, the permissions on the *files *in the following folder were a > problem: > > *C:\ProgramData\Microsoft\Windows\Hyper-V\Resource Types* > > The folder permissions appeared to be appropriate, but I could not see the > permissions on the files nor access them in any way. > > I took ownership of the folder itself (which was previously owned by > SYSTEM) and then applied its permissions to the files within. > > They were owned by SYSTEM and I could not get access to them, so I took > ownership, and then reapplied the very same permission that were showing on > the parent folder. > > This allowed the service to run, but it didn't give me back my list of VMs > on either system. (That was understandable on the system where i had > reinstalled Hyper-V a half-dozen or so times, but not on the other server) > > After reviewing a new ProcMon session, I ended up having to perform the > same permissions on the parent folder and all the way down: > > *C:\ProgramData\Microsoft\Windows\Hyper-V\* > > This brought everything back on the least touched system. *Yay!!!* > > > On the other system, I'll have to recreate the virtual machine config, > which I have documented and is thus trivial. Plus, it's a total of 3 > systems on this host, as opposed to 10 on the other host. > > > I'm thankful that I always reboot the smaller host first after patches. > Another process validated. > > And, it seems that the patches were not implicated in this fiasco. > > I have no idea why the permissions were either changed on that folder or > came into play at this point (vs some previous month), but the only > lingering suspicion is upgrade path. (*All three* of these boxes were > upgraded from 2012 to 2012R2. Ironically, the one that worked and helped > me to find the problem had been upgraded from 2008-R2 to 2012 to 2012-R2.) > > After a review of my notes, I may have more to say on this, but for now, I > am glad to have gotten past this with some idea of what the problem was, > although not exactly why it happened. > > ProcMon to the rescue again. > > Thanks for all the pointers provided, as they aided in ruling out other > things. > > > Regards! > > > > > > *ASB **http://XeeMe.com/AndrewBaker* <http://xeeme.com/AndrewBaker> > *Providing Virtual CIO Services (IT Operations & Information Security) for > the SMB market...* > > > > On Thu, Nov 20, 2014 at 11:46 AM, Andrew S. Baker <[email protected]> > wrote: > >> I played around with pagefile settings to no avail... >> >> Then, I enabled the Hyper-V role on my older (former) Hyper-V host which >> only has 8GB RAM. >> >> It works. >> >> So, I started running some more PROCMON tests against both the working >> and the unworking system, and started to see something that might point to >> permissions. >> >> The first few options dead-ended, but I may have found something now, in >> the *C:\ProgramData\Microsoft\Windows\Hyper-V* folder. >> >> To be continued... >> >> >> >> >> *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:52 PM, Miller Bonnie L. < >> [email protected]> wrote: >> >>> Found this thread--I'm not seeing an answer here, but might give you >>> some ideas? The one comment that strikes me is about the page file as that >>> could be memory related. Maybe try removing it completely and get it to >>> create a brand new one? I'm assuming you've already disabled any AV >>> software. >>> >>> >>> >>> >>> https://social.technet.microsoft.com/Forums/windowsserver/en-US/7c1a74b9-b512-4a09-80b5-1ae344f72840/hyperv-vmm-service-terminated-with-the-following-error-not-enough-storage-is-available-to-complete?forum=winserverhyperv >>> >>> >>> >>> -Bonnie >>> >>> >>> >>> *From:* [email protected] [mailto: >>> [email protected]] *On Behalf Of *Andrew S. Baker >>> *Sent:* Wednesday, November 19, 2014 12:13 PM >>> *To:* ntsysadm >>> *Subject:* Re: [NTSysADM] Cannot Start the Hyper-V Management Service >>> >>> >>> >>> 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, >>> >>> >>> >>> >>> >>> >>> *ASB **http://XeeMe.com/AndrewBaker* <http://xeeme.com/AndrewBaker> >>> *Providing Virtual CIO Services (IT Operations & Information Security) >>> for the SMB market...* >>> >>> >>> >>> >>> >>> >>> >> >> >
