We are running IIS v3 on NT 4.0 SP6a, Exchange 5.5 SP4. Under
IIS, within our domain, there are four sites listed. They are default FTP, default Web, Administrator Web and our server. Periodically, the sites stop for no known reason. Once the site is stopped, we can't access our e-mail through Outlook Web Access. Any ideas on how to keep these running all the time?
There are two other possibilities. One is to spend a great deal of time debugging your Web applications, to isolate and fix the problems. Unfortunately, IIS 3.0 doesn't have great debugging capabilities, so that's not such an easy task.
The final option is to regularly reboot your server. Any self-respecting admin would cringe at this idea. After all, if your applications are well-built, they should run indefinitely without a reboot. In your case, at least one Web application is not well-built, and is causing your Web server to crash. If finding and fixing the problem, or upgrading IIS aren't options, then frequently rebooting the server can postpone these unexpected failures. How often you need to reboot depends on how often the application fails. If it fails less than once per day, scheduling a nightly reboot may eliminate the symptoms of your problem. Good luck!
This was first published in May 2002