I would like to thank Phil (and others on this list) for the assistance in
tracking down this problem.  The core problem is related to the following
attempt to write this registry value when the value of the SDA property is
not an integer:

<RegistryValue Root="HKMU" Key="$(var.Release_CompanyRegKey)" Name="SDA"
Value="[SDA]" Type="integer" KeyPath="yes" />

It was introduced several weeks ago when I changed how the SDA property was
initialized.  I incorrectly assumed that my mba would initialize this
property's value.    However when the on-demand install kicks in after the
initial install of the burn bundle, (with this msi marked to be published as
an advertised feature), this property was not initialized and was blank. 
(This is why this problem only showed up when an on-demand, after a
first-install of the bundle was done.  In all other scenarios the mba
provided a default value.).

The msi error (reporting an access problem with the key location) was
related to the attempt at runtime to resolve #[SDA] when SDA was an
uninitialized string and not a valid integer.  The permissions error did not
relate to the location of where the registry value was to be created or the
context of the user as implied in the message.

Thanks again for your help in understanding this issue.  Phill



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/advertised-install-and-user-permissions-tp7594058p7594127.html
Sent from the wix-users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to