6 Ways to Find Failed ASP.NET Requests
6 Ways to Find Failed ASP.NET Requests
Trying to reproduce an error in production or chasing down IIS logs/IIS error logs is not fun — but tracking errors is one of the most important things teams should do.
Join the DZone community and get the full member experience.Join For Free
Sensu is an open source monitoring event pipeline. Try it today.
Your web application is throwing some sort of error or invalid response. Do you know how to troubleshoot IIS or ASP.NET errors on your servers? Luckily, Windows and ASP.NET provide several different logs where failed requests are logged beyond simple IIS logs.
Get to Know the 4 Different IIS Logs
You are probably familiar with normal IIS logs, but there are some other places to look if you are looking for more detailed error messages or can’t find anything in your IIS log file.
1. Standard IIS Logs
Standard IIS logs will include every single web request that flows through your IIS site. Via IIS Manager, you can verify that your IIS logs are enabled and where they are being written to.
You should find your logs in folders that are named by your W3SVC site ID numbers.
By default, each logged request in your IIS log will include several key fields including the URL, querystring, and error codes via the status, substatus, and win32 status. These status codes can help identify the actual error in more detail.
#Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) cs(Referer) sc-status sc-substatus sc-win32-status time-taken 2016-09-13 21:45:10 ::1 GET /webapp2 - 80 - ::1 Mozilla/5.0 - 500 0 0 5502 2016-09-13 21:45:10 ::1 GET /favicon.ico - 80 - ::1 Mozilla/5.0 http://localhost/webapp2 404 0 2 4
The “sc-status” and “sc-substatus” fields are the standard HTTP status code of 200 for OK, 404, 500 for errors, etc.
The “sc-win32-status” can provide more details that you won’t know unless you lookup the code. They are basic Win32 error codes.
By the way, if you are using Retrace, you can also use it to query across all of your IIS logs as part of it’s built in log management functionality.
2. HTTPERR Is Your IIS Error Log
Every single web request should show in your IIS log. If it doesn’t, it is possible that the request never made it to IIS, or IIS wasn’t running. Also, be sure that your IIS logging is enabled.
Incoming requests to your server first route through HTTP.SYS before being handed to IIS. These type of errors get logged in HTTPERR. Common errors are 400 Bad Request, timeouts, 503 Service Unavailable, and similar types of issues. The built-in error messages and error codes from HTTP.SYS are usually very detailed.
3. Look for ASP.NET Exceptions in Windows Event Viewer
By default, ASP.NET will log unhandled 500 level exceptions to the Windows Application EventLog. This is handled by the ASP.NET Health Monitoring feature. You can control settings for it via
system.web/healthMonitoring in your
Very few people realize that the number of errors written to the Application EventLog is rate limited. So, you may not find your error! By default, it will only log the same type of error once a minute. You can also disable writing any errors to the Application EventLog.
Can’t find your exception? Depending on if you are using WebForms, MVC, Web API, WCF, or other frameworks, you may have issues with ASP.NET not writing any errors at all to ASP.NET due to compatibility issues with the health monitoring feature.
4. Failed Request Tracing for Advanced IIS Error Logs
Failed request tracing (FRT) is probably one of the least used features in IIS. It provides robust IIS logging and works as a great IIS error log. FRT is enabled in IIS Manager and can be configured via rules for all requests, slow requests, or just certain response status codes.
The only problem with FRT is it is insanely detailed. It tracks every detail and every step of the IIS pipeline. You can spend a lot of time trying to decipher a single request.
5. Make ASP.NET Show the Full Exception — Temporarily
If you can reproduce the problem, you could modify your ASP.NET web.config to see exceptions. Typically server side exceptions are disabled from being visible within your application for important security reasons. Instead, you will see a yellow screen of death (YSOD) or your own custom error page. You can modify your application config files to make exceptions visible.
You could use remote desktop to access the server and set customErrors to “RemoteOnly” in your web.config so you can see the full exception via “localhost” on the server. This would ensure that no users would see the full exceptions but you would be able to.
If you are OK with the fact that your users may now see a full exception page, you could set customErrors to “Off.”
With .NET Core, how error handling works has been completely changed from previous versions of ASP.NET. You now need to use the DeveloperExceptionPage in your middleware.
6. Using a .NET Profiler to Find ASP.NET Exceptions
.NET Profilers like Prefix (which is free!) can collect every single exception that is thrown in your code even if they are hidden in your code. Prefix is a free ASP.NET profiler that is designed to run on your workstation to help you optimize your code as you write it. Prefix can also show you your SQL queries, HTTP calls, and much, much more.
Get Proactive About Tracking Application Errors
Trying to reproduce an error in production or chasing down IIS logs/IIS error logs is not fun. Odds are, there are probably many more errors going on that you aren’t even aware of. When a customer contacts you and says your site is throwing errors, you better have an easy to see them! Tracking application errors is one of the most important things every development team should do.
Published at DZone with permission of Matt Watson , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.