I have a problem with a CA in a feature installation. - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

N\sy
Posts: 2
Joined: Tue Nov 27, 2012 10:36 pm

I have a problem with a CA in a feature installation.

I have a double feature in my installation.

First: Feature Management
  • Management.exe
Second: Feature Service. <- Not selected
  • Service.exe
  • ServiceInstall.cmd
  • ServiceUninstall.cmd
Install.cmd is called in a CA when the feature service is selected. But really should not be called when only the feature management was selected.
Exactly what is happening. How can I make within the installation, the CA will be called only if the corresponding feature will be installed!

Extract from the log.

Code: Select all

...

MSI (s) (48:CC) [11:26:21:682]: PROPERTY CHANGE: Deleting MsiRestartManagerSessionKey property. Its current value is '48bd67a975a385429669b2727402dcf3'.
MSI (s) (48:CC) [11:26:21:682]: Feature: Management; Installed: Absent;   Request: Local;   Action: Local
MSI (s) (48:CC) [11:26:21:682]: Feature: NET_Framework_4.0; Installed: Absent;   Request: Null;   Action: Null		//<-- Not selected
MSI (s) (48:CC) [11:26:21:682]: Feature: Service; Installed: Absent;   Request: Null;   Action: Null				//<-- Not selected
MSI (s) (48:CC) [11:26:21:682]: Feature: Management; Installed: Absent;   Request: Local;   Action: Local			//<-- Selected
MSI (s) (48:CC) [11:26:21:682]: Component: ProductCode; Installed: Absent;   Request: Local;   Action: Local
MSI (s) (48:CC) [11:26:21:682]: Component: AppPath; Installed: Absent;   Request: Local;   Action: Local
MSI (s) (48:CC) [11:26:21:682]: Component: UpgradeCode; Installed: Absent;   Request: Local;   Action: Local
File is called even though it is not included in the feature.

Code: Select all

...

MSI (s) (48:CC) [11:26:23:682]: Note: 1: 2228 2:  3: MsiAssembly 4: SELECT null, null, `Component`.`Component`, `Feature`, `Component`.`ComponentId`, `Component`.`RuntimeFlags` FROM `MsiAssembly`, `Component`, `Feature`  WHERE `MsiAssembly`.`Component_` = `Component`.`Component` AND `MsiAssembly`.`Feature_` = `Feature`.`Feature` AND `MsiAssembly`.`File_Application` = null AND ((`Feature`.`Action` = 1 OR `Feature`.`Action` = 2)  OR (`Feature`.`Action` = 4 AND `Feature`.`Installed` = 0) OR (`Feature`.`Action` = 3 AND (`Feature`.`Installed` = 1 OR `Feature`.`Installed` = 2 OR `Feature`.`Installed` = 4))) 
MSI (s) (48:CC) [11:26:23:682]: Doing action: PublishFeatures
MSI (s) (48:CC) [11:26:23:698]: Doing action: PublishProduct
MSI (s) (48:CC) [11:26:23:729]: Doing action: ServiceInstall.cmd				//<-- Not selected ?????????
MSI (s) (48:CC) [11:26:23:729]: Note: 1: 2753 2: ServiceInstall.cmd 			//<-- Not selected ?????????
MSI (s) (48:CC) [11:26:32:977]: Produkt: ACSCore 2013 -- Fehler 2753. Die Datei 'ServiceInstall.cmd' ist nicht für die Installation markiert.

MSI (s) (48:CC) [11:26:33:071]: Machine policy value 'DisableRollback' is 0
MSI (s) (48:CC) [11:26:33:071]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
Attachments
Image of CA
Image of CA
CA-Image.png (60.85 KiB) Viewed 3407 times
MSI65A7-FehlerInstallation.txt
Log of installation
(106 KiB) Downloaded 249 times
Bogdan
Posts: 2796
Joined: Tue Jul 07, 2009 7:34 am
Contact: Website

Re: I have a problem with a CA in a feature installation.

Hi and welcome to our forums,

You need to customized the execution condition for the custom action. Besides the checkboxes you need to use the button "..." from the "Condition" field. This will open a new dialog, in the lower side of that dialog you will find a set of predefined templates for defining conditions.

There is also a template for defining a condition based on a feature action. So you can double click that predefined condition, it will then show you a new dialog from where you can select the feature based on which you want to create the condition.

Best regards,
Bogdan
Bogdan Mitrache - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
N\sy
Posts: 2
Joined: Tue Nov 27, 2012 10:36 pm

Re: I have a problem with a CA in a feature installation.

Thanks for the answer.

two questions occurred to me.

First: For selection of the component is actually taken into account before that this is associated with a feature.
Select Installed File Dialog
Select Installed File Dialog
SelectInstalledFile.png (15.18 KiB) Viewed 3389 times
Second: Why then is 'Execution State Condition'
ESC.png
ESC.png (4.57 KiB) Viewed 3389 times
'Install' and 'First Time Install' believe that the CA is executed only if the feature is installed!

Why do you have now additionally define a condition? Actually it's already met, met to set 'Source Path'!
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: I have a problem with a CA in a feature installation.

Hello,

Please keep in mind that Windows Installer only verify if the component of the related installed file (used by your "Launch installed file" custom action) will be installed at run-time. But it will not skip the custom action execution if the feature (containing the component of your installed file) will not be selected for install. In this case Windows Installer will throw an "YourFile is not marked for installation" error message, but it will not skip the custom action execution.

So, in order to achieve what you want you should use the solution presented by my colleague in the previous post.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”