Summary

Symptoms

ICE43 only occurs in validation and is displayed in the following formats:

1. Component <COMP> has non-advertised shortcuts. It must use a registry key under HKCU as its KeyPath, not a file.

2. Component <COMP> has non-advertised shortcuts. It must use a registry key under HKCU as its KeyPath. The KeyPath is currently NULL.

3. Component <COMP> has non-advertised shortcuts. Its KeyPath registry key must fall under HKCU.

4. The KeyPath registry entry for component <COMP> does not exist.

5. The registry entry <REG> is set as the KeyPath for component <COMP>, but that registry entry doesn't belong to <COMP>.

Cause

This is an entry in the Component table:

This is an entry in the Registry table. Notice that there is only one entry, and the Registry column says Reg5. However, in the Component table entry above Component1 is looking for an entry Reg4 in the Registry table:

A component contains a key path registry entry key, but the key is associated with another component. This scenario does not occur under normal circumstances. It only occurs if the Registry or Component table has been manually edited via the Direct Editor. Following is an example of table entries that would cause this validation error.

This is an entry in the Component table:

This is an entry in the Registry table. Notice that there is only one entry, and the Component column says Component2. However, in the Component table entry above, the Component column says Component1. However, both the KeyPath column above and the Registry column below have Reg4 listed:

Resolution

1. Find the component mentioned in the error via the Components or Setup Design view.
2. Expand the component and click Files.
3. Right-click the key file and choose Clear Key File. The key file will have a key icon displayed to its left.
4. Click Registry Data.
5. Right-click the HKEY_CURRENT_USER hive under the Destination computer's Registry view and choose New > Key.
6. Right-click the new key and choose New > Default Value.
7. Right-click the new default value under Destination computer's registry data and choose Set Key Path.
8. Rebuild the release and revalidate.

1. Find the component mentioned in the error via the Components or Setup Design view.
2. Expand the component and click Registry Data.
3. Right-click the HKEY_CURRENT_USER hive under the Destination computer's Registry view and choose New > Key.
4. Right-click the New key and choose New > Default Value.
5. Right-click the New default value under Destination computer's registry data and choose Set Key Path.
6. Rebuild the release and revalidate.

1. Find the component mentioned in the error via the Components or Setup Design view.
2. Expand the component and click Registry Data.
3. Right-click the key that is set as the key path and choose Clear Key Path. The current key path will be listed under a hive other than HKEY_CURRENT_USER. The key will have a key icon displayed to its left.
4. Right-click the HKEY_CURRENT_USER hive under the Destination computer's Registry view and choose New > Key.
5. Right-click the New key and choose New > Default Value.
6. Right-click the New default value under Destination computer's registry data and choose Set Key Path.
7. Rebuild the release and revalidate.

1. Find the component mentioned in the error via the Components or Setup Design view.
2. Expand the component and click Registry Data.
3. Right-click the HKEY_CURRENT_USER hive under the Destination computer's Registry view and choose New > Key. You can use an existing key if you wish.
4. Right-click the New key and choose New > Default Value.
5. Right-click the New Default value under Destination computer's registry data and choose Set Key Path.
6. Rebuild the release and revalidate.

1. Find the component mentioned in the error via the Components or Setup Design view.
2. Expand the component and click Registry Data.
3. Right-click the HKEY_CURRENT_USER hive under the Destination computer's Registry view and choose New > Key. By recreating the key, the key will be associated with the correct component.
4. Right-click the New key and choose New > Default Value.
5. Right-click the New value under Destination computer's registry data and choose Set Key Path.
6. Rebuild the release and revalidate.

Additional Information

Key paths and key files help the Windows Installer detect a component's presence on a machine. There is not necessarily a right or wrong key path or key file, but generally, the key path or key file should be a main piece of the application. For example, if a component has two files, one text file and one DLL, and the application will not work if the DLL is not present on the target machine, mark the DLL as the key file, not the text file. The same applies to marking registry keys as key paths.

In addition to the solutions above any non-advertised shortcuts can be changed to Advertised using these steps:

1. Open the Shortcuts view.
2. Click each shortcut one at a time and set the Advertised property to Yes if it is set to No.

The ICE43 validation error is documented in the Windows Installer Help Library topic ICE43.

The Registry table is documented in the Windows Installer Help Library under topic Registry Table.

The Component table is documented in the Windows Installer Help Library under topic Component Table.

For more information on the advertised shortcut property, see the InstallShield Help Library topic Shortcut Properties.

For more information on advertisement in general, see the Windows Installer Help Library topic Advertisement.

For more information on key files and key paths, see the InstallShield Help Library topics Setting Component Key Files and Setting Key Paths for Components.