Application Virtualization TechCenter > Microsoft Application Virtualization (App-V) Forums > App-V Clients > Error Code 4505CD-0EC05E0C-0000003C after upgrade to App-V 4.5 Terminal services client.
Ask a questionAsk a question
 

Proposed AnswerError Code 4505CD-0EC05E0C-0000003C after upgrade to App-V 4.5 Terminal services client.

  • Tuesday, November 04, 2008 11:57 PMKim Morgan Ellis Fiva Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hi.

     

    After I've upgraded a couple of clients to test the App-V 4.5 client I'm not able to start all the applications. Some work, but I have one that failes before the script is run.

     

    I've reooted, flushed the cache, moved the cache, reinstalled the client, but nothing helps. I've also searched for this error code but I'm not able to find a solution that fits.

     

    We need to upgrade to App-V 4.5 as soon as possible, but I need to resolve this problem first.

     

    We are running the client on Windows 2003 SP2 Terminal services.

     

    The application works fine with 4.1.3.15 version of the client, the package I try to start is sequenced with 4.2.2.15 (RTM) version of the sequencer.

     

     

    ------------------------

    sftlog.txt with verbose logging. :

     

     

    [11/05/2008 00:49:32:271 ???? INF] {tid=18E8:usr=usertest}
    Starting sort of older Sec9.


    [11/05/2008 00:49:32:376 ???? ERR] {tid=18E8:usr=usertest}
    CSuite::InternalUpload failure  ec05e0c-      3c while uploading Virtual Filesystem


    [11/05/2008 00:49:32:391 SWAP INF] {hap=34:app=Visma Global STDVC730.1 7.30.2246.0:tid=18E8:usr=usertest}
    Elapsed time for upload: 0.328 seconds


    [11/05/2008 00:49:32:406 TRAY ERR] {tid=1620:usr=usertest}
    The Application Virtualization Client could not launch Visma Global STDVC730.1 7.30.2246.0.

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

    Error code: 4505CD-0EC05E0C-0000003C

     

    ------------------

All Replies

  • Thursday, November 06, 2008 10:08 AMgjtje Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Proposed Answer
    Did you try to save the package from a 4.5 sequencer? We're re-sequencing all applications because we noticed many do not work when upgrading to 4.5 from 4.1.
    Most are fixed by just going through the sequencing process without changing anything.
  • Thursday, November 06, 2008 10:21 AMKim Morgan Ellis Fiva Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    That is an option, but we have 950+ packages so it's quite a heavy job.

     

    Did you get any other problems upgrading from 4.1 to 4.5?

     

     

    Kim

     

  • Thursday, November 06, 2008 11:28 AMgjtje Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    We haven't upgraded yet, we're still preparing all updates packages. Smile
    In the test area I didn't find any problems, applications seem to start and run a lot faster but that could be placebo too. 
  • Tuesday, December 09, 2008 10:02 AMhegi55 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Might be interesting to you all..

     

    I have receiced the same error message, CSuite::InternalUpload failure  ec05e0c-      3c while uploading Virtual Filesystem, on a new sequenced package.

     

    The solution offered from the MS Knowledge Base and MS Blogs wasn't helpful, because the application run on a new clean machine.

     

    Solution:

    The Sequencer put a mapped network drive, which was needed to run the app correctly, into to package. Running the package on the destination machine crashed after streaming. Because the mapped network drive was then from another user.

     

    bg

    heiko

     

    .. and never give up to find a solution

     

     

     

  • Monday, March 08, 2010 3:47 PMAlphenIT Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi can you please share what you mean by "The Sequencer put a mapped network drive, which was needed to run the app correctly, into to package. "

    Did you find this network item in the registry or was it something you found in the VFS mapping (or both)..?
    I'm currently looking into a similar issue...
    Thanks..!

    Visit my Techblog at http://www.virtualistic.nl
  • Monday, March 08, 2010 6:48 PMznack Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hello,

    Mapped drives (or UNC-paths) are usually located under one of the tabs post-sequencing within the sequencer. Should be fairly easy to spot if you have a look around.

    /Znack
  • Tuesday, March 09, 2010 10:47 AMAlphenIT Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Proposed Answer

    Nope, nothing to be found under the VFS or the Files Tab. I created a  new package, did the installation again but didn't start the application during monitoring and now it's working fine...(Sequencer 4.5.2.17140)

    This was the error I saw in my logs:
    [03/08/2010 16:13:36:171 ???? ERR] {tid=12F8:usr=username}
    CSuite::InternalUpload failure  ec05e0c-      3c while uploading Virtual Filesystem

    [03/08/2010 16:13:36:218 TRAY ERR] {tid=500:usr=username}
    The Application Virtualization Client could not launch Application 10.

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

    Error code: 45246D3-0EC05E0C-0000003C

    [03/08/2010 16:14:48:585 ???? ERR] {tid=144C:usr=username}
    CSuite::InternalUpload failure  ec05e0c-      3c while uploading Virtual Filesystem


    Visit my Techblog at http://www.virtualistic.nl
    • Proposed As Answer byznack Tuesday, March 09, 2010 11:29 AM
    •  
  • Tuesday, March 09, 2010 3:39 PMkirk_tn Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Kim,

    you should test with some failing applications if re-opening them with the 4.5 Sequencer and saving them (without any changes) already solves the issues (since the error points to Virtual File System issues, there is a certain chance it would...)

    If so, you could us the Sequencer's command line options to "bulk re save" your packages

    Falko