Transform will apply properties, but not write to registry
I am trying to build a Transform with InstallShield for OSIsoft PI-ProcessBook. I have extracted the vendor supplied MSI from the setup.exe, built my simple transform and only part of it seems to work. I have it change a few properties (works) and want it to also write a few registry entries in HKLM (not working). It does not fail to install, or give any errors. My feature and component are called BG_Branding and this is an excerpt from the log
MSI (s) (C0:30) [20:25:01:214]: Feature: Complete; Installed: Absent; Request: Local; Action: Local
MSI (s) (C0:30) [20:25:01:214]: Feature: SQC; Installed: Absent; Request: Local; Action: Local
MSI (s) (C0:30) [20:25:01:214]: Feature: BG_Branding; Installed: Absent; Request: Null; Action: Null
MSI (s) (C0:30) [20:25:01:214]: Feature: PBAdvertise; Installed: Absent; Request: Local; Action: Local
And
MSI (s) (C0:30) [20:25:01:214]: Component: __OfficeCore.D0DF3458_A845_11D3_8D0A_0050066; Installed: Null; Request: Local; Action: Local
MSI (s) (C0:30) [20:25:01:214]: Component: __BG_Branding65; Installed: Null; Request: Null; Action: Null
MSI (s) (C0:30) [20:25:01:214]: Component: __PBPROP1.DLL65; Installed: Null; Request: Local; Action: Local
To me it looks like the Request should be local and the Action should be local, but I do not know where these values come from.
Any help is greatly appreciated!
Answers (4)
Verify that the feature you created is set to be installed in the feature table and/or condition table. If the original package does not contain registry keys, check that the InstallExecuteSequence contains the WriteRegistryValues (and RemoveRegistryValues) standard actions.
Try contacting their support, they should give you something about the installations just like in this link. You must be a registered users though..
http://techsupport.osisoft.com/Download+Center/Download+Center.htm
Have you verified that the feature you created is set to be installed in the feature table and/or condition table? Here is a good link to check out http://msdn.microsoft.com/en-us/library/windows/desktop/aa368585(v=vs.85).aspx
If the original package does not contain registry keys, have you checked that the InstallExecuteSequence contains the WriteRegistryValues (and RemoveRegistryValues) standard actions?
Some very good suggestions have already been posted by henrik and pjgeutjens.
However, I would like to say that create a new component in the parent feature which will definitely install.
I have never seen a scenario like this.
