ToolsAfter sequencing RSSOwl 2.x with Microsoft Application Virtualization (App-V) you may be able to launch RSSOWL during the monitoring and the launch phase, however after the second launch (and subsequent launches) the application fails to start with an application-specific error:

"There are no more files"

Cause

This occurs due to a sharing violation with the initial configuration file and the directory which needs to be opened for Read/Write access.

Resolution

1. Add an exclusion for %CSIDL_PROFILE%\.rssowl2\ prior to monitoring. You can do this by going to "Tools" and then "Options" in the sequencer. Then click the "Exclusion Items" tab.

2. During sequencing, let RSSOwl launch after it finishes installing during the monitoring phase. Then click through (skip) the Launch window. This will ensure all user settings do not get capture and get regenerated for new users and get properly routed to their profile *.PKG files.

Hope this helps,

Steve Thomas | Senior Support Escalation Engineer

The App-V Team blog: http://blogs.technet.com/appv/
The WSUS Support Team blog: http://blogs.technet.com/sus/
The SCMDM Support Team blog: http://blogs.technet.com/mdm/
The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
The OpsMgr Support Team blog: http://blogs.technet.com/operationsmgr/
The SCVMM Team blog: http://blogs.technet.com/scvmm/
The MED-V Team blog: http://blogs.technet.com/medv/
The DPM Team blog: http://blogs.technet.com/dpm/
The OOB Support Team blog: http://blogs.technet.com/oob/
The Opalis Team blog: http://blogs.technet.com/opalis

clip_image001 clip_image002