Does any1 know how to resolve ICE 30.

I am packaging Oracle Discoverer Desktop v 9.0.4 (10g) which installs the files with the same name in different directories (under Inventory).
On validation ICE 30 occurs as different components are installing files with the same name.

Any way around the above?
0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity


Does it complain about SFN or LFN?
Answered 05/17/2005 by: Wozik
Orange Belt

Please log in to comment
As far as I know this error should only present a problem if you are planning on deploying your package to a SFN system.

If you aren't you can either leave the ICE30 errors - or fix them (by removing the SFN file reference) which will create ICE03 errors instead.

I think the package will install and work fine either way... I had the same problem repackaging the Oracle 9i client!

Hope this helps,
Answered 05/17/2005 by: MSIPackager
Third Degree Black Belt

Please log in to comment

It complains about both LFN and SFN. Oracle Discoverer installs almost 40 files with the same names to different folders.


I've tested this client and it works as far as I know. However the nos. of ICE 30 errors reported by Orca is close to 300! This really concerns me as I've always endeavored to remove all ICE errors I come across in my professional career.

Is this a problem with Oracle not following Microsoft guidelines?
Answered 05/17/2005 by: oofemioo
Blue Belt

Please log in to comment
It's just an MSI limitation with the 8.3 formatting system for long file names. It will generate a short file name reference for any files names over 8 characters but because the Oracle install has loads of files with the same name into different folders it causes errors in the MSI. It's not Oracle's fault particularly - other than the way their apps work!

Take the CompID.properties file for example - the 1st reference in the MSI file table will be COMPID~1.PRO
The second will be COMPID~2.PRO and so on until it gets to COMPID~Z.PRO

After that every SFN reference to the file will be COMPID~Z.PRO - which is where the ICE30s start appearing.

I appreciate having all these errors in a package doesn't look good but as far as I'm aware there is no way around it - how can there be? As long as you aren't installing the package on a SFN system then you will be fine.

That's how I understand it anyway [8|] If anyone knows a way to fix ICE30s without creating ICE03s then I'd be interested - and impressed!
Answered 05/18/2005 by: MSIPackager
Third Degree Black Belt

Please log in to comment
I just got the same problem (ICE30) after repackaging Oracle OLE-DB

I know that we used to rename all those Short File Names manually so that they were unique afterwards and we didn't get any ICE30 errors anymore.

However, if this is only a cosmetic thing, I don't think that it is worth spending so much time on it.

Answered 01/09/2006 by: rpfenninger
Second Degree Green Belt

Please log in to comment