locked
App-V 5.0 SP2 upgrade to HF4 and 5 fail RRS feed

  • Question

  • Hi Everyone, 

    Issue:

    Applications fail to launch after Hotfix 4 or 5 for App-v 5.0 SP2 for RDS has been applied.  The machine has been rebooted after the installation.  Before the patch all virtualized applications would launch and work.

    Error details: 

    Following is the error pop-up when I try to launch virtual Excel:

    • Problem signature:
        Problem Event Name: APPCRASH
        Application Name: EXCEL.EXE
        Application Version: 15.0.4667.1000
        Application Timestamp: 543d366c
        Fault Module Name: ntdll.dll
        Fault Module Version: 6.1.7601.18229
        Fault Module Timestamp: 51fb1072
        Exception Code: c0000005
        Exception Offset: 0002e066
        OS Version: 6.1.7601.2.1.0.16.7
        Locale ID: 1033
        Additional Information 1: 7b3b
        Additional Information 2: 7b3bff76da6c751effaa3f1e8a07e6e2
        Additional Information 3: 2f91  Additional Information 4: 2f919c290779e890064098ded6ee81ad

    • Read our privacy statement online:
        http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

      If the online privacy statement is not available, please read our privacy statement offline:
        C:\Windows\system32\en-US\erofflps.txt

    I get the same ntdll.dll fault module name when I try any other application (like acrobat 11) When I look in the App-v event log I see an error stating:

    1. A virtual application could not be launched from package '' because the App-V Client Service is not running.  Start the App-V Client Service and try again.

    The Microsoft App-V Client service is running(and I restarted it for good measure)

    Troubleshooting:

    • Reboot machine
    • Repair install of hot fix
    • Restart Service
    • Remove, then remount and publish ap
    • scour internet for answers

    Machine config:

    Server 2008 R2 Standard

    Citrix Xenapp 6 installed 

    VM running on ESXi

    Office package was sequenced using the ODT tool

    Acrobat sequenced on 32 bit machine with unpatched 5.0 SP2 sequencer 

    Summary:

    Please let me know if you have seen this or have any ideas on what the cause could be.

    Thanks in advance, 

    Chris



    • Edited by cslish Wednesday, December 3, 2014 8:19 PM
    Wednesday, December 3, 2014 8:14 PM

Answers

  • I figured out what was happening.  The packages I was testing (acrobat 11 and office 2013) had both been reopened and modified in the SP2 sequencer.  

    I was able to launch packages, that were built with the SP2 sequencer but required no VFS or registry changes.

    Now re-sequencing Acrobat to test.


    Thanks

    • Marked as answer by cslish Thursday, December 4, 2014 7:38 PM
    Thursday, December 4, 2014 7:38 PM

All replies

    • Edited by Ben De Vriese Wednesday, December 3, 2014 9:00 PM Added blog post link
    Wednesday, December 3, 2014 8:58 PM
  • Hi Ben, 

    I found VC++ was already installed on the machine, but ran the repair utility to be sure.  After reboot I installed HF4, rebooted again, and get the same issue.

    Any other thoughts?


    Thanks

    Wednesday, December 3, 2014 9:41 PM
  • Are you sure redist 2013 is installed. This is a new requirement after hotfix4.
    Thursday, December 4, 2014 9:37 AM
  • Removed and re-installed redist VC++ 2013 for good measure.  Still no joy.  I even went as far to install both the x86 and x64 versions. 

    What is really striking me as odd is the App-v event log:

    A virtual application could not be launched from package '' because the App-V Client Service is not running.  Start the App-V Client Service and try again.

    It is clearly running and generates NO errors when the service is restarted.

    I applied SP4 to a server 2012r2 machine in my lab and had no issues.





    • Edited by cslish Thursday, December 4, 2014 4:03 PM
    Thursday, December 4, 2014 4:02 PM
  • I figured out what was happening.  The packages I was testing (acrobat 11 and office 2013) had both been reopened and modified in the SP2 sequencer.  

    I was able to launch packages, that were built with the SP2 sequencer but required no VFS or registry changes.

    Now re-sequencing Acrobat to test.


    Thanks

    • Marked as answer by cslish Thursday, December 4, 2014 7:38 PM
    Thursday, December 4, 2014 7:38 PM
  • Try the SP3 sequencer, it's available!

    Friday, December 5, 2014 1:37 PM