![]() IIS log files can be quite large for example, in Figure 2, the log file u_ex12101858.log is nearly 100MB in size. Open Windows Explorer and navigate to the directory that contains the IIS log files of the website that experienced the performance problem. You will need this ID to determine which W3SVC* directory to analyze.įigure 1: Getting the ID of your web site This will show you the ID of each website hosted on your server. Open the IIS Manager and select Sites, as shown in Figure 1. In this troubleshooter, I will be using IIS 8. IIS 6 and earlier: %WinDir%\System32\LogFiles.IIS 7 and later: %SystemDrive%\inetpub\logs\LogFiles.Data Collectionīy default, IIS log files are located in the following directories: You can take the information you gather with LogParser and pass it along to your database team, your network team or to your developers for more analysis. In many situations, the tool will help you quickly get to a deeper understanding of what happened on the server and may help you identify problems. Microsoft's LogParser is a good tool that is quick and easy to use. In many cases, other new issues take you away from any serious root cause analysis. You have no details from the users, such as error codes, screen shots and worse, you have no performance data to compare what just happened to normal performance. However, you cannot accept that as a solution and need to know why this happened, but don't know where to start. You jump into action and recycle the worker process all appears to be working again, as normal. There is some mention that web browsers simply time out or stop responding completely when they are accessing your website. Modifying IIS 7 log data in Windows 2008 ScenarioĪs a Systems Administrator you begin to hear reports from users of your system hosted on IIS that the response is slow. The following blog which discusses how to perform this on IIS 7+: So if you haven't already done so, select these additional fields, they will help you find solutions when problems happen. Therefore, the best time to include these additional fields is before you are experiencing system problems. ![]() For example, Bytes Sent and Bytes Received are not selected, but they are very useful when troubleshooting a performance problem. ![]() Before you begin, it is important to note that all fields IIS can log are not enabled by default. This troubleshooter will help you analyze IIS log files in an effort to determine the cause when an application that is hosted on IIS is failing or experiencing performance issues. A basic knowledge of SQL queries is helpful.A basic knowledge of IIS HTTP Status Codes is helpful ( ).By Benjamin Perkins Tools and knowledge used in this Troubleshooter ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |