2k3, x64, IIS6, Service Unavailable

I cannot get past this serious headache. I am attempting to setup IIS 6.0 on
a client's domain controller (their call, not mine) so we can run SQL
Reporting 2005. I haven't even made it to installing SQL, and am getting the
ever-unhelpful "Service Unavailable" error when browsing to localhost. I
have scoured the web for answers, and none of them have solved my problem. I
have:

-Used Filemon and Regmon (no access violations)
-Set access rights to Network Service and IIS_WPG
-Attempted to use new user/app pool

The client is running Win2003 x64 as a domain controller. The event
viewer gives me:

A process serving application pool 'DefaultAppPool' terminated unexpectedly.
The process id was '3160'. The process exit code was '0xffffffff'.

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

with no further information. The httperr log file gives me a bunch of
entries as such:

2007-08-14 13:59:22 127.0.0.1 3529 127.0.0.1 80 HTTP/1.1 GET / 503 1
AppOffline DefaultAppPool

I have also gone through the steps on MS's website to run IIS 6.0 in 32-bit
mode.

Can anyone help? I will provide more info as needed.

Thanks!

Re: 2k3, x64, IIS6, Service Unavailable

On Aug 14, 7:48 am, BowlerMonk
wrote:
> I cannot get past this serious headache. I am attempting to setup IIS 6.0 on
> a client's domain controller (their call, not mine) so we can run SQL
> Reporting 2005. I haven't even made it to installing SQL, and am getting the
> ever-unhelpful "Service Unavailable" error when browsing to localhost. I
> have scoured the web for answers, and none of them have solved my problem. I
> have:
>
> -Used Filemon and Regmon (no access violations)
> -Set access rights to Network Service and IIS_WPG
> -Attempted to use new user/app pool
>
> The client is running Win2003 x64 as a domain controller. The event
> viewer gives me:
>
> A process serving application pool 'DefaultAppPool' terminated unexpectedly.
> The process id was '3160'. The process exit code was '0xffffffff'.
>
> Application pool 'DefaultAppPool' is being automatically disabled due to a
> series of failures in the process(es) serving that application pool.
>
> with no further information. The httperr log file gives me a bunch of
> entries as such:
>
> 2007-08-14 13:59:22 127.0.0.1 3529 127.0.0.1 80 HTTP/1.1 GET / 503 1
> AppOffline DefaultAppPool
>
> I have also gone through the steps on MS's website to run IIS 6.0 in 32-bit
> mode.
>
> Can anyone help? I will provide more info as needed.
>
> Thanks!



The Event Log indicates that you are getting 503 because IIS is
repeatedly failing to startup the worker process. This is either due
to misconfiguration of the Application Pool or code that you
configured to run in the process.

To distinguish between them, try:
1. make a request to a plain GIF or HTML page instead of your app.
This will cause IIS to startup the worker process but not load your
application.
2. If you have configured ISAPI Filters/Extensions to run on the
request, please remove them and try again

After determining where the problem is coming from, then we can look
at usefulness of using FileMon/RegMon, changing ACLs, or using new
users for AppPool Identity.

Also, depending on order of installing IIS6 and DCPROMO, it may/not
work by default. That's due to ACL changes by DCPROMO.


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

Re: 2k3, x64, IIS6, Service Unavailable

"David Wang" wrote:

> On Aug 14, 7:48 am, BowlerMonk
> wrote:
> > I cannot get past this serious headache. I am attempting to setup IIS 6.0 on
> > a client's domain controller (their call, not mine) so we can run SQL
> > Reporting 2005. I haven't even made it to installing SQL, and am getting the
> > ever-unhelpful "Service Unavailable" error when browsing to localhost. I
> > have scoured the web for answers, and none of them have solved my problem. I
> > have:
> >
> > -Used Filemon and Regmon (no access violations)
> > -Set access rights to Network Service and IIS_WPG
> > -Attempted to use new user/app pool
> >
> > The client is running Win2003 x64 as a domain controller. The event
> > viewer gives me:
> >
> > A process serving application pool 'DefaultAppPool' terminated unexpectedly.
> > The process id was '3160'. The process exit code was '0xffffffff'.
> >
> > Application pool 'DefaultAppPool' is being automatically disabled due to a
> > series of failures in the process(es) serving that application pool.
> >
> > with no further information. The httperr log file gives me a bunch of
> > entries as such:
> >
> > 2007-08-14 13:59:22 127.0.0.1 3529 127.0.0.1 80 HTTP/1.1 GET / 503 1
> > AppOffline DefaultAppPool
> >
> > I have also gone through the steps on MS's website to run IIS 6.0 in 32-bit
> > mode.
> >
> > Can anyone help? I will provide more info as needed.
> >
> > Thanks!
>
>
>
> The Event Log indicates that you are getting 503 because IIS is
> repeatedly failing to startup the worker process. This is either due
> to misconfiguration of the Application Pool or code that you
> configured to run in the process.
>
> To distinguish between them, try:
> 1. make a request to a plain GIF or HTML page instead of your app.
> This will cause IIS to startup the worker process but not load your
> application.
> 2. If you have configured ISAPI Filters/Extensions to run on the
> request, please remove them and try again
>
> After determining where the problem is coming from, then we can look
> at usefulness of using FileMon/RegMon, changing ACLs, or using new
> users for AppPool Identity.
>
> Also, depending on order of installing IIS6 and DCPROMO, it may/not
> work by default. That's due to ACL changes by DCPROMO.
>
>
> //David
> http://w3-4u.blogspot.com
> http://blogs.msdn.com/David.Wang
> //
>
>

Okay, I removed the ISAPI filter reference in the web site, and had it try
and load a standard GIF file, and received the same message. For what it is
worth, even just trying to load the default HTML page for IIS6 will not load.
This happens when trying to use our App pool as well as the DefaultAppPool,
having no special configuration aside from what is setup by default.

Re: 2k3, x64, IIS6, Service Unavailable

On Aug 15, 5:08 am, BowlerMonk
wrote:
> "David Wang" wrote:
> > On Aug 14, 7:48 am, BowlerMonk
> > wrote:
> > > I cannot get past this serious headache. I am attempting to setup IIS 6.0 on
> > > a client's domain controller (their call, not mine) so we can run SQL
> > > Reporting 2005. I haven't even made it to installing SQL, and am getting the
> > > ever-unhelpful "Service Unavailable" error when browsing to localhost. I
> > > have scoured the web for answers, and none of them have solved my problem. I
> > > have:
>
> > > -Used Filemon and Regmon (no access violations)
> > > -Set access rights to Network Service and IIS_WPG
> > > -Attempted to use new user/app pool
>
> > > The client is running Win2003 x64 as a domain controller. The event
> > > viewer gives me:
>
> > > A process serving application pool 'DefaultAppPool' terminated unexpectedly.
> > > The process id was '3160'. The process exit code was '0xffffffff'.
>
> > > Application pool 'DefaultAppPool' is being automatically disabled due to a
> > > series of failures in the process(es) serving that application pool.
>
> > > with no further information. The httperr log file gives me a bunch of
> > > entries as such:
>
> > > 2007-08-14 13:59:22 127.0.0.1 3529 127.0.0.1 80 HTTP/1.1 GET / 503 1
> > > AppOffline DefaultAppPool
>
> > > I have also gone through the steps on MS's website to run IIS 6.0 in 32-bit
> > > mode.
>
> > > Can anyone help? I will provide more info as needed.
>
> > > Thanks!
>
> > The Event Log indicates that you are getting 503 because IIS is
> > repeatedly failing to startup the worker process. This is either due
> > to misconfiguration of the Application Pool or code that you
> > configured to run in the process.
>
> > To distinguish between them, try:
> > 1. make a request to a plain GIF or HTML page instead of your app.
> > This will cause IIS to startup the worker process but not load your
> > application.
> > 2. If you have configured ISAPI Filters/Extensions to run on the
> > request, please remove them and try again
>
> > After determining where the problem is coming from, then we can look
> > at usefulness of using FileMon/RegMon, changing ACLs, or using new
> > users for AppPool Identity.
>
> > Also, depending on order of installing IIS6 and DCPROMO, it may/not
> > work by default. That's due to ACL changes by DCPROMO.
>
> > //David
> >http://w3-4u.blogspot.com
> >http://blogs.msdn.com/David.Wang
> > //
>
> Okay, I removed the ISAPI filter reference in the web site, and had it try
> and load a standard GIF file, and received the same message. For what it is
> worth, even just trying to load the default HTML page for IIS6 will not load.
> This happens when trying to use our App pool as well as the DefaultAppPool,
> having no special configuration aside from what is setup by default.- Hide quoted text -
>
> - Show quoted text -



Well, if you insist that there is "no special configuration aside from
what is setup by default" then you are saying that default IIS6 does
not work on 64bit Windows, which we all know is not true. Thus, your
problem is that the server has special configuration causing the
issue. If you don't admit this, then there is no point for me to help
troubleshoot further.

You may not know the special configuration that is causing your issue
and I am willing to help, but if you say that there is no special
configuration causing the issue, then there is nothing for me to do.

I would not switch to 32bit because you have no evidence that Bitness
is the issue. In fact, switch bitness can cause more problems than
solutions, especially if you don't understand the gazillion ways it
can break your server vs the reasons it'd help.

If you try random things without diagnosing the issue, you just risk
making things work. It's the same as if you had a sore throat and
randomly decided that chemotherapy should solve it. You go through
chemotherapy and start losing your hair but still hasn't solved the
sore throat.

Worker process failing with exit code -1 usually indicate a really bad
crash in software running in the Application Pool, or bad Application
Pool Identity that is not in IIS_WPG group.


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