locked
SCVMM2012 SP1 Beta, VMMAgent on VMM Server fails RRS feed

  • Question

  • Hello,

    I have a fresh install of a Windows Server 2012 Datacenter. No Cluster. Then created a VM for SCVMM 2012 SP1 Beta. Installation went fine so far, but after the first night, I found that a refresh of the Library failed. This is due to the fact, that the Agent ist not responding. When I look after it, i. e. net start vmmagent, I always get a error. I never get the VMMAgent on the VMM Server running again, only uninstall VMM (retain settings), reboot and reinstall solves the problem.

    When trying to start VMMAgent, the Event Log entry shows the following entry (sorry, in German, translation in brackets):

    Name der fehlerhaften Anwendung (name of failed application): vmmAgent.exe, Version: 3.1.3612.0, Zeitstempel: 0x503c2754
    Name des fehlerhaften Moduls (name of failed module): MSVCR100.dll, Version: 10.0.40219.325, Zeitstempel: 0x4df2bcac
    Ausnahmecode (exception code): 0x40000015
    Fehleroffset (error offset): 0x00000000000761c9
    ID des fehlerhaften Prozesses (id of failed process): 0x540
    Startzeit der fehlerhaften Anwendung (start time of failed application): 0x01cd9c9117991b5b
    Pfad der fehlerhaften Anwendung (path failed application): C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\vmmAgent.exe
    Pfad des fehlerhaften Moduls (path failed module): C:\Windows\SYSTEM32\MSVCR100.dll
    Berichtskennung: 5570904b-0884-11e2-93f0-00155d10bc01
    Vollständiger Name des fehlerhaften Pakets (full nameof failed package): [empty]
    Anwendungs-ID, die relativ zum fehlerhaften Paket ist (application ID relative to failed package):[empty]

    I installed the vcredist from the VMM2012SP1Beta Installation Package (from Folder Prerequisites)

    My colleagues tested it again and they can reproduce this problem. The problem occurs on German and on English Windows Server 2012.

    Does anyone have a solution?

    Kind regards, David


    • Edited by David_SE Thursday, September 27, 2012 1:42 PM
    Thursday, September 27, 2012 1:41 PM

Answers

  • It seems I solved this issue. Fresh install Server 2012 and SCVMM2012 SP1 Beta, but didn't install SCCM 2012 Client like in last scenario. All works fine during a week.
    • Edited by iyastrebov Saturday, October 20, 2012 6:56 AM
    • Marked as answer by M Fawzi Monday, November 26, 2012 11:51 PM
    Saturday, October 20, 2012 6:56 AM

All replies

  • I have the same problem.

    First also with a german installation of Windows 2012, but i've tested it also with an english Windows installation.
    At the first installation the VMMAgent Service was running for about a week before ending in the night.
    Afterwards we could not start it agein and we also got the same error message as described above.

    On a new installation i had a little bit different behaviour: after the first night the service was ended too
    but when i tried to start it, i didn't get an error message, but after a few seconds the service was stopped again
    an the error above was logged in event log.

    • Proposed as answer by RUGood4it Wednesday, October 10, 2012 10:56 AM
    Tuesday, October 9, 2012 12:22 PM
  • Hello,

    I have the same error.

    Does anyone have a solutions?

    Thanks

    Dimitris

    Monday, October 15, 2012 9:11 AM
  • Any updates on this issue ?

    For me it is still not fixed !

    Monday, October 15, 2012 1:00 PM
  • Me too!  Having it here as well.  Server 2012 for all.
    Monday, October 15, 2012 1:45 PM
  • Im having the same problem, i can do a fresh install. It keeps working for 5 of 6 hours. After that i get same acces denied on my hosts, and the agent on the vmm server itself goes to not responding. If i try to start the service on the vmm server it crashes.

    Wednesday, October 17, 2012 8:52 AM
  • Hi all,

    to resolve this issue, install hyper-v role on the VMM2012 server.



    • Edited by enzo288 Friday, October 19, 2012 1:40 PM
    Friday, October 19, 2012 1:38 PM
  • It seems I solved this issue. Fresh install Server 2012 and SCVMM2012 SP1 Beta, but didn't install SCCM 2012 Client like in last scenario. All works fine during a week.
    • Edited by iyastrebov Saturday, October 20, 2012 6:56 AM
    • Marked as answer by M Fawzi Monday, November 26, 2012 11:51 PM
    Saturday, October 20, 2012 6:56 AM
  • Yeah, the problem is in incompatible Visual Studio Components which SCCM agent is installing with it. VMM agent also uses VS Components but much newer version. To avoid this problem on Beta stage (in RTM it will be fixed for sure) don't install SCCM agent on any host where is VMM agent is working.
    Wednesday, October 24, 2012 9:50 AM