locked
"sfttray.exe" deadlock? RRS feed

  • Question

  • When I close all App-V applications, "sfttray.exe" exits.

    When I launch an App-V application before this exit is complete, nothing appears to happen.

    Looking with TaskManager or ProcessExplorer there are 2 "Sfttray.exe" processes.

    Killing the old (exiting) "sfttray" continues the launch of the new application.

    If you try to launch another application during the deadlock, this "sfttray.exe" process throws (after a timeout) following error:

    "The system is too busy to complete the request. If the problem persists, please report it to your System Administrator."

    Anybody know of a solution?

    PC:

    Windows XP SP3

    App-V 4.6 SP1 (with or without hotfixes)

    Friday, July 13, 2012 7:31 AM

Answers

  • Just to circle back - VAPPLauncher is just a wrapper but still encounters the same possibilities as a front-end component in the same manner of VAPPLauncher. The best way to quickly eliminate SEP as an issue (or at least known issues) is to temporarily disengage the SysPlant driver - reboot - and then reattempt the reproduction. It's less of a hassle as opposed to completely uninstalling it.

    The possible causes of this message can sometimes be as simple as excessive launching of SFTTRAY (rapid-double-clicking) but some customers have shut off the tray icon and that alone as reduced these instances.


    Steve Thomas, Senior Consultant, Microsoft

    App-V/MED-V/SCVMM/Server App-V/MDOP/AppCompat

    http://blogs.technet.com/gladiatormsft/
    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.”

    Friday, November 9, 2012 9:54 PM

All replies

  • Hello,

    Do you have any antivirus / third-party tool that installs file-system monitoring drivers?

    Nicke Källén | The Knack| Twitter: @Znackattack

    Friday, July 13, 2012 7:38 AM
  • Yes, the PC is running Symantec Endpoint Protection 11.0.
    Friday, July 13, 2012 7:41 AM
  • Hello,

    Can you verify if the problem exists without SEP?

    Nicke Källén | The Knack| Twitter: @Znackattack

    Friday, July 13, 2012 7:50 AM
  • Hello,

    Same result without SEP.

    Friday, July 13, 2012 8:50 AM
  • Hello,

    OK - if there are no other 3-party components worth investigating - I would suggest looking into these results which were located on the first page after googling for your error-message;

    https://madvirtualizer.wordpress.com/2011/08/03/is-it-the-%e2%80%9csystem%e2%80%9d-that%e2%80%99s-really-too-busy-to-complete-the-request-or-is-it-app-v/

    http://support.microsoft.com/kb/931112

    What could be worth doing is starting with a clean install using a Microsoft-provided installation source of Windows XP - with no alterations by anyone and then adding App-V and the virtual applications.

    Does the error occur or not? If it does - you should probably investigate your packages and see if they can be optimized.


    Nicke Källén | The Knack| Twitter: @Znackattack

    Friday, July 13, 2012 9:15 AM
  • Are you launching an application in a traditional App-V server-based environment, stand-alone environment. If connected to a management server, what would happen if you are in disconnected mode?

    Also - what do you have in the SFTLOG.TXT?


    Steve Thomas, Senior Consultant, Microsoft

    App-V/MED-V/SCVMM/Server App-V/MDOP/AppCompat

    http://blogs.technet.com/gladiatormsft/
    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.”

    Friday, July 13, 2012 5:02 PM
  • The software is deployed with SCCM, but to eliminate SCCM as a cause, I launch directly with "sfttray.exe" and not via "VAppLauncher.exe".

    "sftlog.txt" shows messages up to the point that the last application shut down.

    (This is the instance that hangs when launching "sfttray.exe" again, before "sfttray.exe" of this instance closed (because there where no more virtual applications).)

    [07/17/2012 08:50:09:717 SWAP INF] {hap=24:app=Microsoft Excel 2010 14.0.4756.1000:tid=BB4:usr=...}
    App shut down cleanly

    Tuesday, July 17, 2012 6:56 AM
  • Hello,
    I suggest you deploy the newest hotfix, which also contains fixes from all previous ones;

    http://social.technet.microsoft.com/Forums/da-DK/appvclients/thread/ffcea3c5-0c50-49a1-961c-16ce9b287d18


    Nicke Källén | The Knack| Twitter: @Znackattack

    Sunday, October 14, 2012 10:19 PM
  • Just to circle back - VAPPLauncher is just a wrapper but still encounters the same possibilities as a front-end component in the same manner of VAPPLauncher. The best way to quickly eliminate SEP as an issue (or at least known issues) is to temporarily disengage the SysPlant driver - reboot - and then reattempt the reproduction. It's less of a hassle as opposed to completely uninstalling it.

    The possible causes of this message can sometimes be as simple as excessive launching of SFTTRAY (rapid-double-clicking) but some customers have shut off the tray icon and that alone as reduced these instances.


    Steve Thomas, Senior Consultant, Microsoft

    App-V/MED-V/SCVMM/Server App-V/MDOP/AppCompat

    http://blogs.technet.com/gladiatormsft/
    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.”

    Friday, November 9, 2012 9:54 PM