Article ID: 815167 - Last Review: April 30, 2003 - Revision: 1.6 HOW TO: Monitor Errors in .NET-Connected ApplicationsOn This PageSUMMARYThis step-by-step article describes how to monitor errors in
.NET-connected applications. The .NET-connected applications log errors in
several different ways. Errors that occur in the .NET Framework itself are
logged to the Application Event Log. For example, when ASP.NET recycles an
application that exceeds the specified memory usage, an event is logged to the
Application Event Log that details the quantity of memory that is
consumed. Most events that occur in an application are also logged to the Application Event Log. However, whether the event is logged or not logged is dependant on the application developer. ASP.NET applications frequently rely on the system administrator to parse the HTTP logs to identify HTTP 500 error codes. These error codes identify application failures. Instead of manually monitoring event logs and HTTP logs, administrators can use the Performance snap-in to detect when errors occur. back to the top View .NET Framework Errors by Using the Event ViewerAny type of .NET-connected application, such as Microsoft Windows applications, Web services, and Web applications, can add events to the Application Event Log. You can monitor the Application Event Log to identify and to troubleshoot errors. To view .NET Framework errors by using the Event Viewer, follow these steps:
View ASP.NET Errors Located in HTTP LogsAn error may occur in ASP.NET that the application cannot handle. In this case, Internet Information Server (IIS) logs the request and the response code in the HTTP logs. These logs do not contain a detailed description of the type of error that occurred. However, the log does contain information about the time of the request, the page requested, and the user who issued the request. This information permits you to reproduce and to isolate the error.By default, HTTP logs are stored as text files in subfolders of the \%SystemRoot%\system32\LogFiles\W3SVC#\ folder. While there is no graphical tool that you can use to view the errors that are contained in HTTP logs, there are third-party applications that can analyze IIS log files. When you interactively troubleshoot ASP.NET error messages, you can use trace capabilities to gather more detailed information about the failed requests. back to the top Monitor Errors in Real TimeASP.NET Web applications that experience problems may not add events to the event log. In this case, you will find it difficult if you try to track those problems by parsing HTTP logs. You can use the Performance snap-in to monitor for ASP.NET errors in real time. To monitor ASP.NET errors by using the Performance snap-in, follow these steps:
back to the top REFERENCESFor more information about using the Event Viewer snap-in,
visit the following Microsoft Web site: http://msdn.microsoft.com/library/en-us/comsrv2k/htm/cs_mmc_monitorsites_ezuz.asp (http://msdn.microsoft.com/library/en-us/comsrv2k/htm/cs_mmc_monitorsites_ezuz.asp) back to the top APPLIES TO
| Article Translations
|

Back to the top
