I have another merge module that adds custom actions after CostFinalize so I thought there might be a clash somewhere. I removed this other working module from the installer and the new custom action showed up with no problems.
When I added it back in, the problem re-appeared. I noticed I was getting 26 lines of the following error : warning LGHT1055: The InstallExecuteSequence table contains an action '' which cannot be merged from the merge module.... Notice that the action name is empty. I decided to swap the <merge> entries in the wxs file so that the failing merge module was first in the list and, hey, everything started working. The custom actions from both merge modules showed up as expected. When I swapped them back, it failed again. There seems to be something significant about the order of the <merge> entries. When it fails, merge.log shows Placing action SetValueName.935D381A_65DE_4282_A110_D09C57AD3B85 after CostFinalize Action ValidateProductID could not be placed in database sequence, no ordering possible. Action CostInitialize could not be placed in database sequence, no ordering possible. Action FileCost could not be placed in database sequence, no ordering possible. Action CostFinalize could not be placed in database sequence, no ordering possible. Action SetQtExecDeferred.697CB0F5_D399_4519_AEDE_F350B9384F38 could not be placed in database sequence, no ordering possible. Action InstallValidate could not be placed in database sequence, no ordering possible. Action InstallInitialize could not be placed in database sequence, no ordering possible. Action ProcessComponents could not be placed in database sequence, no ordering possible. Action UnpublishFeatures could not be placed in database sequence, no ordering possible. Action SelfUnregModules could not be placed in database sequence, no ordering possible. Action RemoveRegistryValues could not be placed in database sequence, no ordering possible. Action WixSchedFirewallExceptionsUninstall could not be placed in database sequence, no ordering possible. Action RemoveFiles could not be placed in database sequence, no ordering possible. Action RemoveFolders could not be placed in database sequence, no ordering possible. Action CreateFolders could not be placed in database sequence, no ordering possible. Action InstallFiles could not be placed in database sequence, no ordering possible. Action WixSchedFirewallExceptionsInstall could not be placed in database sequence, no ordering possible. Action WriteRegistryValues could not be placed in database sequence, no ordering possible. Action SelfRegModules could not be placed in database sequence, no ordering possible. Action RegisterUser could not be placed in database sequence, no ordering possible. Action RegisterProduct could not be placed in database sequence, no ordering possible. Action PublishFeatures could not be placed in database sequence, no ordering possible. Action PublishProduct could not be placed in database sequence, no ordering possible. Action QtExecDeferred.697CB0F5_D399_4519_AEDE_F350B9384F38 could not be placed in database sequence, no ordering possible. Action InstallFinalize could not be placed in database sequence, no ordering possible. Action SetValueName.935D381A_65DE_4282_A110_D09C57AD3B85 could not be placed in database sequence, no ordering possible. 2009/6/11 Rob Mensching <r...@wixtoolset.org>: > Strange. Try running light.exe with the -notidy switch and look for the > merge.log in the left over TEMP directory. It may point out a failure > during merge module merging. > > Antony Walmsley wrote: >> I've got a custom action set up in my merge module as follows : >> >> <Binary Id="SetValueCADll" >> SourceFile="$(env.VSBUILDPATH)\$(var.BuildType)\SetValueNameCA.dll" /> >> <CustomAction Id="SetValueName" BinaryKey="SetValueCADll" >> DllEntry="SetValueName" Execute="immediate" Return="check" /> >> <InstallExecuteSequence> >> <Custom Action="SetValueName" >> After="CostFinalize">$ComputerName=2</Custom> >> </InstallExecuteSequence> >> >> Looking in Orca at the msm file, I see that the CustomAction table and >> the ModuleInstallExecuteSequence table have the custom action in them >> as ex >> >> However, looking in the msi file that uses this merge module, I only >> see the CustomAction table entry. The CA is not appearing in the >> InstallExecuteSequence table. I don't understand what is wrong. No >> errors are produced and the ICE validation warning messages do not >> seem to have anything related to this problem. >> >> Do anyone have any ideas? >> >> ------------------------------------------------------------------------------ >> Crystal Reports - New Free Runtime and 30 Day Trial >> Check out the new simplified licensing option that enables unlimited >> royalty-free distribution of the report engine for externally facing >> server and web deployment. >> http://p.sf.net/sfu/businessobjects >> _______________________________________________ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
