[wix-users] ManagedPipeline property of Application Pool in IIS getting reset during Major Upgrade

[Ven H]

Thanks a lot Jacob. Appreciate your help. So, shall I raise a bug?

Regards,
Venkatesh

On Wed, Jan 10, 2018 at 11:41 PM, Hoover, Jacob <Jacob.Hoover at greenheck.com>
wrote:

> Yes it’s part of Wix. - https://github.com/wixtoolset/
> wix3/blob/develop/src/ext/ca/serverca/scaexec/scaexecIIS7.cpp
>
>
>
> It may be a Wix bug, or it may just be designed that way. I wasn’t the
> author of this, so I don’t know much in the way of the details. To me, it
> seems like we are missing a read for that setting, which I believe has to
> happen once elevated, due to some IIS strangeness.
>
>
>
> (It may be as simple as adding a Iis7GetPropertyString call and only set
> the default if it doesn’t already have a value.)
>
>
>
>
>
> *From:* Ven H [mailto:venh.123 at gmail.com]
> *Sent:* Tuesday, January 9, 2018 10:30 AM
> *To:* Hoover, Jacob <Jacob.Hoover at greenheck.com>
> *Cc:* WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
>
> *Subject:* Re: [wix-users] ManagedPipeline property of Application Pool
> in IIS getting reset during Major Upgrade
>
>
>
> Thank you Jacob. Is this file part of WixToolSet? So, does this mean that
> there is a bug, either in IIS or WiX? Sorry, but honestly, I didn't
> understand much, as I am new to WiX. Can you please be kind enough to
> elaborate a bit on that and also, if possible, shed some light on solving
> this issue?
>
>
> Regards,
> Venkatesh
>
>
>
> On Mon, Jan 8, 2018 at 10:36 PM, Hoover, Jacob <Jacob.Hoover at greenheck.com>
> wrote:
>
> I believe it could be caused by:
>
>
>
> scaexecIIS7.cpp @ Line 3573:
>
>     //For WiX II6 /ABO compat we will default managedPipelineMode="Classic"
>
>     hr = Iis7PutPropertyString(pAppPoolElement, IIS_CONFIG_PIPELINEMODE,
> L"Classic");
>
>
>
> But I don’t know the intent behind the action, so I am not entirely
> positive.  If the CA doesn’t have a pipeline mode authored, one would think
> the scheduling/immediate CA would have read the current state and placed
> it’s vale on the CA.  But I know IIS did some wonky stuff like requiring
> admin to read it’s configuration.
>
>
>
> Either way, I don’t have a pool of IIS boxes to work against, so I am not
> much help from here.
>
>
>
> *From:* Ven H [mailto:venh.123 at gmail.com]
> *Sent:* Monday, January 8, 2018 10:49 AM
> *To:* WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
> *Cc:* Hoover, Jacob <Jacob.Hoover at greenheck.com>
>
>
> *Subject:* Re: [wix-users] ManagedPipeline property of Application Pool
> in IIS getting reset during Major Upgrade
>
>
>
> Any help?
>
>
> Regards,
> Venkatesh
>
>
>
> On Fri, Jan 5, 2018 at 8:30 AM, Ven H <venh.123 at gmail.com> wrote:
>
> In both the cases (Install & Upgrade MSIs), I am not setting this property
> and the same applies to ManagedRuntimeVersion also. But
> ManagedRuntimeVersion setting is retained whereas ManagedPipelineMode is
> not.
>
>
> Regards,
> Venkatesh
>
>
>
> On Thu, Jan 4, 2018 at 11:23 PM, Hoover, Jacob via wix-users <
> wix-users at lists.wixtoolset.org> wrote:
>
> But what does the @ManagedPipelineMode in your updated installer look like?
>
>
> -----Original Message-----
> From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf
> Of Edwin Castro via wix-users
> Sent: Thursday, January 4, 2018 10:55 AM
> To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
> Cc: Edwin Castro <egcastr at gmail.com>
> Subject: Re: [wix-users] ManagedPipeline property of Application Pool in
> IIS getting reset during Major Upgrade
>
> It's been a long time since I've worked with App Pools in WiX but is your
> upgrade deleting the old App Pool and creating a new one? Try checking the
> verbose log for signs of the App Pool getting deleted.
>
> --
> Edwin G. Castro
>
>
> On Thu, Jan 4, 2018 at 8:12 AM, Ven H via wix-users <
> wix-users at lists.wixtoolset.org> wrote:
>
> > I am creating an Application Pool through MSI. The Application Pool
> > has Id, Name and some advanced properties set like CpuLimit,
> > MaxWorkerProcesses and so on, but I am not setting the values for the
> > basic settings like ManagedPipeline or ManagedRuntimeVersion. When the
> > application pool gets created, the properties are set as expected.
> > Once the application pool is created, I also manually set some other
> > properties also, including ManagedPipeline. The default for the
> > ManagedPipeline is Classic and I changed it to Integrated.
> >
> > In my Upgrade MSI, I am setting some other properties on the App Pool.
> > When the Upgrade MSI runs, it updates the other properties as
> > expected, retains the changes done manually. So far so good. But, the
> > ManagedPipeline property is getting reset to Classic, though I had set
> > it to Integrated manually after installation, even though other
> > manually updated settings are retained. Can anyone please help me fix
> this?
> >
> > Regards,
> > Venkatesh
> >
> > ____________________________________________________________________
> > WiX Toolset Users Mailing List provided by FireGiant
> > http://www.firegiant.com/
> >
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant
> http://www.firegiant.com/
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant
> http://www.firegiant.com/
>
>
>
>
>
>
>