|
Home > Archive > IIS Server Security > February 2005 > IIS DefaultAppPool Identiy - Service Unavailable
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
IIS DefaultAppPool Identiy - Service Unavailable
|
|
| Joe Krings 2005-02-01, 6:11 pm |
| Just brought up W2003 server (IIS6) installed 1st site/.Net app. When the
DefaultAppPool Identity is set to Local System, no problem (IIS 5 Isoloation
also works); however, setting the identity to Network Service or IWAM acct
results in "Service Unavailable" error. I searched all available MS docs;
verified the security policies, verified folder secrity, the IIS_WPG group
members, ASPNET installation/user; all checks out but still without
receiving error. Really stumped and as to what to try/check next. The errors
resemble a MS document URL, and though I read it, this server is NOT a
domain controller.
The System Event log posts the following error:
Application pool 'DefaultAppPool' is being automatically disabled due to a
series of failures in the process(es) serving that application pool.
after 5 occurences of this error:
A process serving application pool 'DefaultAppPool' terminated unexpectedly.
The process id was '5616'. The process exit code was '0xffffffff'.
Thanks very much. Joe
| |
| Bernard 2005-02-02, 7:47 am |
| Wild guess, it could be the app require local system as process idenity.
create a simple hello aspx page, then put it in the pool, can you browse ?
--
Regards,
Bernard Cheah
http://www.tryiis.com/
http://support.microsoft.com/
http://www.msmvps.com/bernard/
"Joe Krings" <krinjp@jea.com> wrote in message
news:OhUOXNLCFHA.3940@TK2MSFTNGP09.phx.gbl...
> Just brought up W2003 server (IIS6) installed 1st site/.Net app. When the
> DefaultAppPool Identity is set to Local System, no problem (IIS 5
> Isoloation
> also works); however, setting the identity to Network Service or IWAM acct
> results in "Service Unavailable" error. I searched all available MS docs;
> verified the security policies, verified folder secrity, the IIS_WPG group
> members, ASPNET installation/user; all checks out but still without
> receiving error. Really stumped and as to what to try/check next. The
> errors resemble a MS document URL, and though I read it, this server is
> NOT a domain controller.
>
> The System Event log posts the following error:
> Application pool 'DefaultAppPool' is being automatically disabled due to a
> series of failures in the process(es) serving that application pool.
>
> after 5 occurences of this error:
> A process serving application pool 'DefaultAppPool' terminated
> unexpectedly. The process id was '5616'. The process exit code was
> '0xffffffff'.
>
> Thanks very much. Joe
>
| |
| Joe Krings 2005-02-02, 7:47 am |
| Unfortunately, this doesn't help much in terms of root cause and
understanding of the "Network Service" security policy. That is, if the
hello aspx page works, how does that explain why the other app won't. In
terms of root cause, what characteristics (i.e. code, interfaces, filters,
etc.) would a program have that would make it fail using the "Network
Service" identity? I don't see any MS literature on the issue.
Thanks. Joe
.......................................
"Bernard" <qbernard@hotmail.com.discuss> wrote in message
news:eR0E04QCFHA.824@TK2MSFTNGP11.phx.gbl...
> Wild guess, it could be the app require local system as process idenity.
> create a simple hello aspx page, then put it in the pool, can you browse ?
>
> --
> Regards,
> Bernard Cheah
> http://www.tryiis.com/
> http://support.microsoft.com/
> http://www.msmvps.com/bernard/
>
>
>
> "Joe Krings" <krinjp@jea.com> wrote in message
> news:OhUOXNLCFHA.3940@TK2MSFTNGP09.phx.gbl...
>
>
| |
| Bernard 2005-02-03, 2:48 am |
| any MS literature ? generally, if you could doesn't need any special
privileges, network service fit the boat, however, there are times that it
may not work. have you try set it to local system ? and does it work ? if
yes, meaning you app need additional access that doesn't grant to network
service account.
This article tells you what's the default access right for built-in
accounts -
http://www.microsoft.com/resources/...sRG_SEC_23.mspx
--
Regards,
Bernard Cheah
http://www.tryiis.com/
http://support.microsoft.com/
http://www.msmvps.com/bernard/
"Joe Krings" <krinjp@jea.com> wrote in message
news:O%23IXG5RCFHA.2568@TK2MSFTNGP11.phx.gbl...
> Unfortunately, this doesn't help much in terms of root cause and
> understanding of the "Network Service" security policy. That is, if the
> hello aspx page works, how does that explain why the other app won't. In
> terms of root cause, what characteristics (i.e. code, interfaces, filters,
> etc.) would a program have that would make it fail using the "Network
> Service" identity? I don't see any MS literature on the issue.
>
> Thanks. Joe
> ......................................
> "Bernard" <qbernard@hotmail.com.discuss> wrote in message
> news:eR0E04QCFHA.824@TK2MSFTNGP11.phx.gbl...
>
>
|
|
|
|
|