cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Pilgrim

Problems with FeaturePrerequisites during minor update

I have a product for which I have a 32bit and a 64bit Installer. Operating system for the installation is in both cases Windows 7. For both setups I use Feature Prerequisites to install the VC++ 2010 SP1 redistributable. As I learned this is done by a custom action called ISInstallPrerequisites. This CA checks the value of the properties SETUPEXEDIR and SETUPEXENAME which are set when starting the setup.exe. This behavior seems to be different with 32bit or 64bit setups. In both cases I can see in the logfile, that the properties SETUPEXEDIR and SETUPNAME are set to the correct values, but ISInstallPrerequisites seems to behave different:

64bit
Snippets of the logfile:
MSI (c) (8C:64) [09:34:34:455]: PROPERTY CHANGE: Adding SETUPEXEDIR property. Its value is 'C:\Users\sam\AppData\Local\Temp\rl4egnod.tfb\Proom_x64'.

MSI (c) (8C:64) [09:34:52:664]: Doing action: ISInstallPrerequisites
Aktion 09:34:52: ISInstallPrerequisites.
Aktion gestartet um 09:34:52: ISInstallPrerequisites.MSI (c) (8C:B4) [09:34:52:706]: Invoking remote custom action. DLL: C:\Users\sam\AppData\Local\Temp\MSIDAF4.tmp, Entrypoint: InstallPrerequisites
InstallShield 09:34:52: Features with associated prerequisites are being installed or advertised. Finding setup.exe...
InstallShield 09:34:52: Looking for setup launcher in 'C:\Users\sam\AppData\Local\Temp\rl4egnod.tfb\Proom_x64' with name 'setup.exe'...
InstallShield 09:34:52: Checking for correct setup launcher 'C:\Users\sam\AppData\Local\Temp\rl4egnod.tfb\Proom_x64\setup.exe'...
InstallShield 09:34:52: Found matching product code in 'C:\Users\sam\AppData\Local\Temp\rl4egnod.tfb\Proom_x64\setup.ini'.

The bevore set properties SETUPEXEDIR and SETUPEXE are evaluated and the installation can continue.

32bit
Snippets of the logfile:
MSI (c) (F8:88) [09:26:06:050]: PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is 'C:\Users\VW34E5~1.PRO\AppData\Local\Temp\Proom_2.1_install.log'.
MSI (c) (F8:88) [09:26:06:050]: Command Line: REINSTALL=ALL REINSTALLMODE=vomus IS_MINOR_UPGRADE=1 TRANSFORMS=1031.MST SETUPEXEDIR=C:\Users\vw.PROCAD_KA\AppData\Local\Temp\j4i3yts2.znt\Proom SETUPEXENAME=setup.exe CURRENTDIRECTORY=C:\Program Files\PROCAD\Proom CLIENTUILEVEL=0 CLIENTPROCESSID=5624

MSI (c) (F8:88) [09:26:06:051]: Ignoring disallowed property SETUPEXEDIR
MSI (c) (F8:88) [09:26:06:051]: Ignoring disallowed property SETUPEXENAME

MSI (c) (F8:88) [09:26:08:271]: Doing action: ISInstallPrerequisites
Aktion 09:26:08: ISInstallPrerequisites.
Aktion gestartet um 09:26:08: ISInstallPrerequisites.
MSI (c) (F8:FC) [09:26:08:320]: Invoking remote custom action. DLL: C:\Users\VW34E5~1.PRO\AppData\Local\Temp\MSI23C6.tmp, Entrypoint: InstallPrerequisites
InstallShield 09:26:08: Features with associated prerequisites are being installed or advertised. Finding setup.exe...
InstallShield 09:26:08: Checking SourceList directories for setup launcher...
InstallShield 09:26:08: Last used source: 'C:\Users\vw.PROCAD_KA\AppData\Local\Temp\Temp1_proom.zip\Proom\'
InstallShield 09:26:08: Looking for setup launcher in 'C:\Users\vw.PROCAD_KA\AppData\Local\Temp\Temp1_proom.zip\Proom\' with name 'setup.exe'...
InstallShield 09:26:08: Next source: 'C:\Users\vw.PROCAD_KA\AppData\Local\Temp\Temp1_proom.zip\Proom\'
InstallShield 09:26:08: Asking user to provide setup launcher location...

The property SETUPEXEDIR is not evaluated, and the installation cannot continue.

The 32bit log led me to the opinion, that the properties should be entered in the SecureCustomProperties Property, but I think it makes no sense, because the installation actions for the prerequisites are not executed deffered. Also in both cases (32bit and 64bit) they are not entered in SecureCustomProperties.
Or could it be a problem with UAC?

Any other hints?

Best regards
Barbara
Labels (1)
0 Kudos
1 Reply
Highlighted
Pilgrim

SecureCustomProperties

Maybe I found the solution: On all 64bit computers the UAC was turned off, on all 32bit computers the UAC was turned on. This led to the different behavior. I added the properties SETUPEXEDIR and SETUPEXENAME to the Property SecureCustomProperties and it seem to work (but further testing needed).
But: Can somebody from InstallShield explain me this behavior?

Best regards
Barbara
0 Kudos