Starting initial testing for migration to Hyper-V 2012 (or is it referred to as v3.0?). Essentially out of the box install of Server 2012 Data Center RTM (Full), with Hyper-V role enabled.
The day after the initial setup. I opened the Hyper-V console from a remote computer to start testing and was unable to connect to the Hyper-V Management Service. Logging in to the server directly I see that the Hyper-V Virtual Machine Management services
has stopped (Kudos MS for making that so easy to see!). After spending awhile in the event log and finding no reason (I see the service stop but no errors associated with it) I chalk it up to a fluke of the previous days initial install. Next day same thing.
Except two other services have also stopped. More event log research but no trail to follow. It’s as if the service is being commanded by something to stop?? The only possible connection I see is ConfigMgr 2012 client activity near the same time frame as the
service stopping.
Obviously I can’t move forward with further testing and migration until I sort this out. Sure I can set the services to restart but not the ideal option.
Any ideas? Or is 2012 too new to consider for production? I’ve included a couple of event log entries and a list of the services that get stopped.
Thanks, Ken
Stopped Services
Hyper-V Virtual Machine Management
System Center Virtual Machine Manager Agent
User Access Logging Service
Event Log Data
Log Name: System
Source: Service Control Manager
Date: 9/1/2012 12:26:10 AM
Event ID: 7036
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: VMS3.corp.FandR.com
Description:
The Hyper-V Virtual Machine Management service entered the stopped state.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="16384">7036</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2012-09-01T04:26:10.039321300Z" />
<EventRecordID>8188</EventRecordID>
<Correlation />
<Execution ProcessID="1068" ThreadID="4032" />
<Channel>System</Channel>
<Computer>VMS3.corp.FandR.com</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">Hyper-V Virtual Machine Management</Data>
<Data Name="param2">stopped</Data>
<Binary>76006D006D0073002F0031000000</Binary>
</EventData>
</Event>
Log Name: Application
Source: MsiInstaller
Date: 9/1/2012 12:26:36 AM
Event ID: 1040
Task Category: None
Level: Information
Keywords: Classic
User: SYSTEM
Computer: VMS3.corp.FandR.com
Description:
Beginning a Windows Installer transaction: C:\Windows\ccmsetup\{F9BE5FE5-D87B-4958-9BBB-B613A2F4075E}\client.msi. Client Process Id: 4360.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MsiInstaller" />
<EventID Qualifiers="0">1040</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-09-01T04:26:36.000000000Z" />
<EventRecordID>3729</EventRecordID>
<Channel>Application</Channel>
<Computer>VMS3.corp.FandR.com</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data>C:\Windows\ccmsetup\{F9BE5FE5-D87B-4958-9BBB-B613A2F4075E}\client.msi</Data>
<Data>4360</Data>
<Data>(NULL)</Data>
<Data>(NULL)</Data>
<Data>(NULL)</Data>
<Data>(NULL)</Data>
<Data>
</Data>
</EventData>
</Event>
