Frequently Encountered ICEs

Ice03: can be ignored.

Ice64: when any directory error appears, create a same entry in remove file table

If you do not use Roaming Profiles (Intellisync) and Active Directory group policy to assign/publish to Users, you can ignore this error.  It will have no effect on the environment.

Ice99: windows volume – this should be in CAPS

Ice104: when lockpermissionex and msilockpermissionex both exists, we need to drop the lockpermissionex table.

MsiLockPermissionsEx Table enhances the functionality over LockPermissions Table. With MsiLockPermissionsEx table, users now have the ability to set access permissions on objects impacted by the application install that previously required using custom actions or other methods outside of Windows Installer

Ice38: we have to make one of hkcu entry (which should not be a file, as key path).

ERROR: Component DesktopFolder installs to user profile. It must use a registry key under HKCU as its KeyPath, not a file.

Solution: In the Components Tab, find the CurrentUser component, which holds all the user's information. Pick one of the registry keys (except the one set as a keypath), right click on it and select the option 'Move'. Move that key to the component referred on the ICE error message. Go to that component, open it and find the 'new key'. Right click on the entry and select 'Set as Key' option.

Resolve ICE18 Error

Error: KeyPath for Component “ABC” is Directory “XYZ”. The Directory is not listed in the CreateFolders table

Solution: Create a new row in the table “CreateFolder”, select the mentioned Directory and the mentioned Component.

Resolve ICE57 Errors

Error: Component has both per user and per machine data with a per machine keypath

Solution: Create a new component (with a new GUID), move all of the per user data from the component that kicks up the error to the new one. Set one of the reg keys as it’s keypath.

Ice27: have to drop the row.

Only exceptions are ICE33 and ICE36 warnings.