Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm running a server which currently has about 50 sites on, and am encountering from problems with IIS.

Everytime I try and change a setting on a site, switch .Net versions, add/change domains on a site directly in IIS Manager. IIS Manager crashes. When I start up the manager again, all the sites are down.

Does anyone have any advice on how to fix this, without having sites down for a significant period of time?

Thanks in advance,

share|improve this question

The interesting part is the .Net version part, because this doesn't directly lead to a change in IIS settings as I understand it, only web.config settings.

This suggests your IIS management console is utterly borfed, which isn't a common occurrence.

I'd suggest any of:

  • Disable any antivirus that might be present
  • Copy Metabase.XML and check for obvious corruption in a text editor
  • Look at the event log to understand possible reasons for service failure
  • Hire a good exorcist

IIS Manager essentially edits the in-memory metabase, which gets persisted to Metabase.XML on disk. However, the ASP.Net tab doesn't play in the same space, it typically edits the web.config file (I might not be entirely correct there, there might also be a ScriptMaps implication to the use of the tab), in which case something Really Interesting is happening there.

So, take a snapshot of metabase.xml before changing anything, and perhaps grab a copy when the server fails (assuming it's going to fail at least once before you fix it), and compare them.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.