locked
VMM service keeps crashing RRS feed

  • Question

  •  

    I have VMM installed on an 08 server that is a hyper-v vm on a 08 server core host.

    I have the VMM RC1 patch installed and my hyper-v is RTM.

     

    I cannot get the VMM service to stay running. It crashes everytime I try to open the VMM admin console.

    I've rolled back the VM and started over but still wound up with the same problem.

     

    Here's what's in the event logs.

     

    Log Name:      System
    Source:        Service Control Manager
    Date:          9/17/2008 12:18:36 PM
    Event ID:      7034
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      memscvmm.us.corp.mimeo.com
    Description:
    The Virtual Machine Manager service terminated unexpectedly.  It has done this 6 time(s).
    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="49152">7034</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2008-09-17T17:18:36.000Z" />
        <EventRecordID>8598</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>System</Channel>
        <Computer>memscvmm.us.corp.mimeo.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="param1">Virtual Machine Manager</Data>
        <Data Name="param2">6</Data>
      </EventData>
    </Event>

     

     

    And this.

     

    Log Name:      System
    Source:        Service Control Manager
    Date:          9/17/2008 12:18:02 PM
    Event ID:      7031
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      memscvmm.us.corp.mimeo.com
    Description:
    The Virtual Machine Manager service terminated unexpectedly.  It has done this 5 time(s).  The following corrective action will be taken in 100 milliseconds: Restart the service.
    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="49152">7031</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2008-09-17T17:18:02.000Z" />
        <EventRecordID>8596</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>System</Channel>
        <Computer>memscvmm.us.corp.mimeo.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="param1">Virtual Machine Manager</Data>
        <Data Name="param2">5</Data>
        <Data Name="param3">100</Data>
        <Data Name="param4">1</Data>
        <Data Name="param5">Restart the service</Data>
      </EventData>
    </Event>

     

     

    I also get this when opening the VMM admin console.

     

    The connection to the VMM server localhost was lost.

    ID:1612

    Wednesday, September 17, 2008 5:42 PM

Answers

All replies

  • You mention Hyper-V is at RTM.

     

    Did you add the Hyper-V RTM patch tot eh SCVMM server itself (for WinRM compatibility)?

     

    And...Did you connect to a Virtual Center server?  (as this will put SCVMM into a loop every now and then).

     

     

    Wednesday, September 17, 2008 7:20 PM
  •  

    Hyper-V RTM is installed on the 08 server Core machine that a 08 full install with SCVMM server runs on.

     

    No, I don't connect to a Virtual Center server.
    Wednesday, September 17, 2008 7:25 PM
  • Brian is asking if you also installed the Hyper-V RTM patch on the SCVMM server (which in your case is a VM running on your Hyper-V box)...

    -matt
    Wednesday, September 17, 2008 7:36 PM
  • The Hyper-V patch level must match on the two machines.

     

    Wednesday, September 17, 2008 7:38 PM
  •  

    how do I check the hyper-v patch level?
    Wednesday, September 17, 2008 7:44 PM
  •  

    I don't have the hyper-v role installed on the machine running scvmm.

    Do you have to have the hyper-v role installed to run scvmm?

    If that's the case I can't put it on a VM because of the processor support.

     

    Wednesday, September 17, 2008 8:01 PM
  • The Hyper-V role does not have to be installed.  However the Hyper-V update needs to be installed.  As Brian mentioned in a previous post there is an updated version of WinRM included in that update.

    -matt
    Wednesday, September 17, 2008 9:15 PM
  •  

    I installed the update and still have the same errors.

     

    Wednesday, September 17, 2008 9:21 PM
  • Had you stopped all of the VMM services prior to applying the update?

     

    (you have to make sure to manually stop the VM Management Agent and the VMM Server services)

     

    Wednesday, September 17, 2008 10:12 PM
  •  

    I started over and made sure I got all the patches installed and it worked for about 30 mins before the admin console started crashing.

    The VMM service isn't crashing now.

    I'm getting the 1612 error when the console crashes.

    Wednesday, September 17, 2008 11:27 PM
  •  

    I spoke to soon the service is still crashing.
    Wednesday, September 17, 2008 11:32 PM
  • Recommend gather trace logs of the crash submitting bug on connect site.  You can get trace instructions from www.technet.com\chengw

     

    Monday, September 22, 2008 6:28 PM
  • The behavior mentioned is a side effect of not having the Hyper-V update (KB950050) applied.

    Sunday, September 28, 2008 4:06 AM
  •  Was this problem ever resolved?  I have just started getting this error.  I'm running the evaluation copy (haven't upgraded to the production version yet).  I have all my updates in place. 

    The earlier discussion of this topic centers on a time before certain updates that are now required by SCVMM.  The version of Hyper-V manager then was 6.0.6001.18016 associated with KB950050.  Since then I have had to add KB956589 and KB956774 to keep everyone happy.  This results in a Hyper-V manager version of 6.0.6001.18125. 

    The SCVMM has been running fine until today.  The only change I noted was the addition of a Host server running Data Center Core two days ago.  I just verified that the Core install is up to date on the updates and is at 6.0.6001.18125. 

    I did not see a resolution posted.  So again was this problem ever resolved?

    Thanks
    -Robert
    Tuesday, February 10, 2009 1:00 AM
  • Was this problem ever resolved?


    Thursday, June 25, 2009 1:35 PM
  • If you are still having this problem check the VM Manager log on the SCVMM server for SCVMM errors "1" and "199999".  The KB article 969269 ( http://support.microsoft.com/kb/969269 ) covers the general problem and work around.  The bottom line is that one or more of the host machines have an issue with their nics, and that is confusing SCVMM when it tries to do a host refresh on that host.  In my case I had ghost nics created by a firmware update, but there are other things that can create problems with the nics of a host.  I got rid of the ghost nics and the problem went away.  A subsequent host that I had the same symptom but did not have ghost nics.

    The KB article lists your options.  There is now a new option that is not listed in the article, upgrade to SCVMM 2008 R2.  I did that and resolved the second problem host that I mentioned above.  Basically Microsoft fixed the bug (oversight?) in SCVMM 2008 R2.  It is a quick in place upgrade followed by an agent update to each of the hosts.  There is no reboot required.  The upgrade of the SCVMM server took only 10 minutes.  My entire upgrade including the agent updates requied 45 minutes.  The agent update is a separate administrator action for each host after the upgrade is complete. 

    The R2 version is the eval code since the RTM has not been released (estimated for 10/09).  It is stable and fixed many of the P2V problems that we were having as well.

    Hopefully this helps, good luck.
    -Robert
    Thursday, June 25, 2009 8:24 PM