Will the same pain ever stop? It seems like IIS 7 has a habit of inserting in more security restrictions to break your applications when you are not looking. So, after you install SP1 onto your Windows Vista workstation, you may want to immediately run over to browser and test if your local web applications can still function normally. You may encounter the dreaded HTTP 503 Service Unavailable error.
Being ever the comprehensive and useful error message, it naturally guides an administrator to refer to the Event logs. One may see these
Log Name: System
Source: Microsoft-Windows-WAS
Date: 5/4/2008 17:19:16
Event ID: 5009
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: jenova
Description:
A process serving application pool 'Classic .NET AppPool' terminated unexpectedly. The process id was '4968'. The process exit code was '0xfffffffe'.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WAS" Guid="{524B5D04-133C-4A62-8362-64E8EDB9CE40}" EventSourceName="WAS" />
<EventID Qualifiers="32768">5009</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2008-04-05T09:19:16.000Z" />
<EventRecordID>116297</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>jenova</Computer>
<Security />
</System>
<EventData>
<Data Name="AppPoolID">Classic .NET AppPool</Data>
<Data Name="ProcessID">4968</Data>
<Data Name="ExitCode">fffffffe</Data>
</EventData>
</Event>
Log Name: System
Source: Microsoft-Windows-WAS
Date: 5/4/2008 17:19:16
Event ID: 5002
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: jenova
Description:
Application pool 'Classic .NET AppPool' is being automatically disabled due to a series of failures in the process(es) serving that application pool.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WAS" Guid="{524B5D04-133C-4A62-8362-64E8EDB9CE40}" EventSourceName="WAS" />
<EventID Qualifiers="49152">5002</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2008-04-05T09:19:16.000Z" />
<EventRecordID>116298</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>jenova</Computer>
<Security />
</System>
<EventData>
<Data Name="AppPoolID">Classic .NET AppPool</Data>
<Binary>
</Binary>
</EventData>
</Event>
Log Name: Application
Source: Microsoft-Windows-IIS-W3SVC-WP
Date: 5/4/2008 17:19:16
Event ID: 2276
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: jenova
Description:
The worker process failed to initialize correctly and therefore could not be started. The data is the error.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-IIS-W3SVC-WP" Guid="{670080D9-742A-4187-8D16-41143D1290BD}" EventSourceName="W3SVC-WP" />
<EventID Qualifiers="49152">2276</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2008-04-05T09:19:16.000Z" />
<EventRecordID>134487</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>jenova</Computer>
<Security />
</System>
<EventData>
<Binary>05000780</Binary>
</EventData>
</Event>
If only it would say more than "the data is the error". I wish I could give such a terse and effective answer to customers and users when I cannot deliver something on time. For sure, others are having a similar swell time as I am. This party is not going to end soon until we find a more zoomed-in description where this seeming denial of access is happening. I tried the suggested locations to give NETWORK SERVICE read or modify privileges to no avail.
What can we poor sods do when the OS or service decides to keep mum? Always return back to your Operating Lord Almighty and pray again for a newer, more powerful version of Process Monitor. It makes me want to cry how easy it suddenly becomes to track what the heck is happening.
Volia. Grant NETWORK SERVICE read access to C:\windows\System32\inetsrv\config\schema, and boom my ASP.NET web applications kick alive again. And that was all I simply wanted - a path to tell where the denial is. Next time, I am skipping the event logs and just using Process Monitor as my real-time log.