5 replies to this topic

[jay_strain]

After using IS Express 4 for multiple deployments of a VB6 application, our most recent deployment now causes the Windows Installer to appear whenever the runtime program is started. Is there a quick way to fix this? Where did we go wrong??

Appreciate your feedback,
-- Jay

[Stefan Krueger]

Take a look at the Windows Event log. It should contain information which component (GUID) for which product (GUID) triggers the auto repair.

[Glytzhkof]

There are a number of cases where self-repair may kick in unexpectedly: http://forum.install...?showtopic=3974

[jay_strain]

Dear InstallShield Guys,

Excellent suggestions and thank you very much!!

The Event Viewer showed that we had modified our existing InstallShield project to remove several temporary directories no longer in use in our new application. The InstallShield script continued to maintain links to the temporary directories (e.g. "C:\Temp\Chinese") and was unable to find them. The updated IS script continued to look for these folders although they were no longer necessary and kept prompting the Windows Installer on the computer on which the new installation had occurred.

We added the temporary files back to the script and everything is back to normal.

Is there a way we can prevent this in the future?? Secrets to deleting temp files from the IS script??

Thanks Again,
-- Jay

[Glytzhkof]

Self-repair should only occur for folders created as part of components (hard coded as part of the component). If you need to create "empty folders" you could use the "CreateFolder" table instead.

From the SDK:
"...no automatic removal is triggered if the folders become empty. In contrast, folders created by the installer but not listed in this table are removed when they become empty".

Edited by Glytzhkof, 21 January 2004 - 07:39.

[Glytzhkof]

Please check this short article for more on self-repair problems and ways to resolve it: http://stackoverflow...-repair/6066263