• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 780
  • Last Modified:

Hyper V role corrupted

When installing updates, our Windows 2008 server hung for ages on one update.    I gave it a hard restart and now the Hyper V role is corrupted.  

We have only one virtual machine that runs on this particular server and it is running just fine - doesn't seem to be affected.  

My question is how do I recover my Hyper-V server role without affecting the Virtualized server it's hosting?   I can guess that I should uninstall the current hyper-v role and then reinstall but I'm uncertain...

Hoping someone can guide me safely through this.

0
egalois
Asked:
egalois
  • 6
  • 3
2 Solutions
 
Svet PaperovIT ManagerCommented:
Since your VM is running what exactlly is corrupted?

The best option will be if you are able to shutdown the VM and export it before trying to fix the Hyper-V.

 Could you give us more details about what doesn't work
0
 
egaloisAuthor Commented:
When I login to the "Hyper V platform server" the Role Hyper-V usually shows the virutalized server and gives me a host of tools that I can use to manipulate the server - including "Export".

In this case, I see under "Roles"     "Error"    - nothing else.  The Role Hyper V isn't even showing.   I can't export the machine because I can't open the hyper -v role and choose "Export".

I'm trying to comb the event logs now for more information to help.
0
 
egaloisAuthor Commented:
  hyper v error
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
Svet PaperovIT ManagerCommented:
Yes, info from the event log might help.

The best case scenario will be if you have a recent backup of the server. You could do a system state restore then.

The worst case is if you have snapshots taken of your virtual machines, but I can provide you with a procedure how to restore VM. If your VM is without snapshots it is not so bad: since it's working you can just shutdown it and copy the VHD file at some safe place.

Obviously the hypervisor is up, may be only thing corrupted is the management tools. If you have Windows 7 with RSAT you could try to connect to the Hyper-V manager from there. RSAT for Windows 7 can be downloaded from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=7d2f6ad7-656b-4313-a005-4e344e43997d
 
0
 
egaloisAuthor Commented:
I don't believe I have snapshots - we were advised against using this feature.  But the roles veiw is where I normally see them and this is not available so how can I confirm?

Using a backup is less desirable.   We have backups.  However, the issue came about 4 months ago and we are just now getting to it.  Restoring from a job that precedes the problem would mean restoring 4 month old info....  Maybe it doesn't matter that time has transpired.  But it seems to me it would.

0
 
Svet PaperovIT ManagerCommented:
Good choice about not using snapshots, they are no good in production environment. If you have snapshots you would have some AVHD files alongside the VHD file and some folders with very long ABCDE-12345… names in the Snapshot subfolder. If you don’t have these you are OK.

Were you able to run Hyper-V Manager from Windows 7 with RSAT? If it works you will be able to export the virtual machine. Otherwise, you could just copy the VHD file but you are going to lose the network configuration of the VM when you attach it back to newly installed Hyper-V. Besides the network cards there is no other configuration that would be lost. In the worst case you would have to clean the Registry of the virtual machine if it doesn’t allow you to use the same IP address on a new NIC after the restore and reactivate the Windows. The export/import procedure takes care for this.

After stopping the Virtual machine you need to export (using Hyper-V Manager from Windows) or copy the VHD file from the server. Then you can safely try to remove the Hyper-V role. Beware that the server will restart to complete the process. I suggest you to take a backup before removing the role.

If you want to try to fix it without removing, you will have to go over the event log and see what the errors are.
0
 
egaloisAuthor Commented:
I'm trying to apply this fix.  It looks exactly like what I have / need.   I am waiting for a "maintenance window" this weekend to attempt.  Thanks for patience
0
 
egaloisAuthor Commented:
When I come back to this server, I see now that the "Data" drive E, where we keep the vhd file, is no longer visible in the "Computer" explorer window of the Hyper-V host?     Yet;  the virtual machine is running, and through my hyper-v management tool on another domain computer, I can see that the virtual machine is still located on this missing E drive!?!   Fortunately, I'm able to safely export the virtual machine but I'm very concerned about how and why the E drive would suddenly not show up?  And how it's possible that the Virtual Server could be running still?

0
 
egaloisAuthor Commented:
Thanks
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

  • 6
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now