Hi,
We are experiencing problems with a virtual app which uses the Office applications installed on the computer.
Our virtual app calls Word through an ActiveX object which then launches the Word application. However, everytime this happens Word would like to configure itself for fitst use (same with other Office packets).
When we launch word locally, everything starts up just fine (no first time use setup).
Word is a legal 2007 version.
Any options we can try to call the Office 2007 progam's without getting the initial setup all the time?
Thank you in advance!
Hope you have followed this step by step instructions for Office 2007:
http://blogs.vmware.com/thinapp/2008/10/how-to-thinap-1.html
Can you attach the package.ini file please?
The thing is, we did not make a capture from the Office 2007 since it's already locally installed on the computers where we use Office.
We just want the Virtual application to use the local Office product.
The strange thing about this all is, some computers ask us for an initial setup, others don't and just work as they should (they open Word like requested).
Also the problem does not appear on Office 2010 products.
Could you try commenting out the below line in the package.ini and rebuild the package by running build.bat?
VirtualizeExternalOutOfProcessCOM=0
I got a similar Problem.
Just try to make a Empty DOSBOX without your Application and then start the Office.
The same thing should happen. I got this also with Office 2010.
It seems to have something to do with the "Office Protection Platform" Service but i don´t have a solution....
The VirtualizeExternalOutOfProcessCOM=0 don´t fix it becouse i need to start the Office from inside the Application as SnapIn...
It does work when you first open Office through the empty dosbox but that's no real solution for the users here. We can't expect them to open the dosbox first, start the office platform, then start our virtual app.
And like doofkopf said, VirtualizeExternalOutOfProcessCOM=0, doesn't do the magic either.
Any other possible solutions?
Could you try adding the below lines in the package.ini and rebuild the package?
VirtualizeExternalOutOfProcessCOM=0
ChildProcessEnvironmentExceptions=WINWORD.EXE;EXCEL.EXE;POWERPNT.EXE;OUTLOOK.EXE;MOC.EXE
ChildProcessEnvironmentDefault=Virtual
I tried adding the three lines to the package.ini and performed a rebuild. I still get the Windows Installer screen for Office 2007 when my virtual app launches.
Sadly enough no solution ![]()
Any other ideas?
Are you able to launch the ThinApp after the windows installer pop-ups?
Yes, then the application starts without any problem (we can even export the things we want to the Office application).
The only thing is, we can't ask our customers to keep waiting for the Windows Installer before they can use the application.
Ok got it. Could you check the Windows Event Viewer for the error under Application please.
You should be seeing Windows Installer warnings with appropriate message.
I do get a warning there...
"The detection of product {90120000-0011-0000-0000-0000000FF1CE}, function WordFiles has failed during the request of part {0638C49D-BB8B-4CD1-B191-051E8F325736}"
Seems like the ThinApp registry keys does not have permissions to access the native Office due to Isolation modes.
Can you upload the HKEY_LOCAL_MACHINE.txt registry file please.
What is the deployment OS?
The OS is Xp Professional SP3. I could upload the reg file, but that could take a while (14 0 Mb).
Should I be looking for something specific in advance (while I upload the file)?
Can you try changing the isolation mode of HKEY_CURRENT_USER\Software\Microsoft\Office from
The Merged option didn't seem to work either...
I've included the HKEY in the upload (I assumed you wanted the HKEY file from the computer we where testing on, but I assume you mean the HKEY from the build we include?)
You will find the Isolation_Merged line at the bottom of the file...
Any more options we could try?
Please file a support request to look into the issue in detail.
