Failed Request Tracing feature or FREB for short, is one of the most useful debugging features of IIS. While it gives an overview of how the request is being processed, it also helps to trigger dumps for various failure scenarios.
We recently came across a scenario where one of our customers was not able to use procdump and also didn't want to keep the debug diag rule running. In such a scenario, we used the dbghost.exe of Debug Diag to create a dump when FREB gets collected. This article will explain detailed step by step procedure for the same.
Install Debug Diagnostic tool. The latest version of the Debug Diagnostic tool can be found here
Identity of the Application pool being used, must be a member of local Administrators group
We also need to make sure that customActionsEnabled is true for the site we are working on. There are 2 ways we can do this: Using IIS: Go to the Configuration Editor at root level and navigate to system.applicationHost/sites. Click on the ellipsis at the right most corner to open up the sites:
In the pop up window that appears select the required site and expand traceFailedRequestsLogging. Make sure the value for customActionsEnabled is True.
Using applicationhost.exe: Go to the site level and make the following changes: