I am using Application Request Routing 3.0 with IIS's failed request tracing. I am having issues with my rewrite rules so I wanted to troubleshoot it.
I wanted to follow the steps below to enable IIS logging of rewrite rules but the option doesn't seem to be there for me.
I am using Windows 2012 R2
If the Failed Request Tracing was installed after URL rewrite module, the "Rewrite" area in Trace Providers may not be available. If you do not see "Rewrite" area listed there, go to Add/Remove programs and then run URL rewrite module installer in repair mode.
TLDR: you can also just reorder the FRT module to be listed BEFORE the urlrewrite module in IIS.
This simpler solution may appeal to some, versus that ms-documented suggestion to just reinstall urlrewrite. You can go to the server level in iis, choose the "modules" feature, and use its "view ordered list" option. There you will see (in this scenario above) that the Failed request trace module is listed AFTER the urlrewrite module--reflecting the fact that FRT was enabled AFTER urlrewrite was installed. It's an easy situation to end up in, and many then never realize how much frt can help with tracking rewrite rules.
But rather than reinstall urlrewrite (the stock answer), you can just move the frt module to be before urlrewrite, using the options offered there to move modules up or down. (The steps to do that are well-documented by MS and others, so I'll not elaborate them here.)
This way, the frt feature is loaded first and this can watch/track rewrite processing--again achieving the same goal as the proposed uninstall/reinstall of urlrewrite.
Hope that helps some. Sadly, even a lot of resources on using FRT to help debug rewrite rules don't acknowledge this surprisingly common problem, let alone either solution here.
