Archives

ErichZann1

Hyper-V encountered an error trying to access an object…

I’ve Googled this issue on and off for most of the day, more or less attempting every potential fix in the hope of resolving this issue so that I can move on and deploy a bunch of servers via Docker.  I’ve so far being unsuccessful.

Earlier today I installed Hyper-V.  Simple enough (and throughout my attempts to get it to work I’ve uninstalled, reinstalled, purged and re-imaged OS backups countless times).  Then I threw Docker into the mix.  Docker complained with the
noted error, so during my attempts to resolve it I ended up where I started: a recent OS image and a fresh install of Hyper-V.

When I attempt to use Hyper-V Manager, the issue is highlighted further because most entries within Hyper-V Settings, under Server, such as Virtual Hard Disks, Virtual Machines, NUMA Spanning and Enchanced Session Mode Policy list "Load Failed"
as the only item, with the error "There was an error loading the data for this setting." explaining how Hyper-V encountered an error trying to access an object…

The same goes with the Global Network Settings, under Mac Address Range, where "Load Failed" rears its ugly head again.  To cap it all, the Hyper-V Quick Create app throws the error the moment it starts.

No matter what I have attempted today, I simply cannot get Hyper-V working, and I’ve tried every solution Google has thrown at me.  Therefore I’d be eternally greatful for any assistance resolving the issue.

Thanks.

Read full post . . . .

Go Que Newsroom Categories

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 36 bytes) in /home/content/36/8658336/html/goquecom/wp-includes/taxonomy.php on line 3363