SparkleFlow is the acclaimed packaging solution that combines all aspects of a software packaging project into a single interface. Preparing an application migration? Need to reduce your TCO? Need to manage lots of applications? Want to setup your applications right now and not waste to much of your value time? SparkleFlow Package Management offers the complete solution for creating structure in your packaging project.
|
Written by Manfred van Poorten
|
|||||||||
|
Description: Concerns: Additional Information: ICE68 verifies that the specified type for all Custom Actions in the Custom Action table is valid. If this is not the case, then it provides an error as output. Also, this ICE verifies that the bit “msidbCustomActionTypeInScript” (this indicates that it concerns a deferred execution) is set as “msidbCustomActionTypeNoImpersonate” (is executed under “system” context). A small note (extended information: see platform SDK, description "Custom Action In-Script Execution Options"): The Type field in the Custom Action Table is a Hexadecimal field, imagine that as follows: 0x00000000 “msidbCustomActionTypeInScript” is hexadecimaal defined as 0x00000400. “msidbCustomActionTypeNoImpersonate” is defined as 0x00000800. A Custom Action “Execute Program from installation” is definied as 0x00000002. For a Custom Action which is executed from the binary table under system context, the type will thus be 0x00000C02. This is the decimal number 3074, and indeed, you will also find it in the Custom Action Table. examples of possible errors:
Invalid custom action type for action 'Action1'. In case you wish or need to resolve this error: 1. Add 2048 (hexadecimaal 800) to the Type for Custom Action. The Custom Action Type does not exist, so there is no hexdecimal combination possible where this number comes out. Verify which Custom Action you wish to use, which Custom Action In-Script Execution Options and insert the correct type. |
|||||||||
» Back to article overview