locked
Microsoft App-V 4.6 Read only cache wait before apps can be started RRS feed

  • Question

  • We are using RO cache (4.6) on WinXP sp3 deployed with VMWare View. We have a cache growing over 50GB. problem is that it takes about 5min before users can start there apps. sftlist process in running with high use of processor. after sftlist is ready users can access there apps. Is there a way to decrease this time. the RO cache is on a SAN.

    I presume it's a known issue with large cache?!

    My guess is the sftlist is indexing the cache, but is there a workarround for this problem except using local cache (or worst case scenario) creating multiple caches. 

     thanks for your reply

      

     


    Monday, August 22, 2011 2:36 PM

Answers

  • Problem was probably a bad install of app-v client 4.6 with SCCM2007, a clean install did the trick. The bad install was using verbose logging.

    we changed logging option (standard):

    LogMinSeverity: 2

    SystemEventLogLevel:0

     

    we reduced sftlist.exe time running at logon from 7-10 min to under 2 min. the used account had permissions on over 300 apps.

    goiong to make a new install of the app-v client 

    • Marked as answer by DJG78 Thursday, October 27, 2011 8:40 AM
    Thursday, October 27, 2011 8:39 AM

All replies

  • What is the method of publishing your packages to the user? e.g. Management Server, SFTMIME etc. Does the issue occur if a user has access to only 1 application?

    Have you tested with 4.6 SP1 hotfix 3 or 4? It might also be worth testing in a later version of Windows; however I presume that might involve a lot of work.

    You might be best opening a call with Microsoft PSS to assist with troubleshooting.



    This forum post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.
    Wednesday, August 24, 2011 10:27 AM
    Moderator
  • try disabling the autoload triggers:

     

    http://blog.zarb.co.uk/2011/08/app-v-tip-of-day-2-shared-cache-delays.html


    Steve Thomas, SSEE, Microsoft
    App-V/MED-V/SCVMM/SCCM/AppCompat
    http://madvirtualizer.wordpress.com/
    The App-V Team blog: http://blogs.technet.com/appv/
    The MED-V Team Blog: http://blogs.technet.com/medv
    The SCVMM Team blog: http://blogs.technet.com/scvmm/

    “This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all risks.”
    • Proposed as answer by znack Tuesday, August 30, 2011 8:17 AM
    Friday, August 26, 2011 9:54 PM
  • What is the method of publishing your packages to the user? e.g. Management Server, SFTMIME etc. Does the issue occur if a user has access to only 1 application?

    Yes, it still hapens when user has access to only 1 app. the problem is only at logon. after sftlist is ready it works perfectly. I think it sftlist is checking cache, when app is found in cache app can be started.

    Have you tested with 4.6 SP1 hotfix 3 or 4?

    No we haven't tested with hotfix 3 or 4

    It might also be worth testing in a later version of Windows; however I presume that might involve a lot of work.

    We have tested on win7 (small scale, but no improvements)

    try disabling the autoload triggers:

    i will test this, we have autoloadtrigger at value 5 (default). AutoLoadTarget at 0

    thank you so far. i will let you know if i'm ready testing


    • Marked as answer by DJG78 Thursday, October 27, 2011 8:40 AM
    • Unmarked as answer by DJG78 Thursday, October 27, 2011 8:40 AM
    Tuesday, August 30, 2011 11:07 AM
  • this all didn't helpt yet.

    we are going to try with hotfixes

    • Marked as answer by DJG78 Thursday, October 27, 2011 8:31 AM
    • Unmarked as answer by DJG78 Thursday, October 27, 2011 8:31 AM
    Tuesday, September 13, 2011 9:18 AM
  • Problem was probably a bad install of app-v client 4.6 with SCCM2007, a clean install did the trick. The bad install was using verbose logging.

    we changed logging option (standard):

    LogMinSeverity: 2

    SystemEventLogLevel:0

     

    we reduced sftlist.exe time running at logon from 7-10 min to under 2 min. the used account had permissions on over 300 apps.

    goiong to make a new install of the app-v client 

    • Marked as answer by DJG78 Thursday, October 27, 2011 8:40 AM
    Thursday, October 27, 2011 8:39 AM