How to troubleshoot Standard Action in MSI Installshield that did run on /qn parameters
Hello All,
There's an MSI that a standard action wasn't running on /qn parameters. The name of action is "ProcessComponents"
Any workaround?
2 Comments
[ + ] Show comments
-
Do the logs say why it wasn't run? Are you running a verbose log? /l*v <pathandnamefile.log> - dunnpy 10 years ago
-
Have you validated your MSI - this action appears to rely on keypaths (http://msdn.microsoft.com/en-us/library/windows/desktop/aa370853%28v=vs.85%29.aspx) so if your validation throws errors, resolve them and test again. - dunnpy 10 years ago
Answers (4)
Please log in to answer
Posted by:
dunnpy
10 years ago
Check the sequence tables (InstallUISequence & InstallExecuteSequence) to see if your action is in one or both?
I suspect that it's missing from the InstallExecuteSequence, so add it in to match where it is in the other table and test.
Either that or there is a condition that is preventing it running.
Hope that helps,
Dunnpy
Posted by:
anonymous_9363
10 years ago
Yes. Copy the CA from the InstallUISequence to he InstallExecuteSequence.
This is a pretty common scenario with MSIs. Vendors tend to assume that there'll be a user sitting in front of the install.
Comments:
-
Yes it was in InstallExecute Sequence but i didnt run. Upon checking my logs. - ajcbasilio 10 years ago
