locked
Some users get the following error when starting a specific app-v package: 0A-0000E005 RRS feed

  • Question

  • Hi everyone,

    We are using app-v 4.5 Version: 4.5.3.19480 on a terminal server 2003 farm.

    For the past few days our users are getting the following errors when they start a certain app-v package:

    The client was unable to connect to an Application Virtualization Server (rc 16D1120A-0000E005)

    The app-V client logfile shows the following error:

    [05/07/2012 14:54:08:995 JGSW ERR] {hap=37A:app=App 01:tid=1654:usr=xxxx}
    The Application Virtualization Client could not connect to stream URL 'RTSP://appvserver:554/01686-01/01686-01_4.sft' (rc 16D1120A-0000E005, original rc 16D1120A-0000E005).

    [05/07/2012 14:54:09:011 SWAP ERR] {hap=37A:app=App 01:tid=1654:usr=xxx}
    The client was unable to connect to an Application Virtualization Server (rc 16D1120A-0000E005)

    The server logfile shows no errors at all.

    I can't reproduce this error on my admin and test account on the same terminal servers some users are having the problems.

    As far as I can tell the following occurs:

    1) User start application.
    2) the pkg and .tmp files are generated in the App-V global date directory.
    3) User closes application.
    4) tmp files in the app-v global data directory do not get deleted.
    5) User start the same application again and then receives the error.

    Process Explorer reports that the .tmp files are still opened by the system proces (svchost.exe). When I close handles the system process has to the .tmp files and then delete the .tmp files the users can start the application again. However when they shut down the application and try to start it again they receive the error once again.

    This problem does not seem to occur for all users. I have tried removing the app-v cache user cache and even deleting the entire profile but this does not seem to make any difference.

    Any idea what could be causing this error?


















    Monday, May 7, 2012 9:56 PM

Answers

  • Hi,

    Thanks for the links. Found those documents already with some googling. Unfortunately they didn't help me resolve the issue.

    We ended up resequencing the application to resolve the error. After talking to the packagers I noticed they were using app-v 4.6 to sequence apps for the 4.5 clients and then changing the client dependency in the osd files.

    I suppose that was the reason for the strange problems we have been experiencing to so I asked them to not do this anymore.

    Thanks for the help troubleshooting guys.

    Friday, May 11, 2012 8:03 AM

All replies