|
Nov
06
|
The following post will be written in English only
Dynamic Suite Composition which was introduced in Application Virtualization 4.5, explained further in the sequencing whitepaper, has given Application Virtualization some great possibilities – however it offers a more complex virtual environment.
Previously I described an issue where we saw that a specific .DLL was not found by Excel and this lead me to the following statement;
When using shortnames in two or more suited packages only the primary packages virtual environment is shown.
As stated earlier I have sequenced an application where the primary application is a Java-based app that needs Acrobat Standard 8 and Microsoft Office. When opening Excel or Word I often received issues with macros, however I could not repeat this when I opened the application by itself. So my primary package contains Java, my first secondary contains Acrobat and my second secondary contains Microsoft Office. This seems like a complex application and the possibilities for errors seemed to high. However, as the previous picture from PROCMON showed – the vbe6.dll can not be found.
To verify this I essentially created one new application with some folders and then suited it together with a smaller package I had made (containing folders in C:\Program files). What I was looking for is what happens when I access a folder with a shortname – can I see my secondary package? I can not see my secondary packages folders unless I use a full name (not including ~)
The result was not what I had hoped for, and I confirmed this by dropping the vbe6.dll into the primary package (along with some other files..) and the macro-issue disappeared from my previous so troublesome package.
I reconfirmed this on the 4.6 beta, but after reviewing the work a few days later I was not to sure. However, a defect report was submitted on Connect for Microsofts review and hopefully they will address this.
What was the end-result? Well, we made a policy not to use DSC, ordered increased SAN-storage and repackaged some applications. Currently there only exists one other instance of this – posted in this thread on the Technet Forums.
november 30th, 2009 at 11:41
Hi,
I do not think that this is an issue because of Dynamic Suite Composition. I see the problem also but only with Excel 2003 in combination with App-V 4.5 we do not use Dynamic Suite Composition but I receice the same error. VBE6.dll is not found in PROCmon. I get the issue with one plugin where the other is not showing the issue. So it looks in my case more like an issue with certain Excel patches and the plugin is ancient (Year 2004).
november 30th, 2009 at 11:47
Hi,
I just tested the sequence again in monitoring stage and what I found was that when I copied vbe6.dll to let’s say c:\winnt\system32 and registered it over there when I did that everything worked ok. Hope this helps you as well?
december 2nd, 2009 at 21:00
Hello,
I am currently working to confirm the behavior, however as always I am having difficulties finding the time. Hopefully this week or next week I can do some extensive testing with the latest sequencer / client version. From what I have seen the use of shortname seems to be the only common thing when testing in a DSC scenario (and the fact that the problem never occurs in a single suite).
/Nicke