I'm using InstallShield 12 and had the same trouble once.
According to the documentation (
http://msdn2.microsoft.com/en-us/library/aa368798.aspx) it means every colum of the ModuleExecuteUISequence table is not included in the _Validation table of the DirectX merge module. So I opened the module (C:\Program Files\Macrovision\IS12\Objects\ISDX9.msm) with Orca to find some errors.
* ModuleExecuteUISequence is not valid as a name of Merge Module Sequence Table. (
http://msdn2.microsoft.com/en-us/library/aa367792.aspx)
* _Validation table has rows for ModuleInstallExecuteSequence, which is a valid name as a sequence table, but has none for ModuleInstallUISequence.
That gave me an idea that the table name ModuleExecuteUISequence must be wrong and is supposed to be ModuleInstallExecuteSequence instead. I exported the ModuleExecuteUISequence table, edited the exported file to rename it as ModuleInstallExecuteSequence, imported the file and removed ModuleExecuteUISequence.
I also got the ICE18 error (see
http://msdn2.microsoft.com/en-us/library/aa368942.aspx). Since two components in this module seems to be just a trigger to run dxsetup.exe (that's why the File table is empty), I thought _Directry column could be any folder. So I added two rows in the Directory table, both are the same as TARGETDIR, and assign them to _Directry column in the Component table.
I wish this could be a help also for your application
