spencer.wasden1.552490721833913E12 asked a question.
How do I know the offending custom action?
If 9237AE408.{55FB6394-6057-0FAA-0DF4-6AAD39CF2389} is the custom action that is offending (I'm not completely sure it IS a custom action), how do I find out which custom action it refers to? Here's my verbose msi log:
Action ended 16:43:28: InstallFinalize. Return value 1.
MSI (s) (24:C0) [16:43:28:697]: Doing action: 9237AE408.{55FB6394-6057-0FAA-0DF4-6AAD39CF2389}
Action 16:43:28: 9237AE408.{55FB6394-6057-0FAA-0DF4-6AAD39CF2389}.
Action start 16:43:28: 9237AE408.{55FB6394-6057-0FAA-0DF4-6AAD39CF2389}.
MSI (s) (24:C0) [16:43:28:707]: Note: 1: 2762
Error 2762.Cannot write script record. Transaction not started.
I have 0 custom actions after InstallFinalize
I see the warning for the custom action I mentioned. I actually have 4 of these warnings [i.e. warnings that reference custom actions by an ID but not a name], each with a different identifier, e.g.:
ISDEV : warning -6524: The Custom Action 9237AE408.{55FB6394-6057-0FAA-0DF4-6AAD39CF2389} in the InstallExecuteSequence table is deferred and must be sequenced between InstallInitialize and InstallFinalize. Ensure that the Custom Action is sequenced properly and that the base actions exist in the sequence.
I can't find these identifiers in the Direct Editor. How do you find the custom action by the ID?
Thanks
Another thing you might try is to open the MSI in InstallShield (or Orca) and look at the Custom Actions view of the MSI.