App-V 5.0 Sequencer - Sequencer not responding/Apps not available RRS feed

  • Question

  • Has anyone had any applications where the sequencer stops responding and/or where applications are not available for launch in the GUI when working through the sequencing process.  On the occasion where the sequencer stopped responding, the event log on the sequencer shows ingredients.xml being created as an information message, then nothing else.  We have one application where the sequencer stops responding at the point after installation where the sequencer captures changes, the same application sequenced correctly using the Powershell cmdlet rather than the GUI, but did not launch successfully on the client, and when opening for update afterwards to customize settings the main application would not launch, error - side by side configuration incorrect.  Another application sequenced but the programmes were not available to be launched after capturing the changes.  Both applications worked successfully with App-V 4.6 SP2, converted to v5 without any errors/warnings, but the converted package did not successfully launch on the client so re-sequencing is necessary if we are to continue with App-V 5.0.
    Thursday, April 18, 2013 10:50 AM

All replies

  • Hello,

    I have only seen it when system components have been installed, but without knowing what your installer does its hard to give any suggestions

    Nicke Källén | The Knack| Twitter: @Znackattack

    Thursday, April 18, 2013 12:54 PM
  • The main app mentioned above uses 5 com+ components, and also 2 services, and an ODBC connection.  I know com+ is listed under the sequencing limitations for v4.6 and v5.0, but sequencing with 4.6 SP1 was successful, and after publishing, the users have been happy with functionality.  Both the AppV 4.6 and 5.0 VM's have a dummy ODBC connection.  Have also sequenced another application that gave a com+ warning at the end of sequencing, the sequencing process completed without the sequencer going into a no-responsive state.  In your experience would the com+ components have caused the non-responsive state?  Currently, if we can't sequence this application, we will have to hold off on app-v 5 for a while until another method of distributing this application has been found.  Thanks for your help. 
    Thursday, April 18, 2013 2:10 PM