Recursos para Profesionales de TI >
Página principal de foros
>
Hyper-V
>
hyper-V virtual machine management Service fail
hyper-V virtual machine management Service fail
- Hello,
the question is long... sorry :(
Server1 - 2008 Enterprise with Hyper-V
Server2 - 2003 R2 with SQL2005
I've installed SCVMM2008 on Server1 with the SCVMM2008 Database on Server2.
After some days i've uninstalled SCVMM from Server1, so when i try to start any VM from Hyper-V manager the error is this:
2008Core1 failed to start worker process: The extended attributes are inconsistent. (0x800700FF). (Virtual machine ID D829E154-BDD7-438B-8F9E-96B287173F9A)
In the Event Log, Application and Services-Microsoft-Windows-Hyper-V-VMMS there is this: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).
Mmm.... i think that there is a security error on that file, i go to check the security of HyperVAuthStore.xml and try to add "Everyone" in "Modify".
Ok, now all the VMs could start...
I've rebooted the Server1.
After reboot i've opened Hyper-V manager but the list of VM are empty!
I go to check the status of "hyper-V virtual machine management" service and... is stopped!
Try to start.... "Windows could not start the hyper-V virtual machine management Service on Local Computer. Error 0x80070002 The system cannot find the file specified".
Go to Event Log, Application and Services-Microsoft-Windows-Hyper-V-VMMS there is this:
The authorization store could not be initialized: 'msxml://C:\ProgramData\Microsoft\Virtual Machine Manager\HyperVAuthStore.xml'. Error: The system cannot find the file specified. (0x80070002).
Wow... CANNOT FIND!
Go to C:\ProgramData\Microsoft\Virtual Machine Manager and.... there isn't HyperVAuthStore.xml file!!
How can i recreate that file??
Thanks....
Respuestas
- This is an issue the VMM team is aware of. I'd suggest posting this in the Connect newsgroup for VMM (where you downloaded VMM 2008 from) to see if they have a resolution.
This posting is provided "AS IS" with no warranties, and confers no rights.- Marcado como respuestaMike Sterling [MSFT]MSFT, Propietariomartes, 15 de julio de 2008 13:17
Todas las respuestas
- Oh my God...
This problem is caused by the uninstallation of SCVMM2008 and in particular by the SCVMM Local Agent.
I've reinstalled only the SCVMM2008 Local Agent and all the Services could now start... :( - This is an issue the VMM team is aware of. I'd suggest posting this in the Connect newsgroup for VMM (where you downloaded VMM 2008 from) to see if they have a resolution.
This posting is provided "AS IS" with no warranties, and confers no rights.- Marcado como respuestaMike Sterling [MSFT]MSFT, Propietariomartes, 15 de julio de 2008 13:17
- Hi,
I have the same problem with Hyper-V. In my case, I installed Hyper-V with SQL in one server, and VMM in another, adding the Hyper-V server as a host. Everything worked well, till I discovered I had installed the 2007 version of VMM and not the 2008 version.
I uninstalled VMM and at some point re-started the Hyper-V server, which is when I started to have problems.
I guess I, too, am going to reinstall Hyper-V and VMM.
Thanks. - Hi,
I had the same problem yesterday. I found this post but the SCVMM was no longer required so I needed to find a way to enable the Virtual Machines without installing any SCVMM component.
At the end it was really simple, and the only thing you need is to backup your virtual machines not only the hard disks you will need also de configuration files. Here are the steps:
1.- Remove the Hyper-V Role
* This action doesn't remove either the configuration file or the hard disks of the virtual machines.
2.- After the reboot, reinstall the Hyper-V Role.
3.- After the reboot, open de Hyper-V console and YES your virtual machines are there with no changes at all.
One thing to consider is when you reinstall the Hyper-V Rol try to do the same configurations to the network adapter for the Hyper-V.
Another thing is that maybe you would need to set the network adapter for the virtual machines again.
My server is a Windows Server 2008 Enterprise 64-Bits.
Regards.- Propuesto como respuestaJose Cueva viernes, 08 de enero de 2010 23:32
Ivan:
Thanks for the post. I had the same situation. I have a Windows 2008 x64 server that's been running Hyper-V since October 2008. I had also installed a trial installation of System Center Virtual Machine Manager 2008 back in early 2009. The trial expired, and there wasn't a compelling reason to purchase it in this particular environment. So SCVMM hasn't been actively used on this Host system in about a year.
Anyway, the SCVMM had put an instance of SQL Server Express 2005 on this server. SQL Server Express had been failing to get updated with one of Microsoft's updates (Security Update for SQL Server 2005 Service Pack 3 (KB970892)) since late last summer.
I figured that today I would fix this SQL Express update error by uninstalling SCVMM since it was no longer used. This was a big mistake! Suddenly the Hyper-V Manager only displayed the following message:
The Virtual Machine Management service is not available
None of the VMs were listed.
After screwing around for a while, I figured that I was going to have to remove the Hyper-V role and add back on, again. I wasn't sure how much of the Hyper-V environment that I was going to have to redefine after this surgery, though. I'm glad that I came across your post.
My experience was exactly as you described:
- Remove Hyper-V Role
- Reboot
- Add Hyper-V Role
- Reboot
- All VMs have a configuration error within the NIC definition. Remapping Virtual NICs to the Virtual Networks within each VM definition fixes this issue.
- All VMs now start normally.
Hopefully, this post will help someone else.
See Ya!
Van
Venice, FL, USA
