Windows Forum

Ask something
Discussion Locked

XP Windows Installer Problems ?

0 helpful
2 replies

by l-plate

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Is there a known issue with Windows Installer for XP SP2 systems ?

New build XP SP2 MCE machine

Problem is consistently repeatable failure to install any third party application software which uses Installshield i.e. most everything

During the configuring Windows Installer process, the progress bar halts half way across and error code 1628 is reported (task manager shows the installer application as still running O.K.)

Some software applications, particularly legacy programs using dedicated installers (e.g. WISE) install and run with no problem - it seems that anything trying to install via XP's installer is doomed to failure ?

Surely this must be a known issue - anyone help please ?

2 replies

by dmiles

Cause 1
An InstallScript MSI (formerly Standard) project has two features with the same name but defined in different cases. For example, DefaultFeature and defaultfeature. In this scenario, iDriver.exe is not cleaned up at the end of the installation, and the uninstallation log file becomes corrupted.

Resolution
Use the Windows Task Manager to end the iDriver.exe process. If you are not sure how to access the Task Manager, see the Additional Information section.

Delete the .ilg (uninstallation log) file from the \InstallShield Installation Information\{Product Code} directory. If you do not know your project's Product Code, it can be found under the General Information > Product Properties view in the InstallShield Development Environment (IDE).

Search the project for duplicate features. This can be done via the Setup Design, Features, or Direct Editor views. If any duplicates are found, one of them must be renamed, and the release must be rebuilt.

--------------------------------------------------------------------------------

Cause 2
The installation has at least one child feature whose Required Features property is set to either a Parent or GrandParent feature.

Resolution
By default, parent features and grandparent features are forced to be required if the subfeature is selected, so this does not need not be done explicitly.

Select the Setup Design view.

For each subfeature, check its Required Features property and verify that is value is None Selected. Change the value in this field if necessary.

This discussion is closed to new replies.