ICEM03 verifies that all actions in the module are either base actions or derive from a valid base action.

Merge module ICEs are stored in a merge module .cub file called Mergemod.cub and not in the .cub file containing the ICEs used for package validation.

Result

ICEM03 posts the error messages for a module containing actions in a sequence table that is not a base action or derived from a valid base action.

Example

ICEM03 posts the following error messages for a module containing the database entries shown below.

The action 'Action1' in the 'ModuleInstallExecuteSequence' table is 
orphaned. It is not a valid base action and does not derive from a 
valid base action.
The action 'Action2' in the 'ModuleInstallExecuteSequence' table is 
orphaned. It is not a valid base action and does not derive from a 
valid base action.

ModuleInstallExecuteSequence Table

Action	Sequence	BaseAction	After	Condition
Action1		Action2	0
Action2		Action1	0

 

ICEM03 posts errors for these two actions because they refer to each other as base actions in the ModuleInstallExecuteSequence table. All actions in the ModuleAdminUISequence, ModuleAdminExecuteSequence, ModuleAdvtUISequence, ModuleAdvtExecuteSequence, ModuleInstallUISequence, and ModuleInstallExecuteSequence tables must either be base actions or derive their position from the combination of another action and a before and after flag.

To fix this error, determine the base actions for the two actions. Add a record for the base actions with a default sequence number. For Action1 and Action2 enter the base action names in the BaseAction column and 0 or 1 in the After column.

See Also

Merge Module ICE Reference

Send comments about this topic to Microsoft

Build date: 8/13/2009