Installed the latest windows updates and after the reboot, IIS basically is caput. Specifically, all AppPool are crashing (and getting into disabled mode). the only Apppools not crashing are MSExchangeServicesAppPool and MSExchangeUMAppPool. Even the DefaultAppPool is crashing just hitting the iistart.htm file. I am not sure but I think these pools are run in w3wp.exe. that process is not even in the task manager. I think it's going down as soon as it starts although I don't have a crash event log for that process specifically. turned on iis logging, but nothing gets generated either. Exchange itself works - sending receving messages, however OWA and ActiveSync are non-functioning.Running Windows 2003 x64 Std (as a domain controller) with 8GB memory and Exchange 2007 with latest updates (Version 8.1 (Build 240.6)) I believe.Ps: this might really be a windows/IIS issue with the latest update. If so, I'd apprecaite the mods moving the question to the appropriate forum.

Not a good situtaion you are in on a week end. Any ways so as you said , are you getting any event IDs, any thin gon the IIS logs?Just try this . Create a new application pool (say test) and then map it to a existing app pool which is not working http://www.developer.com/article.php/2245511.Also have you tried unintsllain the updates that started all this?Raj

Here are some of the event logs i am getting: Event Type: Warning Event Source: W3SVC Event Category: None Event ID: 1009 Date: 12/12/2009 Time: 4:26:11 AM User: N/A Computer: SRV3 Description: A process serving application pool 'MSExchangeOWAAppPool' terminated unexpectedly. The process id was '5676'. The process exit code was '0xffffffff'. For mor

Here are some of the event logs i am getting: Event Type: Warning Event Source: W3SVC Event Category: None Event ID: 1009 Date: 12/12/2009 Time: 4:26:11 AM User: N/A Computer: SRV3 Description: A process serving application pool 'MSExchangeOWAAppPool' terminated unexpectedly. The process id was '5676'. The process exit code was '0xffffffff'. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. And then eventually: Event Type: Error Event Source: W3SVC Event Category: None Event ID: 1002 Date: 12/12/2009 Time: 4:26:12 AM User: N/A Computer: SRV3 Description: Application pool 'MSExchangeOWAAppPool' is being automatically disabled due to a series of failures in the process(es) serving that application pool. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. This pattern repeats for all the above mentioned app pools, not just the MSExchangeOWAAppPool.

I tried making a new site (running on port 81) and mapped it to a new AppPool with the identity of the administrator. I created a simple html file with just a word in the body. Results were the same - service unavailable: Event Type: Warning Event Source: W3SVC Event Category: None Event ID: 1009 Date: 12/12/2009 Time: 9:05:23 AM User: N/A Computer: SRV3 Description: A process serving application pool 'AppPool #1' terminated unexpectedly. The process id was '6152'. The process exit code was '0xffffffff'. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. I guess my next path is to try to uninstall the updates. The last MS update was about 7 updates if I am not mistaken.

The updates were: Event Type: Information Event Source: NtServicePack Event Category: None Event ID: 4377 Date: 12/11/2009 Time: 1:53:25 PM User: OURDOMAIN\administrator Computer: SRV3 Description: Windows Server 2003 Hotfix KB973904 was installed. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type: Information Event Source: NtServicePack Event Category: None Event ID: 4377 Date: 12/11/2009 Time: 1:54:12 PM User: OURDOMAIN\administrator Computer: SRV3 Description: Windows Server 2003 Hotfix KB973917 was installed. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type: Information Event Source: NtServicePack Event Category: None Event ID: 4377 Date: 12/11/2009 Time: 1:57:00 PM User: OURDOMAIN\administrator Computer: SRV3 Description: Windows Server 2003 Hotfix KB976325-IE8 was installed. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type: Information Event Source: NtServicePack Event Category: None Event ID: 4377 Date: 12/11/2009 Time: 2:00:00 PM User: OURDOMAIN\administrator Computer: SRV3 Description: Windows Server 2003 Hotfix KB974318 was installed. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type: Information Event Source: NtServicePack Event Category: None Event ID: 4377 Date: 12/11/2009 Time: 2:00:36 PM User: OURDOMAIN\administrator Computer: SRV3 Description: Windows Server 2003 Hotfix KB971737 was installed. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Event Type: Information Event Source: NtServicePack Event Category: None Event ID: 4377 Date: 12/11/2009 Time: 2:01:18 PM User: OURDOMAIN\administrator Computer: SRV3 Description: Windows Server 2003 Hotfix KB974392 was installed. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Will uninstall them and let you know were we end up.

I uninstalled the Windows updates listed and now the IIS works again. Either a bad install, or a huge bug. Now I am scared to apply the security updates - IIS up and running vs. security hole? MS is not leaving us in a good situation...

I would call PSS...Active Directory, 4th Edition - www.briandesmond.com/ad4/

I started applying the updates one at a time. KB973917 is the one that breaks IIS. Once I found that out, I searched for that KB and low and behold, others are reporting the exact same thing.http://support.microsoft.com/?kbid=2009746http://blogs.msdn.com/jaskis/archive/2009/12/09/after-installing-kb-973917-the-iis-6-0-application-pools-cannot-start-up.aspxI am going to re-install the Win2k3 SP2 per first MS article and see what happens.

Yes, please do the suggestions according to the KB article. If the issue persists, I suggest you write the post on our Windows Server forum, as this is not Exchange issue right now...http://social.technet.microsoft.com/Forums/en/category/windowsserver/Thanks,Elvis