Using IIS 8.0 Logging for Troubleshooting Troubleshooting Authentication and Authorization Troubleshooting Communication Troubleshooting Configuration
Why Audit IIS Logs? How the Tracing Infrastructure Works When to Monitor for Critical Errors Creating a Tracing Rule to Monitor Critical Errors Configuring Selective Logging for an Application Best Practices for Logging
IIS 8.0 logs request details that contain valuable troubleshooting information Web Clients Web Server
Trace event sources w3core Trace event consumers Any pipeline module TRACE_EVENT Consumer Module Read trace config Trace config Trace output
Active monitoring can resolve errors with minimal impact on performance and availability Considerations for monitoring critical errors: Use default logging to capture minimal data about the occurrence of critical errors Set Tracing Rules to capture more detail about frequent errors as needed Use more aggressive monitoring in testing and early deployment
To Add a Failed Request Tracing Rule: Add Failed Request Tracing Rule Wizard Choose Error Conditions Choose Modules and Verbosity To Configure a Failed Request Tracing Rule: Use specific error numbers and ranges (500, 404) Choose relevant modules (ASP.NET, CGI and ISAPI) Specify the minimal amount of data needed
To Configure Selective Logging: Enable per-site Logging Enable as needed for the application Choose what to log Scenarios: Enable detailed logging per application not entire site Newly deployed or beta applications Troubleshooting problems specific to a single application
Benefit Conserve Disk Space Best Practice Recycle logs automatically Minimize Impact to Performance Log only necessary data Write log files to a separate physical disk Secure log files Assign permissions per application
What are Common Error Messages? Reviewing Common Causes of Errors Enabling Trace Logging Auditing IIS Logs for Authentication and Authorization Issues Demonstration: Examining the Output of Trace Logging
Display Example Client - Default Client - Custom Server FREB Log
401.1 401.2 Error Common Causes User supplied incorrect username/password Application Pool identity Anonymous Authentication configuration Browser issue with Integrated Authentication Intervening proxy server 401.3 Wrong ACLs
Enable Trace Logging to Further Troubleshoot Authentication and Authorization Errors Use Tracing to: Find the identity that is failing Identify the resource that cannot be accessed
Use IIS Logs and Failed Event Tracing to distinguish authentication and authorization issues
What are Common Communication Error Messages? Reviewing Common Causes of Communication Errors Auditing IIS Logs for Communication Issues Verifying Communication
Scenario Example Client - Not connected to server Client Server error Server to Server Detailed Error
400 Error Common Causes DNS error Network problem W3SVC service is not started 503 Application has been stopped by Rapid Fail Protection Connection Reset Idle time exceeded the set limits Proxy or redirection issue
Use IIS Logs and Detailed Errors to pinpoint communication failures
Use Tools to Verify Communication Use Tools to: Check availability Identify the resource that cannot be accessed
What are Common Configuration Error Messages? Reviewing Common Causes of Web Application Errors Auditing IIS Logs for Configuration Issues
Scenario Example Client Denied access Client Server error Server Detailed Error
Error 401 or 403 Common Causes Default document or handler missing or invalid 503 Configuration is invalid or corrupted 500x Application specific issues
Use Failed Request Tracing logs to find the root cause
Exercise 1: Troubleshooting Authentication Exercise 2: Troubleshooting Authorization Exercise 3: Troubleshooting Communication Exercise 4: Troubleshooting Configuration
In this module, you have learned to: Audit logs to troubleshoot IIS Troubleshoot authentication based on common error messages Troubleshoot authorization types for IIS 8.0 Troubleshoot communication when managing a Web server Troubleshoot configuration based on common error messages