Hello to everyone,

When validating the ism, it takes too much time and ended unfinished with ICEHP35 Warning RemoveFile Table is missing. "Cannot continue validation".

I just want to know the reason why the validation of my application cannot continue [&:]. I only have one file which is msvbvm60.dll delivered to C:\Windows\System32 which is my Installdir.

Thanks in advance! [:)]

Regards,

Tink
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
Hi,

I need your help. Any idea to solve this issue? Thanks... :)

Tink

Answered 01/08/2009 by: tinkerbell
Senior Yellow Belt

Please log in to comment
0
It looks like your ISM file has been corrupted for some reason, and given this is a simple package, it might be easiest to start afresh.

However you could try this if you have access to Orca.

Make a backup copy of your ISM just to be on the safe side.

Open Orca and drag and drop your ISM file onto the Orca window.

In Orca click on the Tables .. Add Table menu and hopefully you should see the RemoveFile table listed with a checkbox alongside.

Tick the checkbox and click OK. Save the ISM file.

Exit ORCA and open the ISM in InstallShield.

Build the project and then try running validation again to see if this gets you any further.

Regards,

Spartacus
Answered 01/08/2009 by: spartacus
Black Belt

Please log in to comment
0
Hi Spartacus,

I just captured only one file in C:\Windows\System32 which is msvbvm60.dll and some dll files also which is located in C:\Windows\LastGood\system32. I don't think that my ISM file is corrupted. I just delete uneccessary registries captured pertaining to LastGood. I deliver msvbvm60.dll as file instead of mergemodule because file has higher version than the mergemodule.

I'll try what have you said. Thanks!

Tink
Answered 01/08/2009 by: tinkerbell
Senior Yellow Belt

Please log in to comment
0
I tried to deliver msvbvm60.dll as merge module and then ISM continue its validation. Is it ok to deliver the file with higher version as "merge module" for the application to continue its validation?
Answered 01/08/2009 by: tinkerbell
Senior Yellow Belt

Please log in to comment
0
Shouldn't be a problem however it may fail if the developer has hardcoded some function calles or uses function not available any longer.
Answered 01/08/2009 by: AngelD
Red Belt

Please log in to comment
0
<snip>and some dll files also which is located in C:\Windows\LastGood\system32. <snip>I just delete uneccessary registries captured pertaining to LastGood. That folder should be in your list of excluded folders. The OS deals with that and MSIs have no business futzing in there.
Answered 01/09/2009 by: VBScab
Red Belt

Please log in to comment
0
Hi VBScab,
Are all the Folders inside the directory C:\Windows\LastGood all trashes??
how about C:\Windows\LastGood\INF\??

Regards

josa
Answered 01/15/2009 by: Josa
Senior Yellow Belt

Please log in to comment
0
Whoa! Not trash, no! Just exclude the LastKnownGood folder and sub-folders from your captures.
Answered 01/15/2009 by: VBScab
Red Belt

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