Logging individual site stops and starts on IIS6

I'd like to log when individual sites stop and start on IIS6. I need
something more explicit than looking at the log file and seeing if a new
header is written - I need to know exactly if and when the site is
stopped and then re-started.

The stops and starts could be caused by any of a) manual command via the
IIS Manager, b) by programmatic control, or c) by normal functioning of IIS.

Is there any way to do this? It seems like such a simple requirement and
yet there doesn't seem to be a built in, explicit, mechanism for doing it.


NickF

Re: Logging individual site stops and starts on IIS6

Enable metabase auditing.
http://www.adopenstatic.com/faq/IISMetabaseAuditing.aspx

Cheers
Ken

--
My IIS Blog: www.adOpenStatic.com/cs/blogs/ken


"NickF" wrote in message
news:uyRZQGLBIHA.4732@TK2MSFTNGP04.phx.gbl...
> I'd like to log when individual sites stop and start on IIS6. I need
> something more explicit than looking at the log file and seeing if a new
> header is written - I need to know exactly if and when the site is
> stopped and then re-started.
>
> The stops and starts could be caused by any of a) manual command via the
> IIS Manager, b) by programmatic control, or c) by normal functioning of
> IIS.
>
> Is there any way to do this? It seems like such a simple requirement and
> yet there doesn't seem to be a built in, explicit, mechanism for doing it.
>
>
> NickF

Re: Logging individual site stops and starts on IIS6

Ken, many thanks. That looks very useful.


Ken Schaefer wrote:
> Enable metabase auditing.
> http://www.adopenstatic.com/faq/IISMetabaseAuditing.aspx
>
> Cheers
> Ken
>

Re: Logging individual site stops and starts on IIS6

Oops, I mistakenly replied using my colleague's account just now.
Apologies to all for that.

Thank you, Ken, for the information on metabase auditing. It looks like
it should be very useful for what I need to do.


Ken Schaefer wrote:
> Enable metabase auditing.
> http://www.adopenstatic.com/faq/IISMetabaseAuditing.aspx
>
> Cheers
> Ken
>

Re: Logging individual site stops and starts on IIS6

Excellent, I have enabled auditing for a site I am particularly
interested in and can now see event log entries for changes to the
ServerCommand and ServerAutoStart metabase properties when I manually
stop and start the site as an experiment. However, changes to the
ServerState property do not seem to be logged, even though the value of
this property changes as well. Is it possible to log the value of the
ServerState property too?


Ken Schaefer wrote:
> Enable metabase auditing.
> http://www.adopenstatic.com/faq/IISMetabaseAuditing.aspx
>
> Cheers
> Ken
>

Re: Logging individual site stops and starts on IIS6

ServerState is a transient property, thus its value is literally not
worth auditing.

You can go ahead and set the ServerState property yourself, but you
will see that it has no effect on IIS server behavior at all. Don't
mind the fact that the UI uses the transient property to display state
-- it has no bearing on the actual behavior of the server.

There are several other propertys in IIS metabase that belong in the
same transient property category that is more more show by the UI and
not used by the server at all.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//





On Oct 1, 11:10 pm, NickF wrote:
> Excellent, I have enabled auditing for a site I am particularly
> interested in and can now see event log entries for changes to the
> ServerCommand and ServerAutoStart metabase properties when I manually
> stop and start the site as an experiment. However, changes to the
> ServerState property do not seem to be logged, even though the value of
> this property changes as well. Is it possible to log the value of the
> ServerState property too?
>
>
>
> Ken Schaefer wrote:
> > Enable metabase auditing.
> >http://www.adopenstatic.com/faq/IISMetabaseAuditing.aspx
>
> > Cheers
> > Ken- Hide quoted text -
>
> - Show quoted text -

Re: Logging individual site stops and starts on IIS6

Thanks, David.

David Wang wrote:
> ServerState is a transient property, thus its value is literally not
> worth auditing.
>
> You can go ahead and set the ServerState property yourself, but you
> will see that it has no effect on IIS server behavior at all. Don't
> mind the fact that the UI uses the transient property to display state
> -- it has no bearing on the actual behavior of the server.
>
> There are several other propertys in IIS metabase that belong in the
> same transient property category that is more more show by the UI and
> not used by the server at all.
>
>
> //David
> http://w3-4u.blogspot.com
> http://blogs.msdn.com/David.Wang
> //