Hi,

Wanted to take a quick poll to see how you guys are handling ICE09 warnings (WARNING - Component: COMPONENTNAME is a non-permanent system component).

Do you fix them - i.e. add a permanent component attribute and leave stuff behind on uninstall, letting windows installer decide what to replace later - based on file version etc or:

Leave / create them and have a clean uninstall - but using shared reference counting component attributes where appropriate?

At my last place of work we always removed the permanent component attribute i.e. making 16's 0's and making 24's 8's etc (creating ICE09s) to keep a clean uninstall - but here they fix them..

I know there are always exceptions depending on the package or environment but as a general rule of thumb - what do you do, and what are your thoughts behind it...?

Cheers,
Rob.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
At my last place of work we always removed the permanent component attribute i.e. making 16's 0's and making 24's 8's etc (creating ICE09s) to keep a clean uninstall - but here they fix them

What do you mean by this, could you explain the 16's and 24's bit a bit more for me.

Thanks

TG
Answered 12/06/2005 by: Thegunner
Second Degree Green Belt

Please log in to comment
0
Sure - this is the value in the Attributes columns in the Component table which you'll see when looking at your MSI in table view:

* The 8 value is the Shared DLL Reference count bit (same as 'Always increment shared .DLL count' check box in wise)

* The 16 value is the Permanent Attribute bit (same as 'Leave installed on uninstall' check box in wise)

Setting both of these options totals 24 - see MSDN reference info for the component table for more info.

So removing the 16 value (for example leaving a result of 0 or 8) is the same as un-checking the 'Leave installed on uninstall' box in wise.. Doing this means the component is removed on uninstall (keeping it clean) - but if the directory for that component is (for example) the System32 folder - it will generate an ICE09 warning...


Does that help?

Cheers,
Rob.
Answered 12/06/2005 by: MSIPackager
Third Degree Black Belt

Please log in to comment
0
In IBM Romania we always make a clean uninstall. We ignore the warning.
Answered 12/06/2005 by: shogun_ro
Orange Belt

Please log in to comment
0
thanks shogun - anyone else? [:)]
Answered 12/08/2005 by: MSIPackager
Third Degree Black Belt

Please log in to comment
0
As for my self I try to make as clean un- & installations as possible but it's almost up to the customer.
We can only give the customer recommendations on how to things, the positiv/negative sides of different scenarios.
Answered 12/08/2005 by: AngelD
Red Belt

Please log in to comment
0
I leave them, as long as the software installs and uninstalls and works.
Answered 12/09/2005 by: Thegunner
Second Degree Green Belt

Please log in to comment
0

I am leaving this Warnig as it is. I want a clean uninstall and even if I found on some vendor msi packages components with 16 or 24 atribute I am modify them to 0 or 8.

Answered 05/09/2013 by: terebent
Brown Belt

Please log in to comment
Answer this question or Comment on this question for clarity