Windows

just uninstall the windows option pack and install it again in the same directory of Inetpub.
this a normal problem when the dll gets corrupted by your static site

And remember to apply the patch for the Code Red Worm!

Thanks ankit! That's what I thought. If I am going to uninstall/reinstall IIS4 what are the consequences? Do I need to reset the Exchange and OWA settings? How about re-installing it (without uninstalling) will it overwrite the corrupt dll's?

You could always change your logging options to try to pick up on what is causing the issue. I think the change to the Outlook users is a red herring. If you run backups and the server's content is relatively static, do a system restore to the last date iot was working.

If not, uninstall and reinstall the option pack. Once you have the system running the way you want it to, I highly recommend backing up the server. You should also download a free tool called metaedit from Microsoft and use it to make a backup of the metabase (IIS' registry essentially...) If you experience trouble in the future, try restoring the metabase first.

You could always change your logging options to try to pick up on what is causing the issue. I think the change to the Outlook users is a red herring. If you run backups and the server's content is relatively static, do a system restore to the last date iot was working.

If not, uninstall and reinstall the option pack. Once you have the system running the way you want it to, I highly recommend backing up the server. You should also download a free tool called metaedit from Microsoft and use it to make a backup of the metabase (IIS' registry essentially...) If you experience trouble in the future, try restoring the metabase first.

This is the behavior of a IIS that is being attacked by CODE RED I or II, apply the patch before taking out IIS. This is not a simple process, especially since you are running OWA on it.