Software Deployment

Hi,

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

Tink

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

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

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?

Shouldn't be a problem however it may fail if the developer has hardcoded some function calles or uses function not available any longer.

<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.

Hi VBScab,
Are all the Folders inside the directory C:\Windows\LastGood all trashes??
how about C:\Windows\LastGood\INF\??

Regards

josa

Whoa! Not trash, no! Just exclude the LastKnownGood folder and sub-folders from your captures.