locked
Hyper-V 2012 Virtual Machine Management Service stops for no apparent reason RRS feed

  • Question

  • 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>

    Tuesday, September 4, 2012 6:09 PM

Answers

  • So, it appears that you must be using the SCVMM 2012 SP1 CTP2?  (since I see a mention of the SCVMM Agent and only this version will work with Server 2012) - BTW SCVMM 2012 SP1 CTP is not supported for production at this time, where Server 2012 Hyper-V is.

    Also, what do you have Config Manager pushing to the Hyper-V Server?  There might be an inherant incongruence.

    Quite honestly, this is the first time I have seen mention of folks running a Config Man agent on a Hyper-V Server.  Others might be more familiar with the two interacting with each other.


    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Attempting change is of your own free will.

    • Marked as answer by GeoTech Friday, September 7, 2012 1:52 PM
    Tuesday, September 4, 2012 6:46 PM

All replies

  • So, it appears that you must be using the SCVMM 2012 SP1 CTP2?  (since I see a mention of the SCVMM Agent and only this version will work with Server 2012) - BTW SCVMM 2012 SP1 CTP is not supported for production at this time, where Server 2012 Hyper-V is.

    Also, what do you have Config Manager pushing to the Hyper-V Server?  There might be an inherant incongruence.

    Quite honestly, this is the first time I have seen mention of folks running a Config Man agent on a Hyper-V Server.  Others might be more familiar with the two interacting with each other.


    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Attempting change is of your own free will.

    • Marked as answer by GeoTech Friday, September 7, 2012 1:52 PM
    Tuesday, September 4, 2012 6:46 PM
  • Hi Brian,

    Actually I'm using the SCVMM RTM agent (didn't know RTM version was not supported on 2012). I've already pulled both the SCCM agent and the SCVMM agent from the server to see if that has any effect. As to SCCM no current packages targeted, but eventually will be used to push patches.

    I'm skeptical either is the problem but I'll know in 24hrs... and post update. Thanks, Ken

    Tuesday, September 4, 2012 7:13 PM
  • I also have this issue with my Server 2012 RTM boxes. I have a Configuration Manager 2012 agent installed, but there are no ties to VMM 2012, and SC2012 SP1 (either CTP) is not applied. I guess I'll try disabling the Configuration Manager agent.
    Wednesday, September 5, 2012 5:36 PM
  • Wes, still reviewing here but it appears the client is the problem. I'm adding them back one at a time to confirm. Since you were not using SCVMM I'll assume the SCCM client was the culprit. Ken

    Wednesday, September 5, 2012 5:41 PM
  • I can confirm that after I removed the SCCM 2012 client (I also disabled push install to my servers temporarily), the Hyper-V VMMS service stayed up overnight.
    Friday, September 7, 2012 1:33 PM
  • I have the same issue.

    Confirmed removing SCCM 2012 client stops the problem happening. Hopefully this is fixed soon...

    Friday, September 7, 2012 10:49 PM
  • I also have been experiencing the Hyper-V server services stopping.....SCCM 2012 has been pushing out the agent, I am in the process of removing it, and will see if this addresses the issue of Hyper-V stopping......

     


    RF

    Saturday, September 22, 2012 12:22 PM
  • Removed SCCM 2012 Client and HYper-V service is no longer stopping.....

    Thanks

    Wes Kroesbergen
    Avatar of Wes Kroesbergen

    Wes Kroesbergen

    Envision IT

    Partner

    45 Points 4 0 0
    Recent Achievements
    First Answer Confirmed First Marked Answer First Helpful Vote
    Wes Kroesbergen's and Merlus !

    RF



    • Edited by RUOK2 Sunday, September 23, 2012 10:15 AM
    Sunday, September 23, 2012 10:13 AM
  • Hello everyone I had this same problem,
    VMM 2012 CTP
    SCCM 2012 RC
    All Windows 2012 hosts - tomorrow the whole service agent in the vmm host are stopped, after uninstall the SCCM 2012 RC agent - the agent works vmm normal?
    Anyone know why? The sccm 2012rc not compatible and to install agents on Windows 2012 hosts?
    Some documentation on the subject?

    thank you

    Ranieri Queiroz

    Friday, September 28, 2012 1:14 PM
  • Never assume that software in any form of release that is not final (RTM or GA) is fully compatible with anything that is. 

    Unless expressely stated by the team developing it.

    So far, this case has been specific to Hyper-V, not Server in general. 

    And, to answer your question; it might not be.  You would need to ask that question in the SCCM forum.


    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Attempting change is of your own free will.

    Friday, September 28, 2012 2:37 PM
  • hello thanks for the feedback, I asked about this scenario because you already went through the same difficulty on the agent sccm 2012 - agent stuck in hyper-v, I thought I could gather more information with you.

    I found nothing in the research that proves that the correction Parade agent hyper-v is related to the agent sccm 2012, more after the removal of the agent from the agent actually sccm 2012 hyper-v not stopped.

    Thank you.

    Ranieri Queiroz

    Friday, September 28, 2012 3:34 PM
  • I have seen the same issue on two 2012 servers (both were upgraded from 2008 R2)  the sccm agent (2012 RTM) was installed for patch management... Seems like something we "should" have!  the VMM service stopped within 24 hrs on both systems, a restart is successful, but no indication why it was stopped.  I will try disabling the agent host to see if the VMM service will survive > 24 hrs. 

    Friday, October 19, 2012 5:39 PM
  • the following procedure for the solution of the charts vmm 3.0 on windows 2012.

    Do not know why it happens more ..... I removed the agent configuration manager 2012 and never stopped the agent vmm 2012.

    Ranieri Queiroz

    Friday, October 19, 2012 7:54 PM
  • Hi guys, I found same issue in my environment, because uninstalling SCCM Agent is not a possibility for me, I create a scheduled task in the servers what take action when the service is stopping.

    I wrote a workarround for this case in my blog

    Tuesday, December 4, 2012 7:50 PM
  • same problem here with VMM 2012and SCCM2012 CU2

    any timeframe on a fix? is this fixed in the long awaited SP1 for VMM and SP1 SCCM2012 products by any chance?

     

    friends don't let friends do instant

    Wednesday, December 19, 2012 4:50 AM
  • I have this issue on 2 hyper-v2008 r2, with sccm2012 agent.

    It should be nice to get a fix.

    Wednesday, January 2, 2013 4:55 AM
  • I have the same issue on Server 2012 with SCCM 2012. Only using this for Endpoint Protection. I find it a bit silly that Microsoft causes this to their own product. I am also getting Event ID 63 (like a million a day) on all servers/computers with EP.

    Event ID: 63

    Source: WMI

    User: System

    A provider, PolicyPlatform_DocumentStore, has been registered in the Windows Management Instrumentation namespace root\Microsoft\PolicyPlatform\Documents to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. 

    It would be nice to see when Microsoft will fix this.

    Wednesday, January 2, 2013 4:35 PM
  • The final fix is on the way folks. MS RTM'ed SP1 for System Center 2012 in mid December. Look for general avaliablity this month. Ken

    http://redmondmag.com/articles/2012/12/14/system-center-2012-sp1-rtm.aspx

    Wednesday, January 2, 2013 4:58 PM
  • in our case it seems related to when KB2506143 [Windows Management Framework 3.0] was installed in December.

    they've since acknowledged that major compatability issues with SCCM 2012 and SCVMM 2012 exist. 

    best thing to do is do the registry fix workaround after removing the update - look for How to repair MDT 2012 integration with ConfigMgr 2012 and MP after KB2506143


    friends don't let friends do instant

    • Proposed as answer by DJ Moz Thursday, January 3, 2013 8:45 PM
    Thursday, January 3, 2013 12:39 AM
  • in our case it seems related to when KB2506143 [Windows Management Framework 3.0] was installed in December.

    they've since acknowledged that major compatability issues with SCCM 2012 and SCVMM 2012 exist. 

    best thing to do is do the registry fix workaround after removing the update - look for How to repair MDT 2012 integration with ConfigMgr 2012 and MP after KB2506143


    friends don't let friends do instant

     I can confirm that the issue started after I've installed Wndows Management Framework 3.0 in my Hyper-V hosts (running 2008 R2). It's a requirement to manage them from the new server manager console in w8.
    Thursday, January 3, 2013 4:49 AM
  • have you tried the registry edit by setting this to true? HKLM\SOFTWARE\Microsoft\CCM\CcmEval\NotifyOnly

    friends don't let friends do instant

    Thursday, January 3, 2013 8:46 PM
  • You may need to reset the WMI repository.

    I've found, since the update was installed, it's created a new wmi repository daily and the services stop at the time the Sccm eval cycle runs daily.

    So after removing the KB, I:

    Stopped the WMI service

    Reset the repository using the following command  - Winmgmt /salvagerepository %windir%\System32\wbem (if that doesn't work then use  Winmgmt /resetrepository %windir%\System32\wbem which will clear it and rebuild)

    This then automatically restarted the WMI service, (check anyway), and had cleared the SCCM client data.  Reboot, or start your hyper-v services.  The SCCM client has now refreshed and I've started all of the discovery cycles and as of yet, the Hyper-v services remain in a running state.


    • Edited by B77 Tuesday, January 8, 2013 12:38 AM
    Monday, January 7, 2013 11:39 PM