App-V client generates "Could not connect to stream URL" error


Here's another issue uncovered by our very own Steve Thomas during the App-V 4.5 beta, this one involving a misleading error you might get if the client cache is full:


Issue: When an application is unable to load because the cache is full, you may receive the following error:

Could not connect to stream URL

Note that you may not get an error for the first application launch but you will for subsequent launches.

The sftlog.txt on the client will also show something along the lines of the following:

The package {E8DA6D01-2526-44D8-B7AA-FDD8095F5563} could not be locked in cache because there is not enough unallocated space (219872 Kb needed, 92160 Kb limit).

Could not set lock status to TRUE

[03/06/2008 18:31:10:611 SWAP ERR] {hap=1:app=AR8 Adobe Reader 8 (Vis.45) 8.06E01E:tid=EF0:usr=local_user}
Could not load app

There is not enough space in the Application Virtualization cache. Report the following error code to your System Administrator.

Error code: 4504B4-16D10E0A-0000E029

Note: You will have to have Verbose logging set on the client to observer this error in the SFTLog.txt.  The Verbose logging level on the client is set under the Properties of 'Application Virtualization' here:


Cause: Although the error code that appears in the customer-facing dialog box is incorrect, the correct error code appears in the log as 0000E029.

Resolution: The resolution is probably obvious but I'll go ahead and say it anyway.  You either need to remove apps that are locked in the cache or make the cache larger.  This is also set under the Properties of 'Application Virtualization' on the client:



Thanks Steve!

J.C. Hornbeck | Manageability Knowledge Engineer

Comments (5)

  1. Anonymous says:

    Feed: The App-V Blog Posted on: Monday, February 02, 2009 9:16 AM Author: jchornbe Subject: App-V client

  2. Martin upper says:

    This kind of errors also report to the eventlog if the User doesn’t have sufficiant rights to access his App-V userdata folder.

    This might happen if you delete an AD-user and create a new AD-user with the same name. App-V user data folder will still exist for the name, but because the SID changed, the user will not have access to the folder. No new user data folder will be created by App-V because it only looks for the name.

  3. Ram Karthik says:

    Can I know how I can get the UI shown above?

  4. SAI says:

    @ Ram


    In the Run command, type "SftCMC.msc" to open the UI

  5. ExchAdminInd says:

    Thanks for this post. I was able to fix my issue.

Skip to main content