locked
Getting error 4505CD-16D1100A-0000E005 launching previously working apps RRS feed

  • Question

  • We're currently running a pilot of App-V using App-V 4.5 with SCCM 2007 R2 using download and execute to deliver the virtualised apps to Win XP SP2 machines.

    We're starting to see users getting the following message when they launch a virtualised app:

    ---------------------------
    Application Virtualization Error
    ---------------------------
    The Application Virtualization Client could not launch FileZilla 3.2.2.1.

    An unexpected error occurred. Report the following error code to your System Administrator.

    Error code: 4505CD-16D1100A-0000E005
    ---------------------------
    OK  
    ---------------------------

    This sometimes happens for users that have been using that app ok for a few weeks, and sometimes occurs the first time a user tries to launch an app. Either way once they've had the error that app won't work again. Other virtualised apps on the same system do work with no problem before and after the problem occurs.

    You get the following errors in the sftlog.txt:

    [05/12/2009 15:18:07:406 JGSW ERR] {hap=12:app=FileZilla 3.2.2.1:tid=428:usr=xxxxxxxx}
    The Application Virtualization Client could not connect to stream URL 'FILE://C:\WINDOWS\system32\CCM\Cache\SOL0002C.2.S-1-5-21-1393408613-3259354127-3638037492-9657\SOL0002C.sft' (rc 16D1100A-0000E005, original rc 16D1100A-0000E005).


    [05/12/2009 15:18:07:422 SWAP ERR] {hap=12:app=FileZilla 3.2.2.1:tid=428:usr=xxxxxxxx}
    The client was unable to connect to an Application Virtualization Server (rc 16D1100A-0000E005)


    [05/12/2009 15:18:07:437 TRAY ERR] {tid=1530:usr=xxxxxxxx}
    The Application Virtualization Client could not launch FileZilla 3.2.2.1.

    An unexpected error occurred. Report the following error code to your System Administrator.

    Error code: 4505CD-16D1100A-0000E005

    (have x'd out user name)

    And a set of matching messages in the system's application event log.

    The stream URL it complains that it can't connect to does exist on the local machine and dopes appear to have all of the correct files in it. In the App V Console on the local machine the app shows as not locked and status is "Idle (100%)".

    Have tried a number of things to fix this problem, starting with a reboot and then moving on to using the Repair function in the AppV console (as per KB930623), most other troubleshooting on this sort of thing on the web seems to assume you're using App-V without SCCM and doesn't seem to apply here. Have checked the RequireSecureConnection registry key and it is set to 0 (as suggested on another post here). Also have removed the user from the collection in SCCM, cleared the app from the local machine (with the Clear option in the client) and then (after waiting a suitable time) re-added them to the collection. Once the app reappears on the machine, get the same problem again.

    Does anyone have any suggestions?
    Wednesday, May 13, 2009 1:23 PM

Answers

  • In our case 4.5 was the first version we looked at, so nothing we have was sequenced with anything less than the 4.5 sequencer.

    For what it's worth the problems described above disappeared when we moved to 4.5 SP1, and definitely haven't been seen at all since we upgraded the App-V clients to v4.6 a few months ago.

     

    • Proposed as answer by znack Friday, June 4, 2010 12:49 PM
    • Marked as answer by Aaron.ParkerModerator Saturday, November 17, 2012 1:27 PM
    Tuesday, June 1, 2010 10:21 AM

All replies

  • Hello,

    Have you tried deleting the entire user-profile?
    Have you tried deleteing application specific file? (see note below)
    This problem may occur because your personal settings file (UsrVol_sftfs_v1.pkg) is corrupted. This file is in the following folder:
    %appdata%\SoftGrid Client\Package
    Note Package is a placeholder for a folder whose name varies depending on the program that you have installed.

    /Znack
    Wednesday, May 13, 2009 1:26 PM
  • Yes I've deleted the personal settings file from %appdata%\SoftGrid Client\ (and I think this is one of the things the client's repair function does?). Have also totally emptied the Softgrid Client folder. Neither of these have helped.

    Will try deleting the entire user-profile.
    Thursday, May 14, 2009 10:28 AM
  • Hello,

    Can other users on the same machine launch the application?

    /Znack
    Thursday, May 14, 2009 10:42 AM
  • One of our customers is receiving the same error message:

     

     The Application Virtualization Client could not launch *******.  An unexpected error occurred. Report the following error code to your System Administrator.  Error code: 4505CD-16D1100A-0000E005

     

    Environment - Server 2003 TS. Client version - 4.5.

    Scenario how this happened to a working package:

    Package has been made with 4.2 Sequencer. After update request it has been upgraded with 4.5 sequencer and made available to users. After testing users reported that vital application functionality is missing (.dll errors, application crashes when trying to access a specific program feature).

    Immediate solution was to roll back to an older version. Newer version has been removed from softgrid server and the error started showing up.

    As the previous poster mentioned, I've tried all the basic steps to solve the issue:

     

    1. full clear of user's cache 
    2. deleting a package from server's cache
    3. restarting sg client service
    4. resetting softgrid client cache to a clean state on that server (surprisingly, this was though to fix the issue, but after a while it comes back again, I am unable to determinate the logic behind this one)

    Any suggestions you might have are very welcome as this is causing a lot of incovenience. None of the users are able to access the package on the affected servers.

    The only solution I see now would be making a package from scratch on a 4.5 sequencer or branching the existing 4.2 package to roll out "mysterious corruption" issues with this specific package.

     


     

    Monday, May 31, 2010 6:51 AM
  • In our case 4.5 was the first version we looked at, so nothing we have was sequenced with anything less than the 4.5 sequencer.

    For what it's worth the problems described above disappeared when we moved to 4.5 SP1, and definitely haven't been seen at all since we upgraded the App-V clients to v4.6 a few months ago.

     

    • Proposed as answer by znack Friday, June 4, 2010 12:49 PM
    • Marked as answer by Aaron.ParkerModerator Saturday, November 17, 2012 1:27 PM
    Tuesday, June 1, 2010 10:21 AM