[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 301
  • Last Modified:

FREB Not Working?

The saga continues...now my freb files are not being sent to the correct directory for some of my sites.  In fact I can't find them at all.  I have Failed Request Tracing enabled and a custom directory indicated.  Everywhere I look it seems fine.  Would appreciate a "don't forget to do ..." advice if anyone has any.
0
Bob Schneider
Asked:
Bob Schneider
  • 9
  • 6
  • 3
9 Solutions
 
Scott Fell, EE MVEDeveloperCommented:
I don't use this feature enough.  When you enabled it you should be able to designate where they go.  The default is inetpub\logs

http://www.iis.net/learn/troubleshoot/using-failed-request-tracing/troubleshooting-failed-requests-using-tracing-in-iis-85
0
 
Scott Fell, EE MVEDeveloperCommented:
Mine are at (server 2012, iss 8)  C:\inetpub\logs\FailedReqLogFiles\
0
 
Bob SchneiderAuthor Commented:
Right I put each site's logs in it's own file: (C:\inetpub\logs\FailedReqLogFiles\etraxc for instance).  It works for some but not all.  Is it related to a custom error page setting?  I'm a little perplexed.
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Big MontySenior Web Developer / CEO of ExchangeTree.org Commented:
It works for some but not all

did you make sure you enabled it when you were logged in as an admin?

did you enable it at the site level and not the server level?


**edit - changed first line from code block to quote block
0
 
Bob SchneiderAuthor Commented:
Yes, and yes...
0
 
Big MontySenior Web Developer / CEO of ExchangeTree.org Commented:
the 2nd yes, you set it at the site level OR the server level?
0
 
Bob SchneiderAuthor Commented:
I set the features and roles in the server but set the parameters for each failed request log at the site level.  Should I do something at the default website level?
0
 
Big MontySenior Web Developer / CEO of ExchangeTree.org Commented:
you can try, but I don't think it'll resolve the issue...

the custom folder you set up for the logs, do they have read/write permissions for whatever accounts you use to run your websites (this would only be relevant if you were using a unique user for each of your sites)?
0
 
Scott Fell, EE MVEDeveloperCommented:
The iis_iusrs account has write and special permissions
0
 
Bob SchneiderAuthor Commented:
I don't think it a permissions thing because when we were trying to get the server running on Sunday the FREB was working.  Only after I redid the sites without the old web.config file did the FREB not work.

Could this be related to the web.config issue?  Should there be a section in that file indicating failed request tracing?
0
 
Big MontySenior Web Developer / CEO of ExchangeTree.org Commented:
it may, do you have a tracing section in your web.config, something like the example below taken from here?

<tracing>
   <traceFailedRequests>
      <add path="*.aspx">
         <traceAreas>
            <add provider="ASPNET" areas="Infrastructure,Module,Page,AppServices" verbosity="Warning" />
         </traceAreas>
         <failureDefinitions statusCodes="404" />
      </add>
   </traceFailedRequests>
</tracing>

Open in new window

0
 
Bob SchneiderAuthor Commented:
No its not there.  Can it be created manually or is there a way to get the system to create it?
0
 
Bob SchneiderAuthor Commented:
Or is there something I did not do to cause that????
0
 
Big MontySenior Web Developer / CEO of ExchangeTree.org Commented:
You can put it in manually. Try doing that and see if that helps
0
 
Bob SchneiderAuthor Commented:
ok would I have to modify your snippet at all for a classic asp page that wanted to send all 500 errors to C:\inetpub\logs\FailedReqLogFiles\site_fldr
0
 
Big MontySenior Web Developer / CEO of ExchangeTree.org Commented:
As a test follow the instructions in the link to see if you can get the trace to work with a 404 error. Once that is working we'll work on the 500 messages
0
 
Bob SchneiderAuthor Commented:
Here is what i put in there...no love.  Let me know if it is incorrect.

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <system.webServer>
        <defaultDocument>
            <files>
                <clear />
                <add value="Default.asp" />
                <add value="Default.htm" />
                <add value="index.htm" />
                <add value="index.html" />
                <add value="iisstart.htm" />
                <add value="default.aspx" />
            </files>
        </defaultDocument>
        <httpErrors>
            <remove statusCode="404" subStatusCode="-1" />
            <remove statusCode="500" subStatusCode="-1" />
            <error statusCode="500" prefixLanguageFilePath="" path="/500err.asp" responseMode="ExecuteURL" />
            <error statusCode="404" prefixLanguageFilePath="" path="/404err.asp" responseMode="ExecuteURL" />
        </httpErrors>
      <tracing>
        <traceFailedRequests>
          <add path="C:\inetpub\logs\FailedReqLogFiles\gopherstateevents">
            <traceAreas>
              <add provider="ASPNET" areas="Infrastructure,Module,Page,AppServices" verbosity="Warning" />
            </traceAreas>
            <failureDefinitions statusCodes="404" />
          </add>
        </traceFailedRequests>
      </tracing>
    </system.webServer>
</configuration>

Open in new window

0
 
Bob SchneiderAuthor Commented:
Thanks for your help.  Finally got them working.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 9
  • 6
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now