IIS 7.0 Service Not Available on Vista

There are two messages each time this occurs.

The last message is

Application pool 'DefaultAppPool' is being automatically disabled due to a
series of failures in the process(es) serving that application pool.

The event id for this message is 5002.

This message is preceded by a series of 5 messages which read;

A listener channel for protocol 'http' in worker process '3456' serving
application pool 'DefaultAppPool' reported a listener channel failure. The
data field contains the error number.

The event id for these messages is 5139.

When I look at the online help for these messages the relevant advice is to
stop/start the application pool, stop/start the WAS, and start W3SVC.

After doing each of these steps a retest yields the same result.

John

--
John H Clark
www.weownit.coop


"Ken Schaefer" wrote:

> Hi
>
> 503 = Service Unavailable.
>
> It would appear that your web application pool is unable to start (or has
> crashed). Can you look in the Windows Event Logs to see if any applicable
> errors have been logged there?
>
> Cheers
> Ken
>
> "John H Clark" <Coyote.DeleteThis@newsgroup.nospam> wrote in message
> news:5A1CD1A9-67C6-4724-9ECA-98F2B05B97F7@microsoft.com...
> >I have a new install of both Vista and IIS 7.0. When I access the IIS
> > Manager and click Browse in the Actions panel I get a 503 response. When
> > I
> > try accessing http://localhost or http://localhost/iisstart.htm I get the
> > same 503 response.
> >
> > In both cases the DefaultAppPool is automatically disabled.
> >
> > There are no applications other than the Reports and ReportServer which
> > are
> > installed with IIS 7.0.
> >
> > What is necessary to getting IIS 7.0 service to work?
> > --
> > John H Clark
> >
>
>
 >> Stay informed about: IIS 7.0 Service Not Available on Vista 

Hi John,

This events indicate the application pool's worker process crashed
unexpectedly for several times in an allowed time period. So IIS
automatically disabled this unhealthy pool to stop serve new requests.
Therefore you get the 503 error.

Generally this kind of crashing issues are caused by defected
code/application running in the application pool's worker process instance.
A thorough troubleshooting requires capturing memory dump files for the
crash and debugging which is not able to be performed in the newsgroup. I'd
like to suggest you use one of your MSDN Technical Support Incidents to
work with us via telephone based support this issue. This will be the most
effective way to assist you on complicated and project based issue. Also
you won't even need to spend the incident account if the problem is finally
confirmed to be a product issue or can be simply fixed by applying hotfix.
Please refer to the support note below.

About the information of free incident support for MSDN subscribers, please
look at:
http://msdn.microsoft.com/subscriptions/support/default.aspx.

To obtain the phone numbers for Microsoft Customer Service and Support
services technology request, please take a look at the web site listed
below.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS

Thanks.

Sincerely,

WenJun Zhang

Microsoft Online Community Support

==================================================

Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at:

http://msdn.microsoft.com/subscriptions/support/default.aspx.

==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.
 >> Stay informed about: IIS 7.0 Service Not Available on Vista 

Is there any resolution of this issue? I am experiencing exactly the same
problem.

""WenJun Zhang[msft]"" wrote:

> Hi John,
>
> This events indicate the application pool's worker process crashed
> unexpectedly for several times in an allowed time period. So IIS
> automatically disabled this unhealthy pool to stop serve new requests.
> Therefore you get the 503 error.
>
> Generally this kind of crashing issues are caused by defected
> code/application running in the application pool's worker process instance.
> A thorough troubleshooting requires capturing memory dump files for the
> crash and debugging which is not able to be performed in the newsgroup. I'd
> like to suggest you use one of your MSDN Technical Support Incidents to
> work with us via telephone based support this issue. This will be the most
> effective way to assist you on complicated and project based issue. Also
> you won't even need to spend the incident account if the problem is finally
> confirmed to be a product issue or can be simply fixed by applying hotfix.
> Please refer to the support note below.
>
> About the information of free incident support for MSDN subscribers, please
> look at:
> http://msdn.microsoft.com/subscriptions/support/default.aspx.
>
> To obtain the phone numbers for Microsoft Customer Service and Support
> services technology request, please take a look at the web site listed
> below.
> http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
>
> Thanks.
>
> Sincerely,
>
> WenJun Zhang
>
> Microsoft Online Community Support
>
> ==================================================
>
> Get notification to my posts through email? Please refer to:
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications.
>
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at:
>
> http://msdn.microsoft.com/subscriptions/support/default.aspx.
>
> ==================================================
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>
>
 >> Stay informed about: IIS 7.0 Service Not Available on Vista 

There are infinite causes for 503 Service Unavailable.

They mostly occur due to user misconfiguration or incompatible
software.

You will have to troubleshoot your server to determine the underlying
cause because this is rarely an issue with IIS or Windows. You will
have to resolve your own issue because your arbitrary issue is
unlikely to be the same as someone else's arbitrary issue.

http://blogs.msdn.com/david.wang/archive/2005/08/29/HOWTO_Understand_a...Diagnos


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




On Mar 6, 4:55 pm, lschult2 <lschu... DeleteThis @discussions.microsoft.com>
wrote:
> Is there any resolution of this issue?  I am experiencing exactly the same
> problem.
>
>
>
> ""WenJun Zhang[msft]"" wrote:
> > Hi John,
>
> > This events indicate the application pool's worker process crashed
> > unexpectedly for several times in an allowed time period. So IIS
> > automatically disabled this unhealthy pool to stop serve new requests.
> > Therefore you get the 503 error.
>
> > Generally this kind of crashing issues are caused by defected
> > code/application running in the application pool's worker process instance.
> > A thorough troubleshooting requires capturing memory dump files for the
> > crash and debugging which is not able to be performed in the newsgroup. I'd
> > like to suggest you use one of your MSDN Technical Support Incidents to
> > work with us via telephone based support this issue. This will be the most
> > effective way to assist you on complicated and project based issue. Also
> > you won't even need to spend the incident account if the problem is finally
> > confirmed to be a product issue or can be simply fixed by applying hotfix.
> > Please refer to the support note below.
>
> > About the information of free incident support for MSDN subscribers, please
> > look at:
> >http://msdn.microsoft.com/subscriptions/support/default.aspx.
>
> > To obtain the phone numbers for Microsoft Customer Service and Support
> > services technology request, please take a look at the web site listed
> > below.
> >http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
>
> > Thanks.
>
> > Sincerely,
>
> > WenJun Zhang
>
> > Microsoft Online Community Support
>
> > ==================================================
>
> > Get notification to my posts through email? Please refer to:
> >http://msdn.microsoft.com/subscriptions/managednewsgroups/default.asp...
> > ications.
>
> > Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> > where an initial response from the community or a Microsoft Support
> > Engineer within 1 business day is acceptable. Please note that each follow
> > up response may take approximately 2 business days as the support
> > professional working with you may need further investigation to reach the
> > most efficient resolution. The offering is not appropriate for situations
> > that require urgent, real-time or phone-based interactions or complex
> > project analysis and dump analysis issues. Issues of this nature are best
> > handled working with a dedicated Microsoft Support Engineer by contacting
> > Microsoft Customer Support Services (CSS) at:
>
> >http://msdn.microsoft.com/subscriptions/support/default.aspx.
>
> > ==================================================
>
> > This posting is provided "AS IS" with no warranties, and confers no rights.- Hide quoted text -
>
> - Show quoted text -
 >> Stay informed about: IIS 7.0 Service Not Available on Vista 

My arbitrary issue sure appears to be the sam as John Clark's.

I found the solution through debugging and searching the web more. In case
other people are having this problem too, I will post what I found.

Some background: this is a brand new laptop that came installed with Vista
Basic. I did the Anytime Upgrade to Vista Business, and was not able to get
IIS to load even the default iisstart.htm. I kept getting 503 errors. This
is out of the box after the Anytime Upgrade.

The post that helped me was:
http://mvolo.com/blogs/serverside/archive/2006/10/19/Where-did-my-IIS7...rver-go
See Mike Volodarsky's comments from December 4, 2007.

The issue was for some reason the applicationHost.config file had the wrong
permissions, and the IIS worker process was failing to read or write to it.
I added IIS_IUSRS group to have full access to this file, and it resolved the
issue.

Again, the system came this way, so it appears that the Anytime Upgrade left
this file with the incorrect permissions.

"David Wang" wrote:

> There are infinite causes for 503 Service Unavailable.
>
> They mostly occur due to user misconfiguration or incompatible
> software.
>
> You will have to troubleshoot your server to determine the underlying
> cause because this is rarely an issue with IIS or Windows. You will
> have to resolve your own issue because your arbitrary issue is
> unlikely to be the same as someone else's arbitrary issue.
>
> http://blogs.msdn.com/david.wang/archive/2005/08/29/HOWTO_Understand_a...Diagnos
>
>
> //David
> http://w3-4u.blogspot.com
> http://blogs.msdn.com/David.Wang
> //
>
>
>
>
> On Mar 6, 4:55 pm, lschult2 <lschu... DeleteThis @discussions.microsoft.com>
> wrote:
> > Is there any resolution of this issue? I am experiencing exactly the same
> > problem.
> >
> >
> >
> > ""WenJun Zhang[msft]"" wrote:
> > > Hi John,
> >
> > > This events indicate the application pool's worker process crashed
> > > unexpectedly for several times in an allowed time period. So IIS
> > > automatically disabled this unhealthy pool to stop serve new requests.
> > > Therefore you get the 503 error.
> >
> > > Generally this kind of crashing issues are caused by defected
> > > code/application running in the application pool's worker process instance.
> > > A thorough troubleshooting requires capturing memory dump files for the
> > > crash and debugging which is not able to be performed in the newsgroup. I'd
> > > like to suggest you use one of your MSDN Technical Support Incidents to
> > > work with us via telephone based support this issue. This will be the most
> > > effective way to assist you on complicated and project based issue. Also
> > > you won't even need to spend the incident account if the problem is finally
> > > confirmed to be a product issue or can be simply fixed by applying hotfix.
> > > Please refer to the support note below.
> >
> > > About the information of free incident support for MSDN subscribers, please
> > > look at:
> > >http://msdn.microsoft.com/subscriptions/support/default.aspx.
> >
> > > To obtain the phone numbers for Microsoft Customer Service and Support
> > > services technology request, please take a look at the web site listed
> > > below.
> > >http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
> >
> > > Thanks.
> >
> > > Sincerely,
> >
> > > WenJun Zhang
> >
> > > Microsoft Online Community Support
> >
> > > ==================================================
> >
> > > Get notification to my posts through email? Please refer to:
> > >http://msdn.microsoft.com/subscriptions/managednewsgroups/default.asp...
> > > ications.
> >
> > > Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> > > where an initial response from the community or a Microsoft Support
> > > Engineer within 1 business day is acceptable. Please note that each follow
> > > up response may take approximately 2 business days as the support
> > > professional working with you may need further investigation to reach the
> > > most efficient resolution. The offering is not appropriate for situations
> > > that require urgent, real-time or phone-based interactions or complex
> > > project analysis and dump analysis issues. Issues of this nature are best
> > > handled working with a dedicated Microsoft Support Engineer by contacting
> > > Microsoft Customer Support Services (CSS) at:
> >
> > >http://msdn.microsoft.com/subscriptions/support/default.aspx.
> >
> > > ==================================================
> >
> > > This posting is provided "AS IS" with no warranties, and confers no rights.- Hide quoted text -
> >
> > - Show quoted text -
>
>
 >> Stay informed about: IIS 7.0 Service Not Available on Vista 

I agree with you that the symptoms *look* similar -- new install that
results in 503.

However, that is far from sufficient to say "sure appears to be the
same". There are lots of people who have clean installs that do not
have 503s. There are upgraders who do not encounter your issue. Most
importantly, John said his issue is with a new install, not upgrade,
so the evidence does not suggest your arbitrary issue is related to
John Clark's. When troubleshooting, you have to think like a criminal
prosecutor -- you need solid evidence, not just similar looking
circumstance.

I am glad that you are happy with finding the solution to your issue
and simply want to publicize it in hopes of helping someone else, but
I must caution that providing information and help with consistent
troubleshooting advice is the only true way to help someone, even if
they don't think so. Simply publishing solutions that "work for me"
and encouraging "pattern matching" of failures against solutions,
although easy to perform, is neutral at best. On something as complex
as computer software, pattern matching is a really bad and harmful way
to problem solve.

Case in point: I believe that you are truly trying to help people with
the solution that you have found -- this is why I am jumping in and
trying to explain to you what is actually going on, why your attempts
to help others are actually detrimental to others, and what the right
solution should be. I believe you are not intentionally trying to harm
others.

Your "solution" to add IIS_IUSRS group to have Full access to the file
is *dangerous*. IIS worker process only needs read access to a
privileged configuration file like applicationHost.config. Write/
FullControl access is actually a serious security vulnerability
because it allows elevation of privilege attacks that allows easy
remote hijack of your computer. I am sure that you did not know nor
intend for this side effect.

Now, Mike only said that IIS_IUSRS group should have "access" -- in
his defense, he did not say "full access", and in your defense, he did
not say "read access". I'm not going to mince words because I believe
we all mean well.

Hope this helps clear things up.


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




On Mar 7, 7:02 am, lschult2 <lschu....TakeThisOut@discussions.microsoft.com>
wrote:
> My arbitrary issue sure appears to be the sam as John Clark's.
>
> I found the solution through debugging and searching the web more.  In case
> other people are having this problem too, I will post what I found.
>
> Some background: this is a brand new laptop that came installed with Vista
> Basic.  I did the Anytime Upgrade to Vista Business, and was not able to get
> IIS to load even the default iisstart.htm.  I kept getting 503 errors.  This
> is out of the box after the Anytime Upgrade.
>
> The post that helped me was:http://mvolo.com/blogs/serverside/archive/2006/10/19/Where-did-my-IIS...
> See Mike Volodarsky's comments from December 4, 2007.
>
> The issue was for some reason the applicationHost.config file had the wrong
> permissions, and the IIS worker process was failing to read or write to it..  
> I added IIS_IUSRS group to have full access to this file, and it resolved the
> issue.
>
> Again, the system came this way, so it appears that the Anytime Upgrade left
> this file with the incorrect permissions.
>
>
>
> "David Wang" wrote:
> > There are infinite causes for 503 Service Unavailable.
>
> > They mostly occur due to user misconfiguration or incompatible
> > software.
>
> > You will have to troubleshoot your server to determine the underlying
> > cause because this is rarely an issue with IIS or Windows. You will
> > have to resolve your own issue because your arbitrary issue is
> > unlikely to be the same as someone else's arbitrary issue.
>
> >http://blogs.msdn.com/david.wang/archive/2005/08/29/HOWTO_Understand_...
>
> > //David
> >http://w3-4u.blogspot.com
> >http://blogs.msdn.com/David.Wang
> > //
>
> > On Mar 6, 4:55 pm, lschult2 <lschu....TakeThisOut@discussions.microsoft.com>
> > wrote:
> > > Is there any resolution of this issue?  I am experiencing exactly the same
> > > problem.
>
> > > ""WenJun Zhang[msft]"" wrote:
> > > > Hi John,
>
> > > > This events indicate the application pool's worker process crashed
> > > > unexpectedly for several times in an allowed time period. So IIS
> > > > automatically disabled this unhealthy pool to stop serve new requests.
> > > > Therefore you get the 503 error.
>
> > > > Generally this kind of crashing issues are caused by defected
> > > > code/application running in the application pool's worker process instance.
> > > > A thorough troubleshooting requires capturing memory dump files for the
> > > > crash and debugging which is not able to be performed in the newsgroup. I'd
> > > > like to suggest you use one of your MSDN Technical Support Incidents to
> > > > work with us via telephone based support this issue. This will be the most
> > > > effective way to assist you on complicated and project based issue. Also
> > > > you won't even need to spend the incident account if the problem is finally
> > > > confirmed to be a product issue or can be simply fixed by applying hotfix.
> > > > Please refer to the support note below.
>
> > > > About the information of free incident support for MSDN subscribers, please
> > > > look at:
> > > >http://msdn.microsoft.com/subscriptions/support/default.aspx.
>
> > > > To obtain the phone numbers for Microsoft Customer Service and Support
> > > > services technology request, please take a look at the web site listed
> > > > below.
> > > >http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
>
> > > > Thanks.
>
> > > > Sincerely,
>
> > > > WenJun Zhang
>
> > > > Microsoft Online Community Support
>
> > > > ==================================================
>
> > > > Get notification to my posts through email? Please refer to:
> > > >http://msdn.microsoft.com/subscriptions/managednewsgroups/default.asp....
> > > > ications.
>
> > > > Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> > > > where an initial response from the community or a Microsoft Support
> > > > Engineer within 1 business day is acceptable. Please note that each follow
> > > > up response may take approximately 2 business days as the support
> > > > professional working with you may need further investigation to reach the
> > > > most efficient resolution. The offering is not appropriate for situations
> > > > that require urgent, real-time or phone-based interactions or complex
> > > > project analysis and dump analysis issues. Issues of this nature are best
> > > > handled working with a dedicated Microsoft Support Engineer by contacting
> > > > Microsoft Customer Support Services (CSS) at:
>
> > > >http://msdn.microsoft.com/subscriptions/support/default.aspx.
>
> > > > ==================================================
>
> > > > This posting is provided "AS IS" with no warranties, and confers no rights.- Hide quoted text -
>
> > > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -
 >> Stay informed about: IIS 7.0 Service Not Available on Vista