For weeks my Exchange 2003 cluster was down. The mail cluster was configured in a active passive configuration and a single server has been up for months. Second virtual machine node was shutdown to save resources.
At some point I was not able to reach my Exchange 2003 mailbox and I started to review the Event Viewer and Services on the active server node. System logs contained around one hundred 4275 event id errors in the IIS Config catalog category.
I filtered Event Viewer for Event ID 4275 to see when these errors started. The first event started on 12 December 2007.
I manually tried to start IIS Admin service and I also reboot the server. Without any success because the IIS services were not going to start. The server’s IIS Metadatabase was not changed in any manual way.
How to restore a Metabase.xml from IIS server?
I went to C:\WINDOWS\system32\inetsrv folder, located and renamed Metabase.xml file to Metabase.xml1. This XML file is being used by IIS to store its configuration database.
Within C:\WINDOWS\system32\inetsrv\History folder all previous XML Metadatabase history files are being stored.
- I copied one of the Metabase files from History folder just before the errors started and pasted the file to C:\WINDOWS\system32\inetsrv folder.
- I renamed the file to MetaDatabase.old.
- I opened Services MMC console and started IIS Admin and WWW services. Both started successfully now.
After the IIS services were running now I opened Cluster Administrator and brought the Exchange group online.
After weeks my Exchange 2003 cluster was finally functioning as configured. Second node was brought online and included in the cluster.
Why did this happened?
The only reason I was able to find that there was a power outage and the IIS Metadatabase.xml file became corrupt. I hope this article was helpful in solving similar issues. My problem was related to Exchange 2003 but same problem could happen with any IIS depended application.
Today (5th of October 2011) I updated this post. Mainly for my new website format and grammar. I am really happy to see you guys are finding the solution for this problem here on my personal blog. Maintaining this blog does cost me some personal effort to write and maintain the site. If you would like me to continue please consider checking out my sponsor on the right upper corner. Again! thanks for being here.