Software Deployment

Here are some of the errors that I am seeing.

Invalid DefaultDir string; Table: Directory, Column: DefaultDir, Key(s): INSTALLDIR5 ice03.html Directory DefaultDir INSTALLDIR5
Evaluation: ICE03

Extension: 'aim' advertises component: 'Extension'. This component cannot be advertised because the KeyPath type disallows it. ice19.html Extension Component_ aim Extension
Evaluation: ICE19

Component Visit_AIM.com.url installs to user profile. It must use a registry key under HKCU as its KeyPath, not a file. ice38.html Component Attributes Visit_AIM.com.url
Evaluation: ICE38

Component AIM4 installs to user profile. It must use a registry key under HKCU as its KeyPath, not a file. ice38.html Component Attributes AIM4
Evaluation: ICE38

Component AIM4 has non-advertised shortcuts. It should use a registry key under HKCU as its KeyPath, not a file. ice43.html Component Attributes AIM4
Evaluation: ICE43

Component 'CurrentUser' has both per-user and per-machine data with an HKCU Registry KeyPath. ice57.html Component Component CurrentUser
Evaluation: ICE57

From one of the component names, CurrentUser, I'd guess that you're using a Wise product, probably Wise Package Studio?

ICE03
Presumably this http://msdn.microsoft.com/en-us/library/aa368798%28VS.85%29.aspx was what you came across in your searching?
This should be easier to spot if you switch to 'Setup Editor' view, select the 'Tables' tab and then select the 'Directory' table. Click the 'DefaultDir' column in the right-hand pane and the error should become clear, as the 'Full Directory' column will be empty. You should be able to track back through the directory tree using the 'Directory_Paren' column to determine what the value for 'DefaultDir' should be.

ICE19
http://msdn.microsoft.com/en-us/library/aa368943%28VS.85%29.aspx
It's pretty straightforward. For an advertised component (e.g. a file extension or COM component), the 'KeyPath' column of the 'Component' table must refer to a file. For an adevrtised shortcut, it must refer to a directory in the case of an advertised shortcut. Either must also always have a ComponentID.

ICE38
http://msdn.microsoft.com/en-us/library/aa368961%28VS.85%29.aspx
Again, pretty straightforward. Set a registry path to be the component's key path, not a file. Select the 'Components' tab, scroll down to the named component (e.g. Visit_AIM.com.url) and expand it. There's probably a 'Files' branch. If you expand that, you'll eventually see an icon with a key symbol next to a part of that component. That part will be a file, whereas it ought to be a registry entry.

ICE43
http://msdn.microsoft.com/en-us/library/aa368968%28VS.85%29.aspx
Similar to the above.

ICE57
This is common with WPS: it can be a bit brain-dead and will mix user and machine data in components. In 99.99% of cases, it will involve registry entries, meaning that the component has stuff in HKLM as well as HKCU. You need to move the HKLM stuff into a separate component.

I know others won't agree but, for me, all of the above is moot IF you're dealing with a vendor-supplied MSI. Unless the ICEs will cause the build major grief, I leave vendor MSIs alone.

http://www.installworld.com/index.php?option=com_content&view=category&id=42&Itemid=138

you can read more about ice errors here

Thank you so much for the help! Yes I am using Wise 8.0 to package.