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

Comments

  • This content is currently hidden from public view.
    Reason: Removed by member request
    For more information, visit our FAQ's.
  • Do the logs say why it wasn't run? Are you running a verbose log? /l*v <pathandnamefile.log>
  • 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.
Please log in to comment

Community Chosen Answer

2

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

Answered 10/11/2013 by: dunnpy
Red Belt

  • This content is currently hidden from public view.
    Reason: Removed by member request
    For more information, visit our FAQ's.
Please log in to comment

Answers

1

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.

Answered 10/11/2013 by: VBScab
Red Belt

  • Yes it was in InstallExecute Sequence but i didnt run. Upon checking my logs.
Please log in to comment
1

Check the condition of the CA in InstallExecuteSequence table.

Answered 10/17/2013 by: piyushnasa
Red Belt

Please log in to comment
1

Remove the condition from the standard action and check..

Answered 12/24/2013 by: jagadeish
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity