Internal Consistency Evaluators – ICEs
Internal consistency evaluators, also called ICEs, are custom actions written in VBScript, JScript, or as a
DLL or EXE. When these custom actions are executed, they scan the database for entries in database
records that are valid when examined individually but that may cause incorrect behavior in the context of
the whole database.
ICE 01
Message
1
ICE 02
Message
1 File: ‘…’ not found in File Table. Ice02.html
Component KeyPath ODBCDataSource
Evaluation: ICE02
ICE 03
Message
1 ICE Internal Error 1149. API Returned: 1615.
2 Error 2228: ,_FtrRef, SELECT ‘Table’,
‘Column’ FROM ‘_FtrRef’ WHERE ‘Table’ =
‘Property’ AND ‘Colomn’ = ‘Property’
3 String overflow (greater then length permitted
in column); Table: “…”. Column: Target
Key(s): “…”
4 Invalid “…” string: Table: “…”, Column: “…”,
Key(s): “…”
5 Not a valid foreign key; Table: “-_Validation”,
Column: “…”, Key(s): “…”
6 Not a valid foreign key: Table: “Shortcut:”
Column: “Icon*.*”
Not a valid foreign key; Table: Class, Column:
Icon_, Key(s): classid > . < context > . <
component_ > in Class table
7 Not a valid foreign key; Table:
ODBCSourceAttirbute, Column: DtaSource_,
Key(s):
8 Not a valid foreign key: Table; Class, Column:
AppID_, Key(s):
{GUID}.InprocServer32.smartui2.ocx_COM
Solution
Solution
Under the Component Table, change the attribute to
32 for the ODBCDataSource
Solution
There is more data inserted in the field then
permitted.(more than 255 characters). This usually
happens when a VBScript is added to the
installation. In most cases it will just function with
the error.
There is no legal string entered for the given key.
Commonly an invalid character triggers this error,
i.e. a filename with non-English characters like ä, ë
or ü. If possible change these characters to a, e or u.
Check the _Validation table for the following
entries:
WiseReleaseMedia | MediaName |N
WiseReleaseMedia | Release_ | N
WiseReleaseMedia | DiskID | Y
WiseReleaseMedia | Size | Y
WiseReleaseMedia | Attributes | Y
The Icon_ column in the shortcut table must match
the exact entry (Icon name) in the Icon table.
The incorrect icon ID was in the Icon_ column.  
Lookup the correct Icon_ id in the Icon table and
copy it to the Icon_ column in the Class table. The
exact path can be copied.
The value of the Datasource_ column in the
ODBCSourceAttribute table is pointing to a
primarykey in the ODBCDataSource table which
doesn’t exist.
Smartui2.ocx is used as an example.
Value in te AppID column should only be a GUID
value that links to the AppID table.

9 Not a valid foreign key; Table: File, Column:
Component_, Key(s):
PCBLIB32.DLL174ice03.html File
Component_PCDLIB32.DLL174
10 Invalid identifier; Table: ProgId, Column:
Icon_, Keys(s): idoc_auto_file ProgId
Icon_idoc_auto_file
11 Invalid identifier; Table: RemoveFile, Column:
Component_, Key(s): '.....'. Found in
RemoveFile table.
12 Invalid Filename; Table: “…”, Column: “…”,
Filename, Key(s): “…”
13 Invalid Language Id; Table: File, Column:
Language, Key(s): File '....' in File table.
14 Invalid Filename/usage of wildcards; Table:
“…”, Column: “…”; Filename, Key(s): “…”
15 Invalid Full Path; Table: “Directory, Column:
“DefaultDir, Key(s): ProfilesFolder
16 Invalid property string; Table: directory,
Column: DefaultDir, Key(s):
ProgramFilesFolder
commonFilesFolder
AppDataFolder
CommonAppDataFolder etc.
17 Invalid filename/iniFile table; Table: iniFile;
Column: File
18 Invalid format string; Table: Registry, Column:
Key, Key(s): "StringName" Registry table.
19 Invalid GUID string.
20 Not a valid foreign key; Table: ProgId,
Column: Class_, Key(s): '....' in ProgId table.
ICE 04
Message
1 File: MyFile, Sequence: 210 Greater
Than Max Allowed by Media Table.
Ammount in the media table.
Check the compnents and its gien name as in the
error message.This error may occur if you made
changes in the package or in the tables.
There is a file in the file table that is a resource of
the PCDLIB32.DLL174 component, but you don’t
have a component in the component table with this
name. Create component.
Icon_ An optional foreign key into the Icon table
that specifies the icon file associated with this
ProgId. This is written under the DefaultIcon key
associated with this ProgId. This column must
beNull for a version independent ProgId.
Check the Component ID.
There is an invalid name entered for a file.
Look at the language set against other files - either
change the entry to the same language as other
files, change it to 0 or remove the language
completely.
The file was down to be removed, but was not in
the File table to be added, so removed:
  (a)   the entry in RemoveFile table
  (b)   the entry in Component table
Or ensure that the file is in the File table if it is
required.
In the _Validation table change the value of the
Category column back to DefaultDir.
Go to Directory table, check if the Column
DefaultDir also has the shortfile name:
i.e.
CommonAppDataFolder
.:APPLIC~1|Application Data.
If not add the shortfile name.
Ini file names contain spaces inside the shortfile
name Delete the spaces inside the short file names.
Leave the long file names alone.
Check the syntax of the Key 'StringName' in
Column Key - may be a missing these brackets
{....} or they need to be closed in that string.
Be sure GUID is all UPPER case
'foreign key' will be a class that has not been listed
in the Class table
Solution
Validates that the sequence number of every file in the
file Table is less than or equal to the largest sequence
number in the LastSequence column of the Media Table.
Check the number of files in the sequence column and
adjust this to last entry in the media table.
ICE 08
Message Solution
1 (Duplicate GUIDS) 2 components with Change the GUID of one of these components.
the same GUIDs.

ICE 09
Message Solution
1 Component “…” is a non-permanent On the component mentioned, the option “Always
system component increment shared .DLL count” must be activated. If the
component points to a Merge Module the error can be
ignored. This is an acceptable error, however to make
the component a permanent system component then give
it a value of 24 in the Attrib column

ICE 15

Message Solution
1 MIME Type 'AppName' referenced by 'AppName' does not map to an extension with a circular
extension 'Ext'. reference Extension Remove the entry from MIME
column in Extension table.

ICE 18

Message Solution
1 KeyPath for Component “…” is Directory Create a new row in the table “CreateFolder”, select the
“…”. The Directory is not listed in the mentioned Directory and the mentioned Component.
CreateFolders table

ICE 19

Message
1 Extension: 'imgr' advertises component:
'imgr'. This component cannot be
advertised because the KeyPath type
disallows it.
http://dartools/iceman/ice19.html
Extension Component_imgr imgr
Solution
The component is empty or might show empty in view
of files/registry, but may contain other information like
extensions/ini files. In case of an extension being there,
move it to a different component. In the extensions table
choose a different component which has a key path and
delete the empty component.

ICE 21

Message
1 Component: 'MyComponent' does not
belong to any Feature in
FeatureComponents table.
Solution
Add an entry to FeatureComponents table with the
following entries:
  (a)   Feature_ = A Present Feature
  (b)   Component_ = 'MyComponent'
ICE 24
Message
1 UpgradeCode: ' < None > 'is an invalid
Windows Installer GUID in Property
table.
ICE 27
Message
1 Unknown action: 'Action1' of
InstallExecuteSequnence table. Not a
standard action and not found in
CustomAction or Dialog tables.
ICE 30
Message
1 Installation of Component “…” would
cause the target file “…” to be installed
twice in “…” on a SFN/LFN system. This
will break the component reference
counting system.
2 Installation of a conditionalized
component would cause the target file
“…” to be installed in “….” By two
different components on a LFN system:
“…” and “…”. This would break
component reference counting.
3 The Target file “…” might be installed in
“…” by two different conditionalized
components on a SFN/LFN system: “…”
and “…”. If the conditions are not
mutually exclusive, this will break the
component reference counting system.
ICE 32
Message
1 Possible Mis-Aligned Foreign Keys
ModuleSignature.1 = s72
Modulecomponents.ModuleID = s72
ICE 33
Message
1 Reg Key “…” is used in an unsupported
way. This key need not to be written as it
already exists in the system.
Solution
Modify the UpgradeCode field entry in Property table -
use GUID Generator to generate a unique id, and copy
this id into the UpgradeCode field
Solution
There is an action listed in the sequence table indicated
that is not a standard actions , a custom action listed in
the CustomAction table , or a dialog box listed in the
Dialog table .
Solution
Go to the given component. In that component there are
two files with the same name. One of those files must be
deleted.
The This file is installed by two components in the same
directory. It is possible that the file also exists in a merge
module. Delete the file ot of the given component.
The file is installed/exists by/in two different merge
modules. This error can be ignored, because the
reference counting system setting is done by the merge
module.
Solution
Edit the ModuleSignature and Modulecomponents table
schema and ensure that both columns (‘1’ and
‘ModuleID’) have the same string length.
Solution
This error is usually generated by a merge module, if
this error is generated by a merge module, it can be
ignored.
This entry may overwrite a value created through that
table. Various
  (a)   check Verb table for extensions
  (b)   check Extensions table for same extensions

2 Reg Key “…” is used in an unsupported
way. Typelib HELPDIR should be
registered via the Typelib Table. This
entry may overwrite a value created
through that table.
3 Reg key “…” is used in an unsupported
way. Typelib should be registered via the
Typelib table – this key is automatically
written during typelib registration.
4 Reg key “…” is used in an unsupported
way. CLSID – ProgId should be
registered via the Class and ProgId tables.
This entry may overwrite a value created
through those tables.
5 Reg key “…” is used in an unsupported
way. ProgId – CLSID associations should
be registered via the ProgId and Class
tables. This entry may overwrite a value
created through those tables.
6 Reg key “…” is used in an unsupported
way. CLSID contexts should be
registered via the Class table. This entry
may overwrite a value created through
that table.
7 Reg key “…” is used in an unsupported
way. CLSID DefinprocHandler should be
registered via the Class table. This entry
may overwrite a value created through
that table.
8 Reg key “…” is used in an unsupported
way. CLSIDs should be registered via the
Class table. This entry may overwrite a
value created through that table.
9 Reg key “…” is used in an unsupported
way. Version Independent ProgId should
be registered via the ProgId table. This
entry may overwrite a value created
  (c)   copy the value from the Registry table to the
Argument column in the Verb table
  (d)   delete the entry from the Registry table
This entry may overwrite a value created through that
table. Registry table
  (a)   add an entry to the Typelib table
  (b)   delete the entry from the Registry table
In the registry path HK_Classes_Root\Typelib there are
several key’s that also exist in the Typelib table. The
key’s that exist in that table can be deleted from the
registry. If the error is generated by a merge module, it
can be ignored.
In the registry path HK_Classes_Root\ there are several
key’s that also exist in the ProgId table. The key’s that
exist in that table can be deleted from the registry. All
sub-key’s can also be deleted. If the error is generated by
a merge module, it can be ignored.
In the registry path HK_Classes_Root\ there are several
key’s that also exist in the ProgId table. The key’s that
exist in that table can be deleted from the registry. All
sub-key’s can also be deleted. If the error is generated by
a merge module, it can be ignored.
This entry may overwrite a value created through that
table
  (a)   add an entry to the Class table
  (b)   delete the entry from the Registry table
If in one of the sub-keys there is a value that begins
with “[!” or there is a name of a DLL or OCX
mentioned then that DLL or OCX should be set to
registers itself.
In the registry path HK_Classes_Root\CLSID there are
several key’s that also exist in the Class table. The key’s
that exist in that table can be deleted from the registry.
All sub-key’s can also be deleted. If the error is
generated by a merge module, it can be ignored.
If in one of the sub-keys there is a value that begins
with “[!” or there is a name of a DLL or OCX
mentioned then that DLL or OCX should be set to
registers itself.
In the registry path HK_Classes_Root\CLSID there are
several key’s that also exist in the Class table. The key’s
that exist in that table can be deleted from the registry.
All sub-key’s can also be deleted. If the error is
generated by a merge module, it can be ignored.
If in one of the sub-keys there is a value that begins
with “[!” or there is a name of a DLL or OCX
mentioned then that DLL or OCX should be set to
registers itself.
In the registry path HK_Classes_Root\ there are several
key’s that also exist in the ProgId table. The key’s that
exist in that table can be deleted from the registry. All
 through that table.
10 Reg key “…” is used in an unsupported
way. ProgId should be registered through
the ProgId table. This entry may
overwrite a value created through that
table.
11 Reg key '....' is used in an unsupported
way. Shell extension verbs information
should be registered via the Verb table.
Reg Key '....' is used in an unsupported
way. ProgId - Icon associations should be
registered via the ProgId and Icon tables.
ICE 36
Message
1 Icon Bloat. Icon '....' is not used in the
Class, Shortcut, or ProgID table. This
adversely affects performance.
ICE 38
Message
1 Component “…” installs to user profile. It
must use a registry key under KHCU as
its keypath, not a file.
2 Component '....' installs to user profile. It
must use a registry key under HKCU as
its KeyPath. The KeyPath is currently
NULL
sub-key’s can also be deleted. If the error is generated by
a merge module, it can be ignored
In the registry path HK_Classes_Root\ there are several
key’s that also exist in the ProgId table. The key’s that
exist in that table can be deleted from the registry. All
sub-key’s can also be deleted. If the error is generated by
a merge module, it can be ignored.
This entry may overwrite a value created through that
table. Various
  (a)   check Verb table for extensions
  (b)   check Extensions table for same extensions
  (c)   copy the value from the Registry table to the
Argument column in the Verb table
  (d)   delete the entry from the Registry table
This entry may overwrite a value created through those
tables
Solution
If the icon can be used in either the Class, Shortcut or
ProgId tables, then use it; otherwise delete it as it?s not
required
Solution
(a)   find all occurrences of this component - usually in
CreateFolder table (along with Component table and
FeatureComponent table)
  (b)   add an entry to the Registry table with the
following details:
       Reg       = Regisrtyxxx Root      = 1 (for HKCU) 2
(for HKLM)
       Key       = Software\xxxxxx\Directories
       Name    = component GUID
       Value    = directory id
       Comp    = component id
  (c)   copy the Registry id into the KeyPath column of
the component, in the Component table
  (d)   change the 0 in Attributes column to 4
Find all occurrences of this component - if in Shortcut
table (along with Component table and
FeatureComponent table)
  a)    add an entry to the Registry table with the
following details:
       Reg       = Featurexxx Root      = 1 (for HKCU) 2
(for HKLM)
       Key      = Software\xxxxxxx\Shortcuts

ICE 39
Message
1 The file “…” is explicitly marked
compressed, but the Summary
Information Stream already specifies that
the whole install is compressed. This
might not be the behavior you want.
ICE 43
Message
1 Component “…” has non-advertised
shortcuts. It Should use a registry key
under HKCU as its KeyPath, not a file.
2 Reg Entry “…” is not of type REG_SZ on
Windows 95 Systems. Make sure the
component is conditionalized to never be
installed on Win95 machines.
ICE 45
Message
1 Row ‘Resume_Install_Dialog.InstallNow
in table ‘Control’ has bits set in the
‘Attributes’ column that are reserved.
       Name    = component GUID
       Value    = shortcut id
       Comp    = component id
  b)    copy the Registry id into the KeyPath column of
the component, in the Component table  
Find all occurrences of this component - if in File table
(along with Component table and FeatureComponent
table)
  (a)   add an entry to the Registry table with the
following details:
       Reg       = Featurexxx
       Root      = 1 (for HKCU)
       Key       = Software\xxxxxx\Files
       Name    = component GUID
       Value    = file id
       Comp    = component id
  (b)   copy the Registry id into the KeyPath column of
the component, in the Component table  
Find all occurrences of this component - if in Registry
table
Solution
If the mentioned file is within a Merge Module this error
can be ignored.
Solution
Put one Current_User registry key under the mentioned
component and set that registry key as the keypath or
Create a dummy regkey with a value of 1 for HKCU.
Change the attributes in the component table to 4, add
the new dummy key as the key path for this component.
Add the component in the registry table as the
component
In the Component where Reg Entry “…” resides set the
condition to “NOT Version9x”.
Solution
They should be 0 to ensure compatibility with future
installer versions.
ICE 46
Message
1 Feature “..” has 2000 components. This
could cause problems on Win9x systems.
You should try to have fewer than 817
components per feature.
Property ADDLocal defined in Property
table differs from another defined
property only by case.
ICE 47
Message
1 Feature 'My Feature' has xxxx
components. This could cause problems
in Win9x systems. You should try to have
fewer than 817 components per feature.
ICE 50
Message
1 The extension of icon “…” for shortcut
“…” is not “exe” or “ico”. The icon will
not be displayed correctly.
2 The extension of icon '....' for shortcut '....'
does not match the extension of the
KeyFile for component '....'
ICE 51
Message
1 Font “…” is a TTC\TTF font, but also has
a title.
ICE 53
Message
1 Registry Key 'xxxxxxx' writes Darwin
internal or policy information..
ICE 57
Message
1 Component 'ShortcutsComponent' has
both per-user data and a keypath that can
be either per-user or per-machine.
http://dartools/iceman/ice57.html
Component Component
Solution
This limitation no longer exists with Windows Installer
version 2.0 or later.
Delete ADDLocal property and add the property in Caps
and define as you need e.g. ALL
Solution
If the install is not on a win95 build this is an acceptable
error in most cases
Solution
Shortcut Table
Check the filename being used for the shortcut, and
ensure it's a valid extension (usually "dll") - if this is the
case, then this is an usually an acceptable error.
If the extensions of the icon and the target file do not
match, the shortcut will not have the correct context
menu when the component is advertised. To fix this
error, rename the icon to match the extension of the
target file.
Solution
A TTF font automatically registers a title for the font.
But a title is also given in the table. Go to the table font
and delete the title text from the mentioned font.
Solution
This is usually reference to Installer keys in the registry
and is spurious - delete them.
Solution
Create a new component holding the HKCU registry
part, add that new component to an existing feature.
Change the keypath for the Shortcutscomponent to
another resource (noneuserprofile file or HKLM registry
entry).
 ShortcutsComponent'
“ShortcutsComponent” used as example
2 Component has both per user and per
machine data with a per machine keypath
ICE 60
Message
1 The File “…” is not a Font, and its
version is not a companion file reference.
It should have a language specified in the
Language Column.
ICE 62
Message
1 The isolated shared component “…” is
shared by multiple applications
(including…) that are installed to the
directory “…”.
ICE 64
Message
1 The directory '....' is in the user profile but
is not listed in the RemoveFile table.
In the Registry table find the registry entry and change
the component column to the name of the component
you created.
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 files/reg keys as it’s
keypath. If you use a registry key as the keypath for the
new component you’ll need to set the attribute on that
component to 4 to avoid new ICE errors.
Solution
If this error is generated by a Merge Module, the error
can be ignored.
Solution
There are DLL’s isolated in compare cense to
executables that are in the same directory. Check what
executable is installed in the same directory as a DLL.
Then delete all association to that executable in the
IsolatedComponent Table.
Solution
There are DLL’s isolated in compare cense to
executables that are in the same directory. Check what
executable is installed in the same directory as a DLL.
Then delete all association to that executable in the
IsolatedComponent Table. Or
in RemoveFile table
Find this component in the Component table - if IN
Component table:
  (a)   add an entry to the RemoveFile table with the
following details:
       FileKey             = 'xxxxxxx'
       Component        = component id
       FileName           = leave blank
       DirProperty        = directory id
       InstallMode        = 3
Find this component in the Component table - if NOT in
Component table:
  (a)   add an entry to the Component table
  (b)   add an entry to the FeatureComponents table
  (c)   add an entry to the RemoveFile table with the
following details:
       FileKey              = '....'
       Component        = component id
       FileName           = leave blank
        DirProperty        = directory id
       Install Mode       = 3

ICE 80

Message Solution
1 This 64BitComponent DIFxAPI.dll uses Remove 64-bit driver condition on Components Table
32BitDirectory Drivers and change the attribute to 0 from 256.
ice80.html Component
Directory_ DIFxAPI.dll

ICE 99

Message
1 WindowsVolume is the same as one of the
MSI Public Properties and can cause
unforeseen side
effects. ice99.html Directory Directory Wi
ndowsVolume
2 Same as above, different folder name.
Solution
Remove the WindowsVolume property entry from the
Property table.
WindowsVolume is a system directory which will be
populated from the Directory table.
Delete the offending Directory table row and then find
entries which contained it in the Component table and
change its folder name to 'WindowsFolder'