Question: Getting ISCE02 error message when validating msi

Getting ISCE02 error message when validating msi

Vado

Greetings all,

I just finished compiling an msi. I then tested it on a Vista 32bit machine and it installed itself fine. The only error that I see after doing a QA is that when I click on help, it says something like "it cannot find the help files" Then I decided to run the Logo Validation Suite and got a bunch of ISCE02 error message. In bried what I did to the appliation was to convert legacy (Installation Monitoring was used) then into irp to ism, then deleted desktop shortcut, renamed a component, set ALLUSERS property to 1. and then compile it to msi

I was wondering if someone could give me a direction as where to go

Thank you

Answer Summary:

Go back to your irp file, compile it and run validation before you edit it.

Answered

Please log in to comment

Answers

Go back to your irp file, compile it and run validation before you edit it. That will rule out post snapshot errors. Also if you can be more accurate with the error message, it would be helpful.

Answered 12/04/2012 by:

oreillyr

Vado 5 months 17 days 23 mins ago

Hey Oreillyr, Thanks for the quick feedback. Indeed I followed ur advice and validated straight from irp built without making any modification to the ism and it validated fine with lesser error message.

Let me ask you another question if you don't mind, how can you tell whether to take action or disregard a post snapshot error message. I did some research and saw that not all error messages are meant to be regarded.

Here is the post snapshot error messages.

ICE03 Invalid DefaultDir string; Table: Directory, Column: DefaultDir, Key(s):_.10.0
ICE27 Unknown action: 'MsiConfigureServices' of InstallExecuteSequence table. NOt a standard action and not found inCustomAction or Dialog Table.
ICE57 Component 'ShortcutsComponent' has both per user and per-machine data with an HKCU Registry KeyPath.
ICE99 The directory name: WindowsVolume is the same as one of the SI PublicProperties and ancause unfrseen side effects.

Of course what I did was to go and search for these error messages and found out that more about the root cause, but how do I take action to resolve those issues.

Cheers

Please log in to comment

Please log in to answer