none
App-V Error : A required component of the Microsoft Application Virtualization system is not working

    Question

  • Environment:
    -------------- 

    - VMWare vSphere
    - VMWare Virtual Machine : Windows 7 Enterprise x64 SP1 SOE
    - App-V Sequencer 4.6 SP1

    Issue:
    ------- 

    After successful installation, the sequencer fails to launch. Throws the following two error messages:

     - A required component of the Microsoft Application Virtualization system is not working
     - Error connecting to the System Guard

    Troubleshooting done:
    -------------------------

    - No logs in the event viewer
    - App-V log
    ----------------------------------------------

    [08/25/2011 14:07:06]  

    [08/25/2011 14:07:06] =============== Sequencer launched.  Sequencer version:  4.6.1.20870 ===============

    [08/25/2011 14:07:06]  

    [08/25/2011 14:07:06 VRB CORE] Sequencer started.

    [08/25/2011 14:07:06 VRB CORE] SQM Initialization

    [08/25/2011 14:07:06 VRB CORE] SQM Logging Disabled

    [08/25/2011 14:07:06 VRB CORE] SQM running with test mode off

    [08/25/2011 14:07:13 VRB CORE] Sequencer terminating normally...

    [08/25/2011 14:07:13 VRB CORE] SQM Terminating...

    [08/25/2011 14:07:13 VRB CORE] SQM Not enabled - no upload

    [08/25/2011 14:07:13] Sequencer releasing log resources...

    [08/26/2011 15:53:19]  

    [08/26/2011 15:53:19] =============== Sequencer launched.  Sequencer version:  4.6.1.20870 ===============

    [08/26/2011 15:53:19]  

    [08/26/2011 15:53:19 VRB CORE] Sequencer started.

    [08/26/2011 15:53:19 VRB CORE] SQM Initialization

    [08/26/2011 15:53:19 VRB CORE] SQM Logging Disabled

    [08/26/2011 15:53:19 VRB CORE] SQM running with test mode off

    [08/26/2011 15:57:33 VRB CORE] Sequencer terminating normally...

    [08/26/2011 15:57:33 VRB CORE] SQM Terminating...

    [08/26/2011 15:57:33 VRB CORE] SQM Not enabled - no upload

    [08/26/2011 15:57:33] Sequencer releasing log resources...

    [08/26/2011 15:58:03]  

    [08/26/2011 15:58:03] =============== Sequencer launched.  Sequencer version:  4.6.1.20870 ===============

    [08/26/2011 15:58:03]  

    [08/26/2011 15:58:03 VRB CORE] Sequencer started.

    [08/26/2011 15:58:03 VRB CORE] SQM Initialization

    [08/26/2011 15:58:03 VRB CORE] SQM Logging Disabled

    [08/26/2011 15:58:03 VRB CORE] SQM running with test mode off

    [08/26/2011 16:00:41 VRB CORE] Sequencer terminating normally...

    [08/26/2011 16:00:41 VRB CORE] SQM Terminating...

    [08/26/2011 16:00:41 VRB CORE] SQM Not enabled - no upload

    [08/26/2011 16:00:41] Sequencer releasing log resources...

    [08/26/2011 16:01:44]  

    [08/26/2011 16:01:44] =============== Sequencer launched.  Sequencer version:  4.6.1.20870 ===============

    [08/26/2011 16:01:44]  

    [08/26/2011 16:01:44 VRB CORE] Sequencer started.

    [08/26/2011 16:01:44 VRB CORE] SQM Initialization

    [08/26/2011 16:01:44 VRB CORE] SQM Logging Disabled

    [08/26/2011 16:01:44 VRB CORE] SQM running with test mode off

    [08/26/2011 16:03:19 VRB CORE] Sequencer terminating normally...

    [08/26/2011 16:03:19 VRB CORE] SQM Terminating...

    [08/26/2011 16:03:19 VRB CORE] SQM Not enabled - no upload

    [08/26/2011 16:03:19] Sequencer releasing log resources...

    --------------------------- 

     - Rebuilt the machines. Does not work.

    Extra Information:
    ---------------------

    I am using our Windows 7 SOE to build these VMs - Sequencer does not work. But when I deploy the same SOE on a physical machine it works. I am not sure whats changed. The only thing I can think of is VMWare drivers. I am trying by removing VMWare drivers from the TaskSequence.   

    It would great if someone could throw some light on this. Happy to provide more information on this.

    Thanks,

    Vithal

     


    Vithal Maddala
    Friday, August 26, 2011 6:14 AM

Answers

  • So don't sequence on your SOE - add the same level of the OS, runtimes and pre-requisites to a vanilla installation

    This forum post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.
    • Proposed as answer by znack Sunday, August 28, 2011 2:02 PM
    • Marked as answer by Aaron.ParkerModerator Friday, November 16, 2012 11:14 PM
    Friday, August 26, 2011 10:03 AM
    Moderator

All replies

  • Have you tested a vanilla Windows 7 installation, with and without the VMware drivers?

    This forum post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.
    Friday, August 26, 2011 7:39 AM
    Moderator
  • I am most certain that it will work with the Vanilla Windows 7 media. I have removed the VMWare drivers from the SOE and rebuilt the machines - no go...
    Vithal Maddala
    Friday, August 26, 2011 8:52 AM
  • So don't sequence on your SOE - add the same level of the OS, runtimes and pre-requisites to a vanilla installation

    This forum post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.
    • Proposed as answer by znack Sunday, August 28, 2011 2:02 PM
    • Marked as answer by Aaron.ParkerModerator Friday, November 16, 2012 11:14 PM
    Friday, August 26, 2011 10:03 AM
    Moderator
  • Unfortunately I am having to do that already as nothing else is helping me. The logs from App-V have no useful information.I am more interested in finding out what those error messages mean and whats causing them. What if that happens on vanilla build as well. BTW, our SOE is just a vanilla Windows 7 wim with unattended file. No Sysprep and no image capture...
    Vithal Maddala
    Sunday, August 28, 2011 11:46 PM
  • Ok. I built a vanilla Windows 7 Enterprise x64 SP1 machine - No VMWare drivers etc. It does not work. I am still getting the same error. No go. Is it an issue with App-V and Windows 7 SP1? Not sure. I might log a case with premier support.
    Vithal Maddala
    Monday, August 29, 2011 12:36 AM
  • Hello,

    A vanilla Windows 7 x64 SP1 enterprise machine should work without issues if using the x64-bits of the release of App-V. As Aaron stated you could try a newer version (not sure if the version you posted is the latest or not), however perhaps you could try a different HW base as a far step


    /Znack
    Monday, August 29, 2011 5:56 AM
  • Vithal,

    Were you ever able to resolve this issue? I am experiencing the exact same problem.

    Friday, November 4, 2011 2:10 PM