Software Deployment

It looks like some custom actions are run in the UI Sequence. You can find alot of vbscript custom actions in the InstallUISequence. Try moving them to InstallExecute sequence.

Hi Joe,
Patrick is right about the Custom Actions.
But moving them to "InstallExecuteSequence" is not a good idea.
Instead you should copy them to the "InstallExecuteSequence" and add "TypeFirstSequence" (+256).
See: http://msdn.microsoft.com/en-us/library/aa368067(VS.85).aspx

I can't see embedded MSI's in this package.
But there are some "helper files" in the "ISSetupFile" table, which are extracted by Installshield.

Regards, Nick

As usual Nick your info is always right on but I don't understand what you mean by "TypeFirstSequence" (+256)" Where do I put the "TypeFirstSequence" (+256)

Thanks


ORIGINAL: nheim

Instead you should copy them to the "InstallExecuteSequence" and add "TypeFirstSequence" (+256).
See: http://msdn.microsoft.com/en-us/library/aa368067(VS.85).aspx

The msidbCustomActionTypeFirstSequence option flag (value 256) have to be add to the CustomAction.Type column for the custom action to only be executed once if placed in both the InstallUISequence and InstallExecuteSequence table.