Use Orca from the Windows Installer 4.5 SDK and look for that custom action in both of the InstallShield merge modules. I'll bet its in both of those modules.
Check the resultant package build in Wix to make sure if you get one of the copies of the functions. Regards, greenaj On Fri, 2009-07-24 at 16:14 -0700, dmcgloin wrote: > I'm getting the following warning when creating an MSI with 2 InstallShield > merge modules: > > "warning LGHT1055 : The InstallUISequence table contains an action > 'setAllUsersProfile2K' which cannot be merged from the merge module > 'C:\Program Files\Company\SDK\Installation\Merge Modules\Spc5.0_Map.msm'. > This action is likely colliding with an action in the database that is being > created. The colliding action may have been authored in the database or > merged in from another merge module. If this is a standard action, it is > likely colliding due to a difference in the condition for the action in the > database and merge module. If this is a custom action, it should only be > declared in the database or one merge module." > > The WiX warning explanation seems to imply that the InstallShield default > custom action is flawed, perhaps because the merge module custom action is > not scoped to the Merge Module GUID in the ModuleInstallExecuteSequence? > > Is there a safe/recommended way to make this warning go away? ------------------------------------------------------------------------------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
