I have seen problems several times over my career where Windows Update, Antivirus software, or a backup service was running and killing the server CPU.
You need to identify if your application itself is using all of the CPU or is something else going on. If your server CPU is pegged at 100%, your application is going to be running slow.
#TROUBLESHOOT IDISPLAY HOW TO#
Let’s review how to troubleshoot these types of ASP.NET web application problems. Including a problem with an application dependency (like SQL Server, Redis, etc) or a spike in traffic. If your ASP.NET web application is online, but the entire application is running slow, you could have a few common problems. Learn more: How to Use Web.Config customErrors for ASP.NET What to do If Your Entire Application is Slow However, this could be helpful if your application is down and you need a quick solution. Please note that this could show potentially sensitive information.
#TROUBLESHOOT IDISPLAY FULL#
You could temporarily disable your custom error page and make ASP.NET show the full exception details. You probably see the standard ASP.NET error page (“yellow screen of death”) or your custom error page. This makes it hard to troubleshoot ASP.NET problems. If your application is throwing an exception on every page load, you are most likely not able to see the details of it. A similar issue could happen with a PageOutput cache provider. You could also have problems with your ASP.NET session provider, caching, or other application dependencies that are used on every single web request.įor example, if you use Redis or SQL Server as your ASP.NET Session provider and they are down, you could see exceptions on every page load. If every page load throws an exception, you likely have a configuration problem in your Web.config or nfig. Learn more: How to Catch All Exceptions in C# & Find All Application Errors You may also want to check Windows Event Viewer if you can gain access to it. Depending on the issue and how you are doing exception logging, it might be getting logged to a file or your error tracking tool.
To solve this issue, you need to quickly check your error logs. IIS Manager Application Pools Does Every Page Load Cause an Exception or 500 Internal Server Error?
0 kommentar(er)
