This post has been republished via RSS; it originally appeared at: IIS Support Blog articles.
Several features such as WebSocket Protocol, Tracing or Request Monitor can be installed in IIS server on need basis.
I came across to the error message below in Event Viewer while trying to install Request Monitor in Windows Server 2016
Server Manager displayed this error:
We also tried installation it via PowerShell. Here is the result:
Collect and analyze the following logs:
- CBS logs (C:\Windows\Logs\CBS)
- DISM logs (C:\Windows\Logs\DISM)
- ApplicationHost.config file (C:\Windows\System32\inetsrv\config)
- The output of Dism /Online /Cleanup-Image /ScanHealth command
- Procmon logs (Use Process Monitor tool)
Following questions also help narrowing the issue down:
- Are you able to install Request Monitor by logging in with another user?
- Are you able to install Request Monitor in another server?
- Are there other roles apart from IIS installed in the server?
- Make sure there is enough space in the disks (Right click on Start menu icon > Computer Management > Disk Management)
- If not installed yet, install .NET Framework and try again
In my case, Procmon logs showed PARSE_ERROR_INFO while reading applicationHost.config file which points out an issue with this file.
As the Procmon point out a parsing issue with applicationHost.config file, we tried to open this file. As expected, it was corrupted:
We didn’t have a backup of this file so we had to reinstall IIS. This fixed the issue.