Property value for Unchecking Checkbox
Hello -
Package with which I am facing issue doesnt allow hiding dialogues in it,its a vendor MSI.
I have to do little customization which is simple- inserting server name and uncheck one checkbox to "Automatically check updates at program startup.
I am creating MST for this application using Installtailor where as required I am unchecking this checkbox,but still when I run MSI along with customized MST this checkbox is auto-selected.
I hv checked properties ,there are two properties:
RTA_CLIENT_AUTO_UPDATE = N (while creating MST when I check for updates its value in MST shows Y and now when I didnt check that box its N)
UIAutoUpdates=1 (When I go to dialogue box and double click property value this is the property which is always set)
I am not sure what extra i should do so that I can successfully Uncheck this checkbox while installation.
These three lines I am copying from ControlEvent table:
Where dlg_auto_upgrade is dialogue box which contain this checkbox.
"dlg_auto_upgrade","btn_next","[RTA_CLIENT_AUTO_UPDATE]","Y","UIAutoUpdates=1","2"
"dlg_auto_upgrade","btn_next","[RTA_CLIENT_AUTO_UPDATE]","N","Not (UIAutoUpdates=1)","1"
"dlg_auto_upgrade","btn_next","[dlg_ready_to_install_bk]","dlg_auto_upgrade","1","3"
Please suggest how do I do it to uncheck this checkbox.
Package with which I am facing issue doesnt allow hiding dialogues in it,its a vendor MSI.
I have to do little customization which is simple- inserting server name and uncheck one checkbox to "Automatically check updates at program startup.
I am creating MST for this application using Installtailor where as required I am unchecking this checkbox,but still when I run MSI along with customized MST this checkbox is auto-selected.
I hv checked properties ,there are two properties:
RTA_CLIENT_AUTO_UPDATE = N (while creating MST when I check for updates its value in MST shows Y and now when I didnt check that box its N)
UIAutoUpdates=1 (When I go to dialogue box and double click property value this is the property which is always set)
I am not sure what extra i should do so that I can successfully Uncheck this checkbox while installation.
These three lines I am copying from ControlEvent table:
Where dlg_auto_upgrade is dialogue box which contain this checkbox.
"dlg_auto_upgrade","btn_next","[RTA_CLIENT_AUTO_UPDATE]","Y","UIAutoUpdates=1","2"
"dlg_auto_upgrade","btn_next","[RTA_CLIENT_AUTO_UPDATE]","N","Not (UIAutoUpdates=1)","1"
"dlg_auto_upgrade","btn_next","[dlg_ready_to_install_bk]","dlg_auto_upgrade","1","3"
Please suggest how do I do it to uncheck this checkbox.
0 Comments
[ + ] Show comments
Answers (20)
Please log in to answer
Posted by:
anonymous_9363
14 years ago
How did you set the property, though? Many apps have Custom Actions which set properties to the required default (in effect ignoring the Property table value) so, if you just changed the Property table's value, it might be ignored anyway. Try a Type 51 Custom Action in the UI sequence.
Also, since the values are being set in the UI, they will be completely ignored in any silent - or partially silent - install. So, if your ultimate aim is to install totally silently, you should verbosely log the install and see what the public property RTA_CLIENT_AUTO_UPDATE gets set to. Once you know that, use that property instead.
Also, since the values are being set in the UI, they will be completely ignored in any silent - or partially silent - install. So, if your ultimate aim is to install totally silently, you should verbosely log the install and see what the public property RTA_CLIENT_AUTO_UPDATE gets set to. Once you know that, use that property instead.
This application can't be installed with /qn switch (Completely silent)Unlikely. I have yet to see an MSI which couldn't be installed silently. It might take some work to force it into cooperating but it's certainly possible. Normally, this means that the package author has a bunch of CAs in the UI sequence which he/she was too stupid or ignorant to copy into the Execute sequence (or force to run at least once).
Posted by:
raviray
14 years ago
This is what I found in logs:
MSI (s) (E0:30) [17:14:40:207]: Doing action: IcaInitSetup
Action ended 17:14:40: CostFinalize. Return value 1.
MSI (s) (E0:30) [17:14:40:207]: Transforming table CustomAction.
MSI (s) (E0:30) [17:14:40:207]: Transforming table Binary.
MSI (s) (E0:0C) [17:14:40:285]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI202.tmp, Entrypoint: IcaInitSetup
Action start 17:14:40: IcaInitSetup.
MSI (s) (E0!90) [17:14:48:834]: PROPERTY CHANGE: Modifying ABC_SRVR_NAME property. Its current value is 'ABCXYZ123'. Its new value: 'ABC123'.
MSI (s) (E0!90) [17:14:48:850]: PROPERTY CHANGE: Modifying ABC_SRVR_IP property. Its current value is '10.XXX.AB.ZZ'. Its new value: '10.LMN.OP.QR'.
IcaInitSetup {
Is new install, maintenance run, or minor upgrade. Installdir resolved internally.
MSI (s) (E0!90) [17:14:48:865]: PROPERTY CHANGE: Adding UIAutoUpdates property. Its value is '1'.
MSI (s) (E0!90) [17:14:48:865]:PROPERTY CHANGE: Modifying ABC_CLIENT_AUTO_UPDATE property. Its current value is 'N'. Its new value: 'Y'.
No ABC server IP was read from the SocketClient2_1 key. The string was null. Server name and IP properties were not set.
}
how should I go about this!!
Action ended 17:14:40: CostFinalize. Return value 1.
MSI (s) (E0:30) [17:14:40:207]: Transforming table CustomAction.
Action start 17:14:40: IcaInitSetup.
MSI (s) (E0!90) [17:14:48:834]: PROPERTY CHANGE: Modifying ABC_SRVR_NAME property. Its current value is 'ABCXYZ123'. Its new value: 'ABC123'.
MSI (s) (E0!90) [17:14:48:850]: PROPERTY CHANGE: Modifying ABC_SRVR_IP property. Its current value is '10.XXX.AB.ZZ'. Its new value: '10.LMN.OP.QR'.
IcaInitSetup {
Is new install, maintenance run, or minor upgrade. Installdir resolved internally.
MSI (s) (E0!90) [17:14:48:865]: PROPERTY CHANGE: Adding UIAutoUpdates property. Its value is '1'.
MSI (s) (E0!90) [17:14:48:865]:
}
Posted by:
aogilmor
14 years ago
from the log it looks like Ian (vbscab) was correct, it's set by a custom action
disable IcaInitSetup (set its condition in the InstallExecuteSequence to 0 or use the remark feature in the wise UI)
it's good that you caught this....reading the logs is a necessary part of windows installer troubleshooting
disable IcaInitSetup (set its condition in the InstallExecuteSequence to 0 or use the remark feature in the wise UI)
it's good that you caught this....reading the logs is a necessary part of windows installer troubleshooting
Posted by:
mekaywe
14 years ago
Posted by:
raviray
14 years ago
Posted by:
sushantnarlawar
14 years ago
Posted by:
raviray
14 years ago
Posted by:
anonymous_9363
14 years ago
Posted by:
aogilmor
14 years ago
yup i'm thinkin' the same thing as vb, some kind of Custom action. sometimes you can get a clue by the name, in the checkbox it was IcaInitSetup but even if the names are totally meaningless you can see what it's doing of you do a verbose log like for the checkbox issue.
Grasshopper, you have now ascended to the next level of windows installer, LOL. [:D]
Grasshopper, you have now ascended to the next level of windows installer, LOL. [:D]
Posted by:
raviray
14 years ago
Me Grasshopper [8|]..ok I will take as compliment..
So here is good news(atleast for me). I found two custom actions which had this condition
(UILevel=2) or (UILevel=3) and (UG_ABC_CLIENT_PATH) and not (UG_ABC_SRVR_PATH)
due to which it was not getting installed completely silent.
I removed it and now I am able to install it completely silent.
Thank you
So here is good news(atleast for me). I found two custom actions which had this condition
(UILevel=2) or (UILevel=3) and (UG_ABC_CLIENT_PATH) and not (UG_ABC_SRVR_PATH)
due to which it was not getting installed completely silent.
I removed it and now I am able to install it completely silent.
Thank you
Posted by:
anonymous_9363
14 years ago
Posted by:
aogilmor
14 years ago
Posted by:
raviray
14 years ago
If in these two custom actions I only remove these UILevel element and not entire condition and click on build and then click ok(In condition builder) it gives me following warning
"There were errors detected in the expression.
Are you sure you want to exit the dialog?"
Is there anything wrong in following expression?
(UG_ABC_CLIENT_PATH) and not (UG_ABC_SRVR_PATH)
Please suggest,
Are you sure you want to exit the dialog?"
Is there anything wrong in following expression?
(UG_ABC_CLIENT_PATH) and not (UG_ABC_SRVR_PATH)
Please suggest,
Posted by:
aogilmor
14 years ago
Posted by:
anonymous_9363
14 years ago
I can't recall exactly but I think Condition Builder is somewhat pedantic about syntax. It may be whining because you have no equivalence check for the properties, e.g something like:
(UG_ABC_CLIENT_PATH > "" ) and not (UG_ABC_SRVR_PATH > "")
whereas the engine itself doesn't care. Run it and see what happens.
(UG_ABC_CLIENT_PATH > "" ) and not (UG_ABC_SRVR_PATH > "")
whereas the engine itself doesn't care. Run it and see what happens.
Posted by:
raviray
14 years ago
(UG_ABC_CLIENT_PATH > "" ) and not (UG_ABC_SRVR_PATH > "")
whereas the engine itself doesn't care. Run it and see what happens.
I tried it and got same error and then I didnt make any change in existing condition (same as vendor msi) and clicked on build ...just to see if this gives error in expression or not and it did.
Why did it give error in existing expression as well?
Posted by:
raviray
14 years ago
Posted by:
anonymous_9363
14 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.