This issue has my mind boggled.
Bit of a background story in order to provide some context. My organisation still uses Lotus Quickplace, version 3.0 that is! It is not compatible with vista or windows 7 because the DHTML active x control was deprecated.
The organisation has transitioned to Windows 7, we have thinapped IE6 in order to provide backwards compatibility with Quickplace.
Everything is working satisfactorily except for Office integration. When opening files directly in IE6, users get an out of memory error, a windows installer not found error or both.
These errors are not encountered in XP when running the virtual IE6, Office opens fine. These errors are also not encountered by other applications like adobe reader.
I can't work out what to change to remove this problem, anyone got any ideas?
Referencing the ThinApp Troubleshooting procedures on the ThinApp Blogs (http://blogs.vmware.com/thinapp/2010/10/thinapp-troubleshooting-methods.html), I'd say you need to run a "washed" test next. That is, start removing the local components one at a time and re-test. At some point, the application should fail based on your production test scenario. However, if the the application doesn't fail, then run a "clean" test with the reverted snapshot of the CnB workstation. If the application passes that, then the issue is most likely an environmental one and thus you should consider those items associated it. As an example, I often name the CnB "localhost" so that any application that tries to pick the workstation name for the registry or some configuration would pick that name which can resolve to any local workstation.
Testing Procedure
Dirty Test
A dirty test is one that is conducted on the CnB with the application still locally installed. Any issues arising from this test will most likely be code related and will present obvious issues right away.
Washed Test
Simply use Add/Remove Programs to uninstall the application from the CnB. Then run the ThinApp to test. If any issues occur here, the likelihood that they are related to missing components or settings is very high.
Clean Test
Revert your CnB back to a clean state and test your ThinApp. This test builds upon the ides of the washed test and will also provide insight to any potential issues that may result from files and setting that are not removed during an uninstall procedure.
Production Test
Using your ThinApp, test in a live production workstation. Local policy, security applications and other items may cause issues. This test will allow you to determine if problems are environmental in nature.<br><br><br><br><br>-Dean F.
http://pubs.vmware.com/thinapp4/help
