SharePoint 2016, Sharepoint 2013, Sharepoint 2010, Windows Server 2012, Sql Server 2012,2014,IIS, Active Directory,User Profile Service, Managed MetaData Service, Search Service, Topology, Web Application, IIS, Site collection, List, Library, PowerShell, office web app, Windows Authentication, NTLM, Kerberos, Saml, ADFS, Active Directory Import, MIM, SharePoint Central Admin http Error, Enable Failed Tracing Request Logging – SharePoint

SharePoint Central Admin http Error, Enable Failed Tracing Request Logging

I think this is the common problem in SharePoint, a lot fo SharePoint administrators face this on the routine basis. Specifically, when you get a generic error i.e The page can’t display with the HTTP 500 error, but no clue from the logs etc. In that case, We should take advantage of the IIS feature of Failed Request Tracing. With tracing for failed requests, you can capture an XML-formatted log of a problem when it occurs, so that you do not have to reproduce the problem before you start troubleshooting. This process consists of the two steps.

  • Enable logging for the Failed Request Tracing
  • Create a Tracing Rule for Failed Requests

Enable Failed Request Tracing

In order to perform this step, one should be Server administrator.

  1. Open IIS Manager
  2. In Connections View, Select Site(SharePoint Central Admin) you can select any site on which you want to enable the logging and in the In the Actions pane, under Configure, click Failed Request Tracing.
    2016-03-25_21h19_11
  3.  In the Edit Web Site Failed Request Tracing Settings dialog box, select Enable to enable logging for this site. In the Directory text box, type the path where you want to store the log files or click the browse button () to find a location on the computer. The default is %SystemDrive%\inetpub\logs\FailedReqLogFiles.2016-03-25_21h24_36

Now Failed Request Tracing is enabled for the SharePoint Central Admin Site. Next Step is to create the Failed Tracing Rule.

Create a Tracing Rule for Failed Requests

  1. Select the Central Admin from Connections Pane and In Features View, double-click Failed Request Tracing Rules.
    2016-03-25_21h25_36
  2. On the Failed Request Tracing Rules page, click Add in the Actions pane.2016-03-25_21h25_58
  3. In the Specify Content to Trace area of the Add Failed Request Tracing Rule dialog box, select AllContent (*)2016-03-25_21h26_15
    • All content (*) – when you want to track all files in a directory.
    • ASP.NET (*.aspx) – when you want to track all .aspx files in a directory.
    • ASP (*.asp) – when you want to track all .asp files in a directory.
    • Custom – when you want to define a failure for a custom set of content, such as “xyz.exe” or “*.jpg”. This can contain, at most, one wildcard and must be local to the directory where the failed request definition is set.
  4. Click Next
  5. In the Define Trace Conditions area of the Add Failed Request Tracing Rule dialog box. Check the Status Code(s) and Enter the Http Error 500.2016-03-25_21h26_36
  6. Click Next
  7. In the Select Trace Providers area of the Add Failed Request Tracing Rule dialog box, I select All.2016-03-25_21h26_54
  8. Click Finish
  9. Now, In feature Pane, you will see a new Rule
    2016-03-25_21h28_04

After this, you have to browse the site and a XML log file will be generated on the location which you defined above.

You may also like...

Leave a Reply

Your email address will not be published. Required fields are marked *