Diagnostic Logging in SharePoint

SharePoint includes diagnostic logging and event reporting that can used to troubleshoot errors may be encountered in SharePoint. The below steps will enable SharePoint diagnostic logging:

  1. Navigate to the Operations page on the Central Administration site.
  2. Select Diagnostic Logging in the Logging and Reporting section and the Diagnostic Logging page will appear.
  3. On the Customer Experience Improvement Program section, select if you wish to participate the Customer Experience Improvement Program.
  4. On  the Error Reports section, select whether SharePoint should collect error reports. When SharePoint detects an  error, a dialog box will appear on the server, providing  the option of sending an error report to Microsoft.
  5. On the Event Throttling section, select an event category (for example,  E-Mail) from the listing of events. A report which details the severity of the errors in the event category appears. Events which are  recorded in a server’s event log can be viewed via the Event Viewer. Events which are recorded in the server’s trace log can be viewed in the trace log file. Use the Event Throttling section to indicate the least severe events to record to the trace and event logs.
  6. On the Trace Log section, set the path where trace logs are to be stored and select the number of log files to retain as well as  the number of minutes a single log file is used. When the max log number is reached, the oldest log file will then be overwritten. If you’re encountering a large number of errors in SharePoint, you may need to increase the number of log files retained and reduce  the number of minutes traces are written to the log file. This will allow you to view smaller snapshots of the log entries.
    Note that the log files are normally stored in C:Program FilesCommon Files Microsoft SharedWeb Server Extensions12Logs. You can navigate to that path to view  the trace logs and usage analysis logs. Viewing trace logs is a good method for getting an understanding of the processes which are running on your servers.
  7. Click OK to complete the process.



Array

No comments yet... Be the first to leave a reply!