I am pretty new at the ThinApp stuff, so please bear with me.
I am using thinapp 4.7 on Windows XP SP3.
I have Microsoft Communicator 2007 R2 packaged and working. I am trying to install a cumulative .msp update and do an sbmerge.
Every time I run the .msp file I get an Installer error saying that the file can't be found in C:\Windows\Installer.
I updated my thinapp package by including the cmd and regedit apps.
I ensure that my sandbox is empty.
I run the original application.
Next, I run the cmd application.
Here is where my problem starts. I have tried to run the .msp update from inside the virtualized cmd app with the update still resident outside the virtual environment. I have tried adding the .msp file to the package, rebuilding it, and then clearing the sandbox, running the original app, running the virtualized cmd app, and then calling the install from the virtual cmd, but I get the same error again. I have also tried to run the original thinapp package, run the virtualized cmd, and from the virtual cmd, copy the .msp file to the virtualized path of my original installation (c:\program files\microsoft office communicator) and I am still getting the same error.
The file is there and available in the sandbox, I can see it in there and it's not in the regularly browsed c:\windows\installer.
The security appears to be fine as well with full control permissions available to myself, admins, and the system account.
I know that I can just repackage this and run the update as part of the new thinapp, but this is the first time that I am trying to do a thinapp update and I want to know how to do this going forward.
Is there something that I am missing? Most of the stuff I have found have people saying that it just works, but I can't seem to get it to work for anything.
Any help is greatly appreciated.
When you install a MSP patch, it will look for the original installer cache under C:\Windows\Installer by comparing the MSI ProductCode.
Check the package.ini for MSI details and verify that the MSIProductcode property is uncomment and containing the exact value of its original installer. You can manually copy the value and overwrite it.
See http://blogs.vmware.com/thinapp/msi/ for additional ThinApp MSI documentation.