none
Issues with app-v 5 hotfix 4

    Question

  • Hello, we are testing the upgrade from app-v 5 sp1 to sp2 with hotfix 4.
    we expierence an issue, after applying hotfix 4 to the client not all applications are published.

    i will explain the situation,
    after applying hotfix 4 everything seems to work fine, but when we remove all packages and then sync with the publishing server not all packages will be published again, in my case on 2 of the 5 packages are published.

    we are using http(s) publishing, when we publish the package with smb there is no issue.

    example https:

    and in the eventviewer the next error appear:
    error 14016:

    The package {73b79dde-518f-4441-a4bb-b91dc2806550} version {789457e0-2cbd-440d-a605-0cf0f8b4f518} could not be mounted because the network connection has been lost or is unavailable.  Check your network connection and try again.

    and error 1008:

    Package {73b79dde-518f-4441-a4bb-b91dc2806550} version {789457e0-2cbd-440d-a605-0cf0f8b4f518} failed configuration in folder 'C:\ProgramData\App-V\73B79DDE-518F-4441-A4BB-B91DC2806550\789457E0-2CBD-440D-A605-0CF0F8B4F518' with error 0x4C40280C-0x80190191.

    the used path is accessible,with sp2 without hotfix 4 there is no issue.

    does someone have a clue what might be the problem?

    Thanks,

    Johnny Bos
    The Netherlands


    • Edited by johnnysidde Wednesday, May 28, 2014 6:44 AM
    Wednesday, May 28, 2014 6:32 AM

Answers

  • I'm currently using SMB.

    I actually swapped from HTTP(S) to SMB for 5.0 SP2 HF4 as it's now the best solution performance wise.

    Have you considered a support ticket with Microsoft? If it was working previously and isn't now perhaps there is something to it. I haven't seen the same issue brought up on these forums. Not that it's the answer, but you may want to reconsider SMB from a performance standpoint..though I believe HTTP is still great from a scalability standpoint.


    PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog: rorymon.com Twitter: @Rorymon

    Thursday, May 29, 2014 4:12 PM

All replies

  • I have not encountered this issue myself. Is this happening on more than one client machine?


    PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog: rorymon.com Twitter: @Rorymon

    Thursday, May 29, 2014 5:13 AM
  • yes this is on multiple windows 7 clients and even on our xenapp 6.5 servers.

    do you use smb or http(s) for streaming?

    Thursday, May 29, 2014 10:18 AM
  • I'm currently using SMB.

    I actually swapped from HTTP(S) to SMB for 5.0 SP2 HF4 as it's now the best solution performance wise.

    Have you considered a support ticket with Microsoft? If it was working previously and isn't now perhaps there is something to it. I haven't seen the same issue brought up on these forums. Not that it's the answer, but you may want to reconsider SMB from a performance standpoint..though I believe HTTP is still great from a scalability standpoint.


    PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog: rorymon.com Twitter: @Rorymon

    Thursday, May 29, 2014 4:12 PM
  • Rorymon thanks for your answer, we are thinking about switching to smb too.
    also because xenapp 7.5 has app-v integration only supported with smb.

    another question, how did you migrate from http(s) to smb was this a manual action deleting and re-importing packages?
    or can it be automated with for example powershell?

    Thanks,

    Johnny Bos

    Monday, June 2, 2014 11:37 AM
  • Hello Johnnysidde,

    I have same problem. I had swapped from HTTP to SMB too after install HF4 or HF5. After roll back to HF2 everythink OK.

    But my configuraion is same as http://social.technet.microsoft.com/Forums/en-US/b8d8724c-465c-48f2-9470-d1f4f5378c97/appv-5-over-https-for-nondomain-clients?forum=mdopappv

    Later I have tryed same configuration on domain computer. Interesting is, when I try in domain computer publishing via HTTP was good HF4 or HF5.


    zdenek.zak@windowslive


    • Edited by zakz Wednesday, July 9, 2014 3:46 PM
    Wednesday, July 9, 2014 3:45 PM
  • To switch from http to smb, there are a few options.

    The easiest and supported method is to use the PackageSourceRoot setting on the client. Here you can enter something like '\\myfileserver\software_packages$\App-V\content'. If you current packages are located under 'http://MyStreamingServer:80/content/', all would be good.

    On the Server side, the only supported method would be to store a package's information (+ user assignments + imported configurations + manually modifed configurations +... maybe others) into a temporary variables, remove and re-add the package using Powershell. To bad: the 'set-appvserverpackage' does not allow to just modify the URI.

    An unsupported (but perhaps also working) method would be to find the URIs in the SQL database and modify them there directly


    Falko

    Twitter @kirk_tn   |   Blog kirxblog   |   Web kirx.org   |   Fireside appvbook.com

    Thursday, July 10, 2014 6:09 AM
    Moderator