This post has been republished via RSS; it originally appeared at: IIS Support Blog articles.
You may notice that Failed Request Tracing (FREB) rule is not creating log files even though the condition in your rule is met.
Reinstalling the Tracing module normally solves issues related to FREB but this may not be an acceptable approach if Shared Configuration is used or you can’t restart the server (uninstalling the Tracing module requires server restart)
Here are a few things to checks:
- Make sure FREB is enabled
- Check if the log path is correct
- Check if the application pool identity has permissions to write to this path
- Add a new website and add a rule for status codes between 200 and 600
If there are still no log files, It’s time to check the applicationHost.config file. For an issue I troubleshot, module references were missing. This is how we solved it:
- Back up applicationHost.config file
- Open the original one. Add the following lines in <globalModules> section
- Add the following line into <modules> section
- Make sure the provider definitions are correct. Here is a definition that works for WWW Server:
- Restart IIS and test if logs are created now