Hello world,
An attempted removal of the Hyper-V role on a Windows Server 2008 R2 Standard server has failed (on an HP ProLiant DL380 G6), resulting in Hyper-V showing up in Server Manager in some half-dead state. Hyper-V services aren't running (they've been removed) but something (Hyper-V-VMMS) is alive enough to still put events in the Event Log.
If I attempt to remove the Hyper-V role now, it whirrs away for a minute and asks for a reboot. Once the machine has started, the clean-up that automatically launches just asks for a reboot again. This happens until the OS gives up (i.e. Windows *detects* that it's stuck in an infinite loop).
Looking in the ServerManager.log file (what is it with these stonkingly massive log files? I quite like using Notepad, you know!) I suspect this is what's tripping the uninstall up:
5400: 2012-11-06 13:22:34.758 [Services] Error (Id=0) System.InvalidOperationException: Service vhdsvc was not found on computer 'DR-SRV-SQL1'. --- System.ComponentModel.Win32Exception: The specified service does not exist as an installed service --- End of inner exception stack trace --- at System.ServiceProcess.ServiceController.GenerateNames() at System.ServiceProcess.ServiceController.get_DisplayName() at Microsoft.Windows.ServerManager.ServiceInfo.InitServiceInfo(Object obj)
5400: 2012-11-06 13:22:34.758 [Services] Error (Id=0) System.InvalidOperationException: Service nvspwmi was not found on computer 'DR-SRV-SQL1'. --- System.ComponentModel.Win32Exception: The specified service does not exist as an installed service --- End of inner exception stack trace --- at System.ServiceProcess.ServiceController.GenerateNames() at System.ServiceProcess.ServiceController.get_DisplayName() at Microsoft.Windows.ServerManager.ServiceInfo.InitServiceInfo(Object obj)
5400: 2012-11-06 13:22:34.758 [Services] Error (Id=0) System.InvalidOperationException: Service vmms was not found on computer 'DR-SRV-SQL1'. --- System.ComponentModel.Win32Exception: The specified service does not exist as an installed service --- End of inner exception stack trace --- at System.ServiceProcess.ServiceController.GenerateNames() at System.ServiceProcess.ServiceController.get_DisplayName() at Microsoft.Windows.ServerManager.ServiceInfo.InitServiceInfo(Object obj)
It's like it's trying to remove Hyper-V services that are simply no longer there and can't handle the fact. Is there any way to mop up the bits the Hyper-V role removal can't get to, or is the ghost of Hyper-V in Server Manager nothing much to worry about now?
I seem to be stuck between two choices here: leave the server as is and just let Hyper-V hang around like some dead conjoined twin, or undertake the perfect ((insert opposite of heaven here)) that is reinstalling Windows on a three year old server. Neither are terribly appetising!
Any help, tips or pointers would be appreciated!
Thanks in advance,
Paul C