locked
Issues using Add-AppvClientPackage cmdlet on App-V 5 SP1 RDS Client with Java Package RRS feed

  • Question

  • I'm posting this issue with full knowledge that it has been posted in various other post on this, and other, forums in the past. It has, at least to my knowledge, not been sufficiently answered as of yet and it has become something of a thorn in my side. I'll begin with what I'm attempting to achieve.

    I need to package older versions of Java (in this case 1.6.0_06) that are required by some of the legacy applications (mostly various web applications) in use in my environment. Until now, we have achieved this goal in App-V 4.6 by sequencing the necessary version of Java along with a custom desktop shortcut to IE that loads the website with the correct version of Java. This works perfectly when publishing the application via SCCM directly to the client. However, we have been recently asked to investigate publishing those virtual packages to a RDS farm to enhance availability, particularly on tablet devices. To test this, we built a simple RDS farm on Server 2012 Datacenter (1 session host, 1 connection broker, 1 web access), installed the RDS App-V 5 client (version 5.0.1104.0) on the session host, and sequenced and published a few basic test applications (TextPad for example) with great success. We then turned our sights to one of the Java App-V 4.6 packages. We upgraded the packages to 5.0 with the sequencer cmdlets and the package worked successfully on the client at first. We then attempted to publish the package with the -Global flag for use with RemoteApp and it encountered the following error:

    Publish-AppvClientPackage : Application Virtualization Service failed to complete requested operation.
    Operation attempted: Publish AppV Package.
    Windows Error: 0x5 - Access is denied
    Error module: Integration Manager. Internal error detail: 9570262100000005.
    Please consult AppV Client Event Log for more details.
    At line:1 char:1
    + Publish-AppvClientPackage -name ADP -global
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidResult: (:) [Publish-AppvClientPackage], ClientException
        + FullyQualifiedErrorId : PublishPackageError,Microsoft.AppV.AppvClientPowerShell.PublishAppvPackage

    Digging in event viewer revealed the following:

    We surmised that the way the package was sequences was attempting to access a protected area of the registry when published as global, thus causing the access denied error. We decided to attempt sequencing Java as a standalone package instead. We thought we could leverage the RunVirtual feature of App-V 5 to make it work the way we need it to. We sequenced Java 1.6.0_06 and attempted to run the Add-AppvClientPackage cmdlet and encountered the following error:

     Add-AppvClientPackage : Application Virtualization Service failed to complete requested operation.
    Operation attempted: Configure AppV Package.
    AppV Error Code: 0C80070057.
    Error module: Streaming Manager. Internal error detail: 4C401C0C80070057.
    Please consult AppV Client Event Log for more details.
    At line:1 char:1
    + Add-AppvClientPackage -Path "\\ms-eagle86\AppVPackages\Java\Java 6u6.002\Java 6u ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidResult: (:) [Add-AppvClientPackage], ClientException
        + FullyQualifiedErrorId : ConfigurePackageError,Microsoft.AppV.AppvClientPowerShell.AddAppvPackage

    This was accompanied the following errors in event viewer:

    I have a feeling the error is related to Java for the following reasons:

    1. Before encountering the error I was able to publish different applications without issues.
    2. Since first encountering the error, I was able to publish different applications without issues.
    3. Since publishing different applications after receiving the error, I still receive the error on this package and other Java packages.
    4. I have created a number of different Java packages with various settings (as application, plugin, middleware, registry settings based on advice from other forum posts, etc.) and all of them fail with the same errors.

    To troubleshoot the error further, I ran Process Monitor while executing the cmdlet and found the following entry

    Process Name: AppVClient.exe
    Operation: <Unknown>
    Path: C:\ProgramData\App-V
    Result: INVALID PARAMETER

    I focused on this line because the final error above references an incorrect parameter.  This line is in a group of operations where it appears to be writing to the App-V folder.

    Currently, I'm at a loss as to what the problem is or how to move forward with the troubleshooting. Any help that anyone can offer would be greatly appreciated.

    I have place all files that I feel may be relevant to the troubleshooting including the event log entries and process monitor output here

    Wednesday, May 8, 2013 6:26 PM

Answers

  • I have cracked this one finally! I must say, there is a lot to be said for reading documentation sometimes. I was re-reading the App-V 5.0 Sequencing Guide this morning in hopes that I might find the nugget of truth in this whole matter. Chapter 2 states

    "It is often possible to sequence on one OS and run the virtualized application on a different OS; however this scenario is both application- and OS-dependent and is not guaranteed to work for all application/OS combinations since App-V is not a general-purpose OS compatibility solution. If problems are encountered, the application may require sequencing on the same OS environment that the App-V Client is running on in order to resolve those problems."

    There you have it. I built a Windows 2012 VM and used it to sequence the package and it worked like a champ. I'm not sure what the issue was exactly, but that proved to be the solution for me.

    • Marked as answer by Dennis Baker Thursday, May 9, 2013 7:10 PM
    Thursday, May 9, 2013 7:10 PM

All replies

  • Hello,

    Are there any other errors in any other App-V Logs?


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

    Thursday, May 9, 2013 6:14 PM
  • I haven't noticed any, but if you have another place for me to look, I'm open to suggestions.
    Thursday, May 9, 2013 6:21 PM
  • I have cracked this one finally! I must say, there is a lot to be said for reading documentation sometimes. I was re-reading the App-V 5.0 Sequencing Guide this morning in hopes that I might find the nugget of truth in this whole matter. Chapter 2 states

    "It is often possible to sequence on one OS and run the virtualized application on a different OS; however this scenario is both application- and OS-dependent and is not guaranteed to work for all application/OS combinations since App-V is not a general-purpose OS compatibility solution. If problems are encountered, the application may require sequencing on the same OS environment that the App-V Client is running on in order to resolve those problems."

    There you have it. I built a Windows 2012 VM and used it to sequence the package and it worked like a champ. I'm not sure what the issue was exactly, but that proved to be the solution for me.

    • Marked as answer by Dennis Baker Thursday, May 9, 2013 7:10 PM
    Thursday, May 9, 2013 7:10 PM