Remove Licensing error prompt during uninstall
I am trying to setup an .msi install to install and uninstall silently. According to the vendor, there is a public property called SHOWACTIVATE that controls the licensing prompt. They say if I set it to 0, the prompt will be skipped and the install will continue. The problem I am having is this is not affecting the uninstall process. I still hit the prompt while running msiexec /x {ProductCode} /qn, which stalls the entire sequence until OK is clicked. I am thinking this prompt is also being controlled by a Custom Action in the Execute Sequence but I am not sure what it may be.
Here is the error message. Any ideas or suggestions are welcomed.
Thank you,
-Adam
Answers (1)
Your thoughts are most likely correct in thinking its a CustomAction. Trouble is its hard to find out which. Try verbose logging with the uninstall, when it pops - stop, then have a look in the log to see where its in the InstallExec Seqeuce - should be close to the action that pops that dialog.
Issue is, if you remove the CA it could have unintentional consequences.
You could condition the CA not to run on uninstall? Could help?
"test test test, it all comes out in the wash then"
Comments:
-
Good idea. I ran the uninstall script again this time creating the log file. Here is the last Action started and ended.
Action start 9:02:17: UnRegisterETABS.
MSI (s) (68:F0) [09:02:17:881]: Doing action: Deactivate64
Action ended 9:02:17: UnRegisterETABS. Return value 1.
This action has one condition on it of REMOVE="ALL"
So this is either representing the action where that error box appears or the one just before it. The next action in the IE Sequence for the uninstall is Deactivate64 which has conditions REMOVE="ALL" AND NOT UPGRADINGPRODUCTCODE
Thoughts on which one might be related to the prompt. I could make an argument for either one I suppose. I'll do some testing. - quattro004 10 years ago -
It looks like the Deactive64 Custom Action controls this prompt. I disabled it from the sequence for testing and it appears to have resolved the issue. Thank you for the help! - quattro004 10 years ago
