\C:\Windows\system32\inetsrv\config\application Host.config’, line number ’1′. The error message is: ‘Configuration file is not well-formed XML’ When browsing to: C:\Windows\system32\inetsrv\config\application Host.config I noticed that the application Host.config files size was 0kb. After opening up the file I noticed it was wiped clean. Luckily IIS7 automatically keeps the history of the application Host.config file every time there is a change in IIS7. Inside this directory you will find the history of all the application Host.config file. Pick a application Host.config file that you know is not corrupted. View the tracing log for more information about the conflict.
Application Host Config Path = "";$global: Web Administration Ext.
The answer is simple, if not that obvious: win2008 is 64bit, notepad is 32bit.
So all websites and web applications were unavailable. This time IIS7 should open, and you should be able to access all your sites and web apps. Fixing Error: An update conflict has occurred, and you must re-try this action.
The Windows Process Activation Service encountered an error trying to read configuration data from file ‘\\? Copy the application Host.config file and paste it into the C:\Windows\system32\inetsrv\config directory, replacing the corrupted file. The object User Profile Application Name=User Profile Service Application was updated by [farm admin id], in the OWSTIMER (ID) process, on machine [machine name].
Always Backup Host Config = $true; As long as there is now a backup function in Power Shell, might as well round out the suite with a Read and Save function for application Host.config.