[wix-users] Stop & Start Service

[Edwin Castro]

I forgot to mention you should look in your verbose log to determine why it
appears that IIS is restarting quickly and not following the sequence.

--
Edwin G. Castro


On Dec 19, 2017 09:28, "Edwin Castro" <egcastr at gmail.com> wrote:

> Perhaps this webapp is the only one deployed today to this IIS service...
> but IIS can host multiple sites and multiple webapps. Stopping and starting
> IIS affects all sites and webapps which could be really, really bad if
> those other sites and webapps suddenly go down without notice. For this
> reason, IIS supports the concept of AppPools which allows you to separate
> unrelated sites and webapps from each other in different processes. You
> should be creating a unique AppPool that you own so that you can stop and
> start that AppPool rather than the default AppPool or the entire IIS
> service. Perhaps a set of related sites and/or webapps could reuse the same
> AppPool you should do so carefully. Restarting all of IIS is a *bad*
> requirement.
>
> --
> Edwin G. Castro
>
>
> On Dec 19, 2017 08:54, "Ven H via wix-users" <wix-users at lists.wixtoolset.
> org> wrote:
>
>> Thank you Chris. But, does this really work as expected? Because, I see it
>> stops & starts quickly and doesn't seem to follow the sequence. Also, it's
>> a requirement to stop it at beginning and start it back towards the end of
>> the installation.
>>
>> Regards,
>> Venkatesh
>>
>> On Tue, Dec 19, 2017 at 5:47 PM, Christopher Painter <chrpai at iswix.com>
>> wrote:
>>
>> > That's pretty much what MSI was designed to do.  The StopServices action
>> > is run towards the front (1900) and the StartServices action is ran much
>> > later near the end (5900).
>> >
>> >
>> > That said, I typically don't start/stop  IIS unless I really have to.
>> > Usually I'm dealing with ASP.NET applications and modern versions of
>> IIS
>> > are pretty good about noticing changes to a web.config file and
>> > automatically restarting that portion of the web server.
>> >
>> >
>> > https://msdn.microsoft.com/en-us/library/windows/desktop/
>> > aa372038(v=vs.85).aspx
>> > Suggested InstallExecuteSequence (Windows)
>> > <https://msdn.microsoft.com/en-us/library/windows/desktop/aa
>> 372038(v=vs.85).aspx>
>> > msdn.microsoft.com
>> > The suggested action sequences for a basic InstallExecuteSequence table
>> in
>> > a Windows Installer database.
>> >
>> >
>> >
>> >
>> >
>> > ------------------------------
>> > *From:* wix-users <wix-users-bounces at lists.wixtoolset.org> on behalf of
>> > Ven H via wix-users <wix-users at lists.wixtoolset.org>
>> > *Sent:* Monday, December 18, 2017 10:54 PM
>> > *To:* WiX Toolset Users Mailing List
>> > *Cc:* Ven H
>> > *Subject:* [wix-users] Stop & Start Service
>> >
>> > Using the ServiceControl element, we can start or stop (or both) a
>> service
>> > during MSI installation. But, I need to stop a service (for example
>> IIS) at
>> > the beginning of MSI installation and start it again during the end of
>> MSI
>> > installation. Can anyone please help me achieve this?
>> >
>> >
>> > Regards,
>> > Venkatesh
>> >
>> > ____________________________________________________________________
>> > WiX Toolset Users Mailing List provided by FireGiant
>> > http://www.firegiant.com/
>> > WiX Support | WiX Experts and Resources from FireGiant
>> > <http://www.firegiant.com/>
>> > www.firegiant.com
>> > WiX Support | Installation, Development, Deployment | WiX Experts and
>> > Resources from FireGiant
>> >
>> >
>> >
>>
>> ____________________________________________________________________
>> WiX Toolset Users Mailing List provided by FireGiant
>> http://www.firegiant.com/
>>
>