Solved

Installing SCVMM Trial broke existing Hyper-V VMs

Posted on 2011-09-11
2
1,215 Views
Last Modified: 2013-11-06
I have a Windows 2008 R2 server that I installed Hyper-V on and built a couple of Virtual Machines. The first one is the core SBS 2011 server for the building, the second is an FTP server also running 2008 R2. While trying to fix another issue I installed a copy of the Microsoft Security Center Virtual Machine Manager, and now the VMs won't start. You can berate me later for doing this on the production server, but I was backed into a corner on the project. I at least had the forethought to build another domain controller onto seperate server so I haven't lost AD services complely, just DHCP and email for now.

When Hyper-V was orginally installed I set the default location for the Virtual Machine files to be stored  as D:\Hyper-V\Virtual Machines and the Virtual Hard Drives as D:\Hyper-V\Virtual Hard Disks. I stopped the VMs that were running before starting the VMM install, did a clean reboot as the analyzer suggested. When the VMM installed it only asked where the Virtual machines were stored. When I went to restart the VMs, both gave errors similar to the following (different Machine IDs for each):

"Unnamed VM" could not initialize

an attempt to read or update the virtual machine
configuration failed because access was denied.

"Unnamed VM" could not initilize. (Virtual machine ID
1A4E96D-8657-4ADF-800E-11F0204FB54D)

"Unnamed VM" could not read or update the virtual machine
configuration because access was denied: General Access
denied error (0x80070005). Check the security settings on
the folder in which the virtual machine is stored (Virtual
machine ID 1A4E96D-8657-4ADF-800E-11F0204FB54D)

After some fishing about on MS Support and on the net, I was able to determine that the issue was that the extended permissions on the files and directories got mucked up when VMM installed, so for both of the top Level Directories, and each of the vhd files, the "machine" folder and Macgine XML file, I ran the following command:

C:\Users\administrator.RTANGLE>icacls "D:\Hyper-V\Virtual Hard Disks\SBS2011-FixedSize.vhd" /grant "NT VIRTUAL MACHINE\334880EE-6A4E-4B81-98FB-BF3FAF6B577D":F

This got me to the point where  now get the following error:


'SBS2011' could nit initialize.
An attempt to initialize VM saved state failed.

'SBS2011' could not initialize. (Virtual machine ID
334880EE-6A4E-4B81-98FB-BF3AF6B577D)

'SBS2011' could not create or access saved state file
D:\Hyper-V\Virtual Machines\Virtual Machines...\334880EE-6A4E-4B81-98FB-BF3AF6B577D.vsv.
(Virtual machine ID
334880EE-6A4E-4B81-98FB-BF3AF6B577D)

I went through the log files and found that the file it was complaining about was D:\Hyper-V\Virtual Machines\Virtual Machines\334880EE-6A4E-4B81-98FB-BF3AF6B577D\334880EE-6A4E-4B81-98FB-BF3AF6B577D.vsv. I can see that this file was created and has content (not zero sized).

I tried running the same icacls command above on that file and also tried adding /inheritance:e to the options and doing the directory again, but still no joy.

Can somebody help me get these VMs working again please!
0
Comment
Question by:oneobserver
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
2 Comments
 

Author Comment

by:oneobserver
ID: 36520621
I will admit that I am very new to using Hyper-V, which was one of the reasons why I was looking into the VMM. While typing this thread, I exported both machines so I would have a copy if needed. Since they finished as I was sending the last message, I thought I would try and just import them back into the system again. I asked it to make a copy with a unique ID and to copy the files so I could repeat the process if needed. It fails saying the virtual hard disk file already exists. Should I be using the restore/Move option instead or am I on the wrong track altogether?
0
 

Accepted Solution

by:
oneobserver earned 0 total points
ID: 36520877
Fixed it.

Created a new location to host the virtual machines on the Hyper-V server. Went back into VMM and updated that location as the only place to create new machines. Switched back to the original Hyper-V manager and imported both machines and copied the files to the new location and now both VMs are starting correcty. Whew!  No points awarded I found my own way out...
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Introduction RemoteFX is already in use today, but you're probably not aware of it.  With the advent of Windows 2012 and Windows 8, RDP has gotten a whole lot better due to the fact that RDP now uses even more RemoteFX technologies to make desktop …
Few best practices specific to Network Configurations to be considered while deploying a Hyper-V infrastructure. It may not be the full list, but this could be a base line. Dedicated Network: Always consider dedicated network/VLAN for Hyper-V…
This tutorial will walk an individual through the steps necessary to configure their installation of BackupExec 2012 to use network shared disk space. Verify that the path to the shared storage is valid and that data can be written to that location:…
This tutorial will walk an individual through setting the global and backup job media overwrite and protection periods in Backup Exec 2012. Log onto the Backup Exec Central Administration Server. Examine the services. If all or most of them are stop…

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question