David
Tue Oct 11 23:17:21 CDT 2005
Yes, the number of solutions to a "503 Service Unavailable" and your two
event log error codes is unlimited, so there have been plenty of solutions
found and they may or may not have anything to do with your issue.
The only thing you can do is debug it to figure out what is causing it, and
only by doing this can you determine the actual solution to your specific
issue.
In other words, asking for solutions to "503 Service Unavailable" is like
searching for a murder suspect. All murders (503 Service Unavailable) look
the same -- someone died and someone probably did it. Saying that you got
1002 and 1009 system event errors is like saying the suspect is under six
feet tall and has dark complexion -- barely narrows down the field of
suspects. Only by catching the crash (i.e. murder) with a tool like
DebugDiag or IIS State can you catch the suspect red-handed in the act.
http://blogs.msdn.com/david.wang/archive/2005/08/29/HOWTO_Understand_and_Diagnose_an_AppPool_Crash.aspx
If things work when run as LocalSystem, it sounds like you are running
custom code which assumes it is going to succeed at something with
LocalSystem credentials, and when it fails as Network Service, it goes down
an untested error path and crashes. Sounds like a badly written ISAPI Filter
or ISAPI Extension to me.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
<nko@hawaii.com> wrote in message
news:1129065514.840216.225310@z14g2000cwz.googlegroups.com...
HI all!
I read a number of posting about 503 Service Unavailable browser
messages that comes along with 1002 and 1009 system event errors.
I am running IIS6 on 2003 Server. The DefaultAppPool runs under
NETWORK SERVICE.
I was wondering if anyone have found a solution to problem yet. I have
tried the following and see no resolution yet:
1. Filemon - no access denieds found
2. RegMon- no access denieds found
3. Local Policy- compared to new machine and it looks the same
4. IISState- no results.
However, when changing application user to LOCAL SYSTEM everything runs
fine. But, of course we do not want to run pool using a super user.
Any suggestions?