Installshield component getting installed even when feature is not selected

[zort03]

I have an installer with 2 features (Server and Client) and both features have multiple components.

similar to the following -

Server

• Component1
• Component2

Client

• Component3
• Component4

Both Server and Client are optional features and user can choose to install only one or both. The problem is Component3 under Client is getting installed even when Client is not selected. (all other components are working correctly.) I've compared Component3 and Component4 in Direct Editor and I cannot find anything different between those.

the following log is written when Server feature only is selected. (Component3 should not get installed)

MSI (s) (FC:8C) [18:51:40:671]: Doing action: InstallValidate
Action 18:51:40: InstallValidate. Validating install
Action start 18:51:40: InstallValidate.
MSI (s) (FC:8C) [18:51:40:671]: PROPERTY CHANGE: Deleting MsiRestartManagerSessionKey property. Its current value is 'a50da1074c5018429e3357b5024ea9c7'.
MSI (s) (FC:8C) [18:51:40:671]: Feature: Server; Installed: Absent; Request: Local; Action: Local
MSI (s) (FC:8C) [18:51:40:671]: Feature: Client; Installed: Absent; Request: Null; Action: Null
MSI (s) (FC:8C) [18:51:40:671]: Component: Component1; Installed: Absent; Request: Local; Action: Local
MSI (s) (FC:8C) [18:51:40:671]: Component: Component2; Installed: Absent; Request: Local; Action: Local
MSI (s) (FC:8C) [18:51:40:671]: Component: Component3; Installed: Absent; Request: Local; Action: Local
MSI (s) (FC:8C) [18:51:40:671]: Component: Component4; Installed: Absent; Request: Null; Action: Null

the following log is written when Client feature only is selected. (Correct Behaviour)

MSI (s) (28:60) [21:26:02:170]: Doing action: InstallValidate
Action 21:26:02: InstallValidate. Validating install
Action start 21:26:02: InstallValidate.
MSI (s) (28:60) [21:26:02:170]: PROPERTY CHANGE: Deleting MsiRestartManagerSessionKey property. Its current value is '8200136a1315f84ea9c479766c5b10ae'.
MSI (s) (28:60) [21:26:02:170]: Feature: Server; Installed: Absent; Request: Null; Action: Null
MSI (s) (28:60) [21:26:02:170]: Feature: Client; Installed: Absent; Request: Local; Action: Local
MSI (s) (28:60) [21:26:02:170]: Component: Component1; Installed: Absent; Request: Null; Action: Null
MSI (s) (28:60) [21:26:02:170]: Component: Component2; Installed: Absent; Request: Null; Action: Null
MSI (s) (28:60) [21:26:02:170]: Component: Component3; Installed: Absent; Request: Local; Action: Local
MSI (s) (28:60) [21:26:02:170]: Component: Component4; Installed: Absent; Request: Local; Action: Local

Each component contains multiple library files (.dll) and I just found out that is not a good practice. But could that be the reason why this is happening?

Any clues or assistances would be appreciated.

Thanks in advance.

[varul]

Could you please check the component3 is not linked to feature1 and the same file in component 3 is not shared or added to other component like comp1 and comp2, 

How you are validating the files from comp3 are getting installed by checking the presence of files or log

Could you please the project ism file, or a sample ism to replicate the issue, so  we can check the ism file correctly configured or not.

[zort03]

Thank you for your reply.

I have checked "FeatureComponents" table and Component3 is not linked to Server feature. Each components is composed of files from separate folders. (Component1 contains only files from folder1, Component2 from folder2, etc.,). Although the same file from the same path is not shared between them, the same file from different folders (.net core dlls) are shared among them.

I have confirmed the files from Component3 is installed by checking both presence of files and log. All files under Component3 are installed when only Server feature is selected and they are also deleted when uninstalling.

I'll try to replicate the issue in a new sample project this evening and will upload here if the same problem occurs.