/build/static/layout/Breadcrumb_cap_w.png

Reg value set in package not applying

Help needed please,
I'm setting a value in HKEY_Local_Machine in my package (appliying via mst to vendor msi). I'm setting a value of a Key to TRUE.
When installing the application the value of the Key is blank, any ideas why my TRUE value is not being applied?

Cheers

0 Comments   [ + ] Show comments

Answers (7)

Posted by: Rheuvel 11 years ago
Brown Belt
0
Run the install again with logging (/lv* <path to logfile>) and check the log afterwards for the following:

1) Is your transform really used? (wrong syntax or typo on command line maybe, log will tell you whether it applied the transform or not)
2) Might be that some Custom Action will kick in after the registry entry is set and changes it. (search the CA table for suspicious CA's and again, the log tell you in what order it happened)
3) If it isn't 1 or 2, maybe a system search for some value, or an old version of the app that's causing it, whatever...? Can't tell with the current information.

So if this isn't helping at all, give us some more details. Like, which application/regfile, the commandline you used, is there a previous version involved (uninstall or upgrade)...


Good luck :)
Posted by: tegai1 11 years ago
Senior Yellow Belt
0
hi,
Thanks for the reply [:D]

1. Transform is working fine as it applies with the shortcut changes made.
2. Application is called Cabri2Plus (Educational Software)
3. Actual Reg change needed is: [HKEY_LOCAL_MACHINE\SOFTWARE\Cabri2p1.3] "Key"="TRUE"
4. ON install it installs as: [HKEY_LOCAL_MACHINE\SOFTWARE\Cabri2p1.3] "Key"=""
5. As you suggested the problem stinks of CA override. I'll have another look although I'm pretty new to this so knowing what I'm looking for is my main problem.

Thanks again
Posted by: tegai1 11 years ago
Senior Yellow Belt
0
under execute immediate I have a CA "WriteRegistryValues" but it's greyed out. Does this look likely to be my problem?

Bit of backgroud to the app:
The application requires activating post install, this has been captured and added to the transform. This now all works as expected providing I add the TRUE value to this reg entry, I just need my package to apply this change and it's job done!
Posted by: Rheuvel 11 years ago
Brown Belt
0
Hmm, greyed out? That's new to me. And taking out a CA called WriteRegistryValues sounds... well... risky too.

You could always make your own CA that re-writes the value to TRUE and have it execute after WriteRegistryValues (talking about quick&dirty).
Posted by: tegai1 11 years ago
Senior Yellow Belt
0
sorry, it's a standard action not a CA
Posted by: tegai1 11 years ago
Senior Yellow Belt
0
hi,
Thanks for all your help with this. I’ve fixed the problem but not via CA. Basically I removed a property in the AppSearch table and reglocator table and then changed the value of the key in the registry table.
I guess changing the value in the regitry table was not sufficient as the property in the other two tables were superseding them?

I'm happy it works now, but if anyone would case to give a true explanation as to what was going on, I would be greatly appreciative.

Cheers again for all your help
Posted by: nheim 11 years ago
10th Degree Black Belt
0
Hi Gwyn,
most likely, the component, which installs the registry key, has a condition on it, which will be set through appsearch/reglocator.
Look at the last column of the registry table line in question and search it in the component table. Then have a look at the condition column of this line.
Regards, Nick
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ