Hyper-V Virtual Machines wont start with Errors 17040 and 15500


We have a Hyper-V Host server running Server 2008 Datacenter with Hyper-V RTM.  On this host we have several guest machines:

1.       Domain Controller

2.       DPM

3.       VMM

4.       Etc


The host OS had a VMM agent which happened to be managed by Virtual Machine Manager which was running on guest OS #3.  In other words, the guest was managing the host.


After installing some windows updates and rebooting the host OS, none of the VM’s would boot, with a dialog box saying that the machines were "unable to start."  Clicking on details would show "ServerName failed to start worker process: The extended attributes are inconsistent. (0x800700FF)."


The following errors showed in the event log:


Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin

Source:        Microsoft-Windows-Hyper-V-VMMS

Date:          8/29/2008 1:04:57 PM

Event ID:      15500

Task Category: None

Level:         Error


User:          SYSTEM

Computer:      Hyper-V Servername 


‘CATDEMO-DC’ failed to start worker process: The extended attributes are inconsistent. (0x800700FF). (Virtual machine ID C6A6A456-C58A-45BE-93D4-A94081481267)



Log Name:      Microsoft-Windows-Hyper-V-Worker-Admin

Source:        Microsoft-Windows-Hyper-V-Worker

Date:          8/29/2008 1:07:06 PM

Event ID:      17040

Task Category: None

Level:         Error


User:          NETWORK SERVICE

Computer:      Hyper-V Servername


The authorization store could not be initialized from storage location ‘msxml://C:\ProgramData\Microsoft\Virtual Machine Manager\HyperVAuthStore.xml’. Error: General access denied error (0x80070005).




1.       Back up the C:\ProgramData\Microsoft\Virtual Machine Manager\HyperVAuthStore.xml file by copying it to the desktop

2.       Change security on C:\ProgramData\Microsoft\Virtual Machine Manager\HyperVAuthStore.xml, give “EVERYONE” read access to the file.

3.       Start your virtual machines.


The recommended resolution is to reinstall the VMM agent from the VMM server, but this wasn’t possible since the VMM server was a virtual that wouldn’t start.  This is a known error with VMM


Related Articles:





Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s