Application Virtualization TechCenter >
Microsoft Application Virtualization (App-V) Forums
>
App-V General Sequencing
>
File IO Error - filter.1.log was not found
File IO Error - filter.1.log was not found
- Sequencer Version 4.5.1.15580
Environment: XP SP3 VPC image with Undo Disk/Clean Install
No errors during install. No errors on launches.
Attempting to sequence Office 2007 Enterprise Edition Custom Install with Run All from PC set for Word, Excel, PowerPoint, and Outlook. Made everything else Not Available. Accepted Default for Common Files and Tools.
Installation went through without a hitch. Launched each application successfully and each of them shut down gracefully.
Then when trying to save package, during the "Encoding Blocks" stage, I get a
File IO Error
C:\Program Files\Microsoft Application Virtualization Sequencer\Logs\filter.1.log was not found.
I click on "OK" which is the only option, and I get
Microsoft App Virt Sequencer Error
An internal error has occurred while saving the package. The SFT file could not be saved. Please contact your system administrator.
I saw a similar thread but there was no suitable answers proposed for the original poster who apparently is facing the same problem.
Answers
- I found that this can happen if you choose the C:\Program Files directory when asked at the beginning of sequencing where the program will be installed. If you do this, then the sequencer will monitor everything under C:\Program Files for changes and include them as part of the sequenced application. What's happening here is that it is detecting the log file as part of the sequenced application, because it resides in a folder inside Program Files. Once it captures the log file, it is removed before the encoding stage.
Short answer: don't pick C:\Program Files as the install location when asked by the sequencer.
The App-V documentation recommends that you install to an 8.3-compliant named folder on a separate partition, preferably one with the same drive letter as the virtual drive on the clients (nomally Q:). If you don't have a choice in the matter, what I do is find out what directory in Program Files is going to be created by the setup program, create it ahead of time, and pick that specific folder inside Program Files.- Marked As Answer byKalle SaunamäkiMVP, AnswererTuesday, October 27, 2009 7:10 PM
All Replies
- Hello,
Have you checked the log-files? Have you tried with a different sequencer? Is there enough disk-space?
/ZNack - Hello
I would agree with Znack, check the log files. You can use teh following link for more information about the Seq log files:
http://technet.microsoft.com/en-us/library/cc843645.aspx
Thx
Dan Bernhardt [MSFT]- Proposed As Answer byznack Thursday, October 01, 2009 8:01 PM
- Have you checked (besides the free space suggested by others) that you don't have any A/V scanners etc. running on your Sequencer machine, which could interfere with the Sequence's files?
/Kalle - I found that this can happen if you choose the C:\Program Files directory when asked at the beginning of sequencing where the program will be installed. If you do this, then the sequencer will monitor everything under C:\Program Files for changes and include them as part of the sequenced application. What's happening here is that it is detecting the log file as part of the sequenced application, because it resides in a folder inside Program Files. Once it captures the log file, it is removed before the encoding stage.
Short answer: don't pick C:\Program Files as the install location when asked by the sequencer.
The App-V documentation recommends that you install to an 8.3-compliant named folder on a separate partition, preferably one with the same drive letter as the virtual drive on the clients (nomally Q:). If you don't have a choice in the matter, what I do is find out what directory in Program Files is going to be created by the setup program, create it ahead of time, and pick that specific folder inside Program Files.- Marked As Answer byKalle SaunamäkiMVP, AnswererTuesday, October 27, 2009 7:10 PM
MS "recommendation" on Creating a 8.3 folder under Q: is NOT to be meant as a "recommendation", rather it is a requirement.
When prompted by the Sequencer for the "Primary Directory the application was installed to" DO ALWAYS point to Q:\8.3 or create an 8.3 directroy right at that point.
A different thing is the applications installation target directroy. Here you may (preferable) create a folder underneath 8.3 and use this. But on the other hand it also often works if the applications installation target points to C:<something>.
Falko- You're right, my use of 'recommended' was probably a bit on the lenient side. However, a 'requirement' implies it won't work at all if you don't follow it. Officially that may be the case, but in some cases, it will work anyway. YMMV. Whenever you have the option, definitely create the 8.3 directory under Q.
Semantics aside, my main point was that I've seen cases where people have intuitively picked the Program Files directory because that's where the program is being installed, and the symptom the OP reported is what happens.
