Uninstalling the nested Installs
Hi,
I am strucked up with two probelms since few days and I appreciate if anybody help me out with these.
I have a parent msi "aa.msi" and a child msi "bb.msi". when I try to install aa.msi, it calls bb.msi and every thing works fine during installation. When I try to install aa.msi, then the bb.msi files will be installed in C:\Program Files\XX directory.
when I tried to uninstall the aa.msi, uninstallation is working fine with out any errors but it is not removing the files which are installed by the bb.msi. I could still find the files in C:\Program Files\XX directoy. Can anybody tell me how to resolve this problem.
One more poblem is when I am trying to run the msi, initially it is showing " Preparing to install" window and it is taking more time to get the next window like 15 to 30 minutes. and after installing the msi and when i ty to un the application by clicking the shortcut, it is saying that " gathering the required information" and launching the application after 15 minutes.
Is there any way to install the msi and run the appication bit fast.
I really need some help on both the issues.
I appreciate if somebody help me with this.
Thanks
WEK
I am strucked up with two probelms since few days and I appreciate if anybody help me out with these.
I have a parent msi "aa.msi" and a child msi "bb.msi". when I try to install aa.msi, it calls bb.msi and every thing works fine during installation. When I try to install aa.msi, then the bb.msi files will be installed in C:\Program Files\XX directory.
when I tried to uninstall the aa.msi, uninstallation is working fine with out any errors but it is not removing the files which are installed by the bb.msi. I could still find the files in C:\Program Files\XX directoy. Can anybody tell me how to resolve this problem.
One more poblem is when I am trying to run the msi, initially it is showing " Preparing to install" window and it is taking more time to get the next window like 15 to 30 minutes. and after installing the msi and when i ty to un the application by clicking the shortcut, it is saying that " gathering the required information" and launching the application after 15 minutes.
Is there any way to install the msi and run the appication bit fast.
I really need some help on both the issues.
I appreciate if somebody help me with this.
Thanks
WEK
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
anonymous_9363
16 years ago
Does AA.MSI call BB.MSI during the uninstall phase? Look for Custom Actions with the condition "If Installed" or "If REMOVE~="ALL" and see if they're calling MSIExec with a command line '/X [Product_Code_from_BB.MSI]'
As for speed, I imagine the time is being spent copying the MSI locally for caching. If it's coming across a slow LAN or WAN, it may take an extended time.
As for speed, I imagine the time is being spent copying the MSI locally for caching. If it's coming across a slow LAN or WAN, it may take an extended time.
Posted by:
WEK76V
16 years ago
Hi,
Thanks for the response.
During the installation of AA.msi. if you the option X ( checkbox) then only the BB.msi will be installed.
I tried in giving different conditions like
a) If Installed And REMOVE~="ALL" --> with this it is skipping the action.
b) If REMOVE~="ALL" --> This is working fine during uninstall only when I select the X option during installation. If BB.msi is not installed then it is giving error 1713.
Any Suggestions...
Thanks
WEK
Thanks for the response.
During the installation of AA.msi. if you the option X ( checkbox) then only the BB.msi will be installed.
I tried in giving different conditions like
a) If Installed And REMOVE~="ALL" --> with this it is skipping the action.
b) If REMOVE~="ALL" --> This is working fine during uninstall only when I select the X option during installation. If BB.msi is not installed then it is giving error 1713.
Any Suggestions...
Thanks
WEK
Posted by:
anonymous_9363
16 years ago
So this is a self-authored MSI, not a vendor-supplied one?
It's important to note that the 'If Installed' condition is only relevant for the product containing it. It won't be true for the other product. So, in order to determine if the other product is installed, I'd suggest using the AppSearch facility to test for the 'UninstallString' entry (or other such entry which you know will appear) in HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\[ProductCode] where 'ProductCode' is the Product Code for the other product. This will populate a property with the data from the entry (or not, of course) and you can then test that property's content and branch accordingly.
I ought to have supplemented my response with the advice to turn on MSI logging so that you can see exactly what's going on. Since you want to log both uninstalls, I'd suggest turning it via policy, rather than adding the required command-line arguments. Paste this into a .REg file and merge it:
[font="courier new"]REGEDIT4
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer]
"Logging"="voicewarmup"
This results in files prefixed 'MSI', followed by 4-6 random alphanumeric characters and with the extension '.LOG' appearing in %SystemRoot%\TEMP.
It's important to note that the 'If Installed' condition is only relevant for the product containing it. It won't be true for the other product. So, in order to determine if the other product is installed, I'd suggest using the AppSearch facility to test for the 'UninstallString' entry (or other such entry which you know will appear) in HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\[ProductCode] where 'ProductCode' is the Product Code for the other product. This will populate a property with the data from the entry (or not, of course) and you can then test that property's content and branch accordingly.
I ought to have supplemented my response with the advice to turn on MSI logging so that you can see exactly what's going on. Since you want to log both uninstalls, I'd suggest turning it via policy, rather than adding the required command-line arguments. Paste this into a .REg file and merge it:
[font="courier new"]REGEDIT4
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer]
"Logging"="voicewarmup"
This results in files prefixed 'MSI', followed by 4-6 random alphanumeric characters and with the extension '.LOG' appearing in %SystemRoot%\TEMP.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.