Click here to Skip to main content
Click here to Skip to main content
Go to top

Recover IIS When ApplicationHost.config is Ruined

, 2 Aug 2013
Rate this:
Please Sign up or sign in to vote.
Introduce how to recover IIS when it is broken by bad editing to applicationHost.config

Issue Description 

Sometimes we have to manually modify applicationHost.config. It is risky because bad editing can ruin the file and cause IIS to be broken. IIS cannot recover even after we have fixed the errors in all applicationHost.config files appeared on the machine and have restarted the machine.


The solution is to use AppCmd.exe. We can find it in C:\Windows\System32\inetsrv.

First, we use "appcmd list backup" to display all the available backups. Then we pick out a proper backup and use "appcmd restore backup <backup name>" to recover IIS. You could see these steps in the following screenshot: 

Note: You need to open the backup file and check if it contains errors before you choose it to recover IIS. You could find these backup files in C:\inetpub\history. The sub folder names are the same as the backup names.


This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


About the Author

Zhuyun Dai
China China
Over 10-years experience in using Microsoft technologies.
At present, working as the architect of a clustered real-time data delivery and visualization system, responsible for the design of component architecture, product packaging and deployment, also targeting private cloud solutions for future.
Follow on   LinkedIn

Comments and Discussions

-- There are no messages in this forum --
| Advertise | Privacy | Mobile
Web03 | 2.8.140916.1 | Last Updated 2 Aug 2013
Article Copyright 2013 by Zhuyun Dai
Everything else Copyright © CodeProject, 1999-2014
Terms of Service
Layout: fixed | fluid