ksmith93
Posts: 10
Joined: Wed Sep 13, 2006 5:14 pm

Bootstrapper Sees Prerequisites as Still Not Installed?

Hello, thanks for a great product in AI. I’m using AI enterprise 4.3, registered.

I have two prerequisites configured within my AI project. One prerequisite has a file version install condition configured for [SystemFolder]msi.dll. The minimum required version is 3.0.3790.2180, and the maximum required version is blank. The other prerequisite has a registry value install condition configured for HKLM\SOFTWARE\Microsoft\.NETFramework\policy\v2.0\50727. The minimum required version is 50727, and the maximum required version is blank.

Both of my prerequisites appear to launch correctly by the bootstrapper. But after both prerequisites are installed, the bootstrapper still sees them as uninstalled, and displays this message: "After launching all packages some required prerequisites are still missing. Press Back to return to the prerequisites list."

Thank you for your support.

(Please see also this link http://www.advancedinstaller.com/forums ... php?t=1530 for contextual info and cross-reference.)
Ionut
Posts: 605
Joined: Tue Nov 22, 2005 11:29 am
Contact: Website

Hi,

Sorry for the late reply - this is indeed a very tricky issue.

Because the Windows Installer Prerequisite replaces a system DLL ("msi.dll"), this file is updated only after the system is restarted (although processes created after WI is updated use the new version of this DLL).

The WI setup spawns an "update.exe" child process which maps "msi.dll" in its address space (the free utility "Process Explorer" from Sysinternals can be used to determine this). From what we have tested, this happens when updating the Windows Installer engine on Windows XP and Windows 2003. On these systems, the detection condition is evaluated correctly after the Prerequisite is installed.

Now, the interesting part: on Windows 2000, "msi.dll" is mapped in the address space of the process in which the bootstrapper runs (instead of the address space of the "update.exe" child process). We could not determine why this happens. As a consequence, the condition does not evaluate correctly after WI is updated.


There are 2 possible solutions for this:

1. Allow the system to be restarted after WI is installed by omitting the "/norestart" parameter.

2. Use another detection criteria for Windows Installer - namely, the version of "msiexec.exe" (although this might be advised against on some forums). In this case, you need to set the Minimum Version to "3.0" in the "Install Conditions" tab of the "Edit Prerequisite" dialog.

Regards,
Ionut
Denis Toma
Advanced Installer Team
http://www.advancedinstaller.com/

Return to “Common Problems”