none
App-V 5 SP3 Client Not Displaying Any Applicatons since changing our local gateway IP Address RRS feed

  • Question

  • We changed our gateway and the next day after rebooting all our servers the App-V Client has stopped downloading and displaying all applications, this is the only change we have made since the problem began.

    I followed the MS Troubleshooting guide: "How to troubleshoot publishing server refresh failures" https://support.microsoft.com/en-us/kb/2778168

    Everything is Ok on this list.

    This affects all servers using the App-v Client.

    We checked firewalls are off for now on all appv server roles.

    The App-V Client service is running.

    We receive this error when running a get-appvclientpackage in powershell for a particular application:

    Get-AppvClientPackage : Application Virtualization Service failed to complete requested
    operation.
    Operation attempted: Get Packages.
    AppV Error Code: 0600000011.
    Error module: Catalog. Internal error detail: 86B0AD0600000011.
    Please consult AppV Client Event Log for more details.

    Applications still run Ok.





    • Edited by daeus Tuesday, August 25, 2015 10:12 AM Correction on facts
    Friday, August 21, 2015 11:55 AM

Answers

  • Ok well some of our packages were converted 4.6 Packages.

    It seems using the below commands to grab the failing packages manually works:

    Add-AppvClientPackage
    Publish-AppvClientPackage

    This could be a separate issue to the issue I originally raised howerver.

    • Marked as answer by daeus Wednesday, August 26, 2015 3:22 PM
    Wednesday, August 26, 2015 3:22 PM

All replies

  • Ok some errors:

    cmdlet Sync-AppvPublishingServer at command pipeline position 1
    Supply values for the following parameters:
    ServerId: 1
    Sync-AppvPublishingServer : There were various errors encountered when trying to synchronize from the server.
    Operation attempted: RefreshPublishingServer.
    AppV Error Code: 070000001E.

    Friday, August 21, 2015 1:08 PM
  • So step 6 (Perform a publishing server refresh) from that website is failing, are you sure step 5 is OK? You can browse to the publishing server site from your client (and actually get the list with entitled packages)?
    Friday, August 21, 2015 1:22 PM
  • So yes we can view our XML file from any client machine http://appvpublish:82

    Friday, August 21, 2015 1:35 PM
  • Your initial indication of the problem seems to indicate that it has nothing to do with publishing, but something else is the issue.  So there are two possible directions you might need to go.

    In the case of publishing is OK but this get on one package on one client is the issue, if you have not done so you should try removing and re-adding the offending package.  If the "get" can't work, that may be a problem, and full client uninstall/reinstall may be required.  All of which sounds independent of changing out the gateway.  The only gateway related issue in that scenario might be that the problem is the URI of that published package, and you need to troubleshoot that URI back to the package store.

    (For completeness I'll also add that if this is XenApp with PVS and the local App-V cache is on the D drive, the issue is only that you rebotted the XenApp server without clearing out the cache.  The removal of the cache folder from the D drive is a must in that scenario).

    If the information in these latest replies is correct (Step 5 OK but step 6 fails with a publishing error) then you need to debug the publishing protocol.  Start looking at the publishing server event logs for App-V, and probably the IIS log also.  You may need to break out wireshark.  I have only seen something similar when it was certificate issues, but you haven't mentioned https yet.

    Tim


    Tim Mangan MVP for App-V and Citrix CTP Author of AppV books: "The Client Book" and "OSD Reference Book" (http://www.tmurgent.com/Books )

    Saturday, August 22, 2015 12:43 PM
    Moderator
  • Thank you for your reply. We are not using PVS on these test XA, we are Full-Caching Apps currently and will possibly also use this mode on our PVS images once all applications are ready.

    We are using a Netscaler to Loadbalance two App-V Publishing servers, the LB Address and both individual Publishing servers return the XML Packages List correctly when browsed.

    We have reinstalled the AppV Client on several XAs.

    We have rebooted the XA's affected.

    We have deleted this registry key on the servers running the Appv Client as this fix relates to the same error:
    https://social.technet.microsoft.com/Forums/en-US/f88bc1f6-569e-4c63-8343-bf676a1257f3/appv-5-part-or-all-packages-publish-failed?forum=mdopappv

    We have added all App-V Server roles to a security group and added it for read access to the Published DFS Content Folder in relation to the same error:
    http://www.jsconsulting.services/2015/04/appv-5-publishing-error-0x74f00f0c/

    For trying to Remove or Add App-V packages using the below commands, we also get the below errors.

    Get-AppvClientPackage -All | Remove-AppVClientPackage

    Get-AppVPublishingServer | Sync-AppvPublishingServer

    Part or all packages publish failed.
     published: 0
     failed: 32
    Please check the error events of 'Configure/Publish Package' before this message for the details of the failure.

    Following the above error we receive an error for each of the 32 failed packages or connector group packages:

    Package {a6f03afd-3f36-4452-bf5e-3158b551fdcd} version {6fc929ab-16d8-4f77-bdab-84881464866e} failed configuration in folder 'C:\ProgramData\App-V\A6F03AFD-3F36-4452-BF5E-3158B551FDCD\6FC929AB-16D8-4F77-BDAB-84881464866E' with error 0xA040132A-0x3.

    and:
    Mandatory package {a6f03afd-3f36-4452-bf5e-3158b551fdcd}, version {6fc929ab-16d8-4f77-bdab-84881464866e} specified in connection group {17216ce9-f0e6-411b-8307-cc8d0ebce838}, version {337ed68f-0bab-4d9a-8792-9a323c43b3f5} has not been added to the computer or has not been entitled to the user.

    Tuesday, August 25, 2015 11:57 AM
  • Re the above error "Failed configuration in folder" I tried re-creating all the local folders since being removed by the remove command, as the registry entries for them still existed using this advice but I still receive the same errors.

    http://trentent.blogspot.co.uk/2015/03/appv5-package-failed-configuration-in.html

    Tuesday, August 25, 2015 12:18 PM
  • We setup the Client on another XA and applications are now displaying.

    I will confirm what we find was the cause once we can.
    Tuesday, August 25, 2015 2:41 PM
  • Package {a6f03afd-3f36-4452-bf5e-3158b551fdcd} version {6fc929ab-16d8-4f77-bdab-84881464866e} failed configuration in folder 'C:\ProgramData\App-V\A6F03AFD-3F36-4452-BF5E-3158B551FDCD\6FC929AB-16D8-4F77-BDAB-84881464866E' with error 0xA040132A-0x3.

    0x3 means it can not find the path specified. Try to manually add a package through Http or UNC directly from the load balancer address (and/or from each publishing server).
    Also did you perform a full removal locally on your XA (through PS: get-appvclientpackage -all | remove-appvclientpackage?

    Tuesday, August 25, 2015 10:22 PM
  • Tiberivs I will check your notes and confirm, I will also digg out online a good source for errors codes online.

    Our new XenApp servers with the AppV client 5 sp3 are actually still receiving these errors still but less so, 8/32 of our packages are failing with the errors below.

    Our Packages have not moved and permissions on the DFS content store shares have not been changed.

    Error 1:
    Part or all groups publish failed.
     published: 6
     failed: 1
    Please check the error events of 'Configure/Publish Virtual Application Connection Group' before this message for the details of the failure.

    Error 2:
    Package {711ececd-3e51-4f70-997c-fa797192eed0} version {94f9b49f-3557-4407-9c66-6e11dc84f480} failed configuration in folder '' with error 0x74F00F0C-0x80070005.

    Error 3:

    Failed to publish group due to the failure of the package.
     Group GUID: {3f268f88-8eee-4ec2-bbe2-92d81611e1a8}
     Group Version GUID: {6fe0747a-c4e0-41f0-ba80-65f47feef6d4}
     Package GUID: {711ececd-3e51-4f70-997c-fa797192eed0}

    Wednesday, August 26, 2015 3:06 PM
  • Ok well some of our packages were converted 4.6 Packages.

    It seems using the below commands to grab the failing packages manually works:

    Add-AppvClientPackage
    Publish-AppvClientPackage

    This could be a separate issue to the issue I originally raised howerver.

    • Marked as answer by daeus Wednesday, August 26, 2015 3:22 PM
    Wednesday, August 26, 2015 3:22 PM