I Googled a little and found that the AppPool might need cycling. When I checked the AppPool associated with the specific web application I saw that it was disabled. That was odd. I started it and it quit shortly after I resumed the AppPool. Next, I began checking the event logs. There were two obvious error sets I needed to deal with. First, I had about five 1009 errors. Then, I had one 1002 error. The 1009 errors were notifying me that the process running the AppPool in question failed with an error 0x80. The 1002 error indicates that the AppPool was being disabled. Here are the actual errors (with a little editting to prevent any good info from being given away).
Error 1009 text
Event Type: Warning
Event Source: W3SVC
Event Category: None
Event ID: 1009
Date: 12/31/2010
Time: 9:13:10 AM
User: N/A
Computer: MYCOMP
Description:
A process serving application pool 'AppPool' terminated unexpectedly. The process id was '4668'. The process exit code was '0x80'.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.Error 1002 textEvent Type: Error
Event Source: W3SVC
Event Category: None
Event ID: 1002
Date: 12/31/2010
Time: 9:13:10 AM
User: N/A
Computer: MYCOMP
Description:
Application pool 'AppPool' 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.If found a post on the IIS blogs which pointed out several things their support teams use to get sites going again:http://blogs.iis.net/brian-murphy-booth/archive/2007/03/22/how-to-troubleshoot-an-iis-event-id-1009-error.aspx