[wix-users] Creating registry entry fails from running from MSI but works in Bundle? [Public]

[Justin Cox]

hmm, odd that it was working with bootstrap and not MSI.  That's usually a
tell-tale sign of an elevation issue. Glad you got it working!

On Thu, Feb 2, 2017 at 11:08 AM Steven Ogilvie <Steven.Ogilvie at titus.com>
wrote:

> Classification: Public
> Aha fixed the issue, which you helped Justin by making me look at the
> registry table using Orca :)
>
> One property was being set but I did not have the other property being set
> :(
> i.e. <Property Id="DISABLE_SAVE_OFFICE" Secure="yes" Value="1"/>
>
> Fixed and working :)
>
> Cheers,
>
> Steve
>
>
> This message has been marked as Public by Steven Ogilvie on February 2,
> 2017 2:07:49 PM. Classification provided by TITUS.
>
>
>
>
>
> -----Original Message-----
> From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf
> Of Justin Cox
> Sent: February 2, 2017 1:24 PM
> To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
> Subject: Re: [wix-users] Creating registry entry fails from running from
> MSI but works in Bundle?
>
> Still won't give you the elevation.  It's part of the UAC and requesting.
> There's no way to elevate the action out of sequence.
>
> On Thu, Feb 2, 2017 at 10:22 AM Steven Ogilvie <Steven.Ogilvie at titus.com>
> wrote:
>
> > I ran the MSI's via an elevated CMD prompt (run as Administrator,
> > logged in as user with local/domain Administrator rights), it is not a
> > custom action is is the WiX RegistryKey/ RegistryValue elements>
> >
> >
> > -----Original Message-----
> > From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On
> > Behalf Of Justin Cox
> > Sent: February 2, 2017 1:20 PM
> > To: WiX Toolset Users Mailing List (wix-users at lists.wixtoolset.org) <
> > wix-users at lists.wixtoolset.org>
> > Subject: Re: [wix-users] Creating registry entry fails from running
> > from MSI but works in Bundle?
> >
> > Steve, since you're writing to HKLM, it requires elevated privileges.
> > Ensure that this is run during the InstallExecute sequence.
> > Bootstrapper gives you elevated privileges during the whole process,
> > so it must be a scheduling issue.
> >
> > On Thu, Feb 2, 2017, 10:14 AM Steven Ogilvie
> > <Steven.Ogilvie at titus.com>
> > wrote:
> >
> > > Hi folks,
> > >
> > > I have a registry that is failing when running the MSI within an
> > > elevated CMD prompt.
> > > Running the installer via the Bootstrapper works...
> > >
> > > I have 2 features, and each feature writes to the same parent
> > > registry key, 1 feature creates the string value the other doesn't
> > > (they are almost exactly the same) it gives an error:
> > >
> > > "Error 1406. Could not write value
> > > AllowUnrestrictedMicrosoftOfficeFunctionality to key
> > > \SOFTWARE\Policies\Titus Labs.  System error .  Verify that you have
> > > sufficient access to that key, or contact your support personnel."
> > >
> > > The full log is:
> > > MSI (s) (C4:8C) [11:27:31:842]: Executing op:
> > > RegOpenKey(Root=-2147483646 <(214)%20748-3646> <(214)%20748-3646>
> > ,Key=SOFTWARE\Policies\Titus
> > > Labs,,BinaryType=0,,)
> > > MSI (s) (C4:8C) [11:27:31:842]: Executing op:
> > > RegAddValue(Name=AllowUnrestrictedMicrosoftOutlookFunctionality,Valu
> > > e=
> > > #1,)
> > > WriteRegistryValues: Key: \SOFTWARE\Policies\Titus Labs, Name:
> > > AllowUnrestrictedMicrosoftOutlookFunctionality, Value: #1 MSI (s)
> > > (C4:8C) [11:27:31:842]: Executing op: RegCreateKey()
> > > WriteRegistryValues: Key: \SOFTWARE\Policies\Titus Labs, Name: , Value:
> > > MSI (s) (C4:8C) [11:27:31:842]: Executing op:
> > > RegAddValue(Name=AllowUnrestrictedMicrosoftOfficeFunctionality,Value
> > > =#
> > > ,)
> > > WriteRegistryValues: Key: \SOFTWARE\Policies\Titus Labs, Name:
> > > AllowUnrestrictedMicrosoftOfficeFunctionality, Value: # MSI (s)
> > > (C4:8C) [11:27:31:842]: Note: 1: 1406 2:
> > > AllowUnrestrictedMicrosoftOfficeFunctionality 3:
> > > SOFTWARE\Policies\Titus Labs Error 1406. Could not write value
> > > AllowUnrestrictedMicrosoftOfficeFunctionality to key
> > > \SOFTWARE\Policies\Titus Labs.  System error .  Verify that you have
> > > sufficient access to that key, or contact your support personnel.
> > > MSI (s) (C4:8C) [11:40:43:259]: Product: TITUS Classification --
> > > Error 1406. Could not write value
> > > AllowUnrestrictedMicrosoftOfficeFunctionality
> > > to key \SOFTWARE\Policies\Titus Labs.  System error .  Verify that
> > > you have sufficient access to that key, or contact your support
> personnel.
> > >
> > > The registry key/component is:
> > >
> > > <!-- Disable Save Registry key -->
> > >       <Component Id="cmp_DisableSave_Registry_TCO"
> > > Guid="{721924EB-02F2-4BB1-8ED5-4F067CDE79D2}" KeyPath="yes">
> > >         <RegistryKey Id="DisableSave_Registry_TCO" Root="HKLM"
> > > Key="SOFTWARE\Policies\Titus Labs" ForceCreateOnInstall="yes">
> > >           <RegistryValue Type="integer"
> > > Name="AllowUnrestrictedMicrosoftOfficeFunctionality"
> > > Value="[DISABLE_SAVE_OFFICE]"/>
> > >         </RegistryKey>
> > >       </Component>
> > >
> > > I have a similar registrykey/value being written by another feature
> > > and it works fine (it is run before this feature)
> > >
> > > Any help would be appreciated...
> > >
> > > Steve
> > >
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant
> http://www.firegiant.com/
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant
> http://www.firegiant.com/
>