I have written a number of troubleshooting labs here, one of which is Lab 21: WinDbg – Memory Consumption. In this article I will identify how to capture a memory dump of a process that is consuming too much memory. In this case it is running on an Azure App Service Web App. NOTE: This […]
Read More →
If you ever need to capture trace from within the Azure Portal to troubleshoot an issue, here are the steps required to do that. Login to the portal here. Navigate to the step just prior to where the issue is happening. Press F5 or refresh. Press F12 to start the browser Developer Tools (IE and […]
Read More →
I was building a new server to use while creating my IIS labs here, and got this error shown in Figure 1. Figure 1, 500.19 Internal Server Error These errors can be caused by numerous things, but in this case it was because I did not have ASP.NET installed And as you can see, in […]
Read More →
I created a sample ASP.NET application that you can download from here that contains a slow running request, a handled and an unhandled exception. UPDATE: I wrote an article here about remote debugging in Visual Studio 2017 and ASP.NET Core here, titled “Remote debug your Azure App Service 2017 including ASP.NET Core”, JIC you are […]
Read More →
This has been my favorite WinDbg extension for a long time and I am very happy to see that it has been made public. It can be downloaded from here. To load the MEX extension, copy the MEX.DLL into the winext directory under which your WinDbg client is running. It can be placed any where […]
Read More →Prerequisites Read this about .NET Compilation Read this about why debug=true is not good for performance Understand that ASP.NET (ASPX, ASCX, ASAX, MVC) files are compiled into a DLL and stored into c:\Windows\Microsoft.NET\Framework?\v?.?.?\Temporary ASP.NET Files Setup Install CSharpGuitarBugs.zip onto an IIS web server as per Lab 1 Install the ASP.NET Role Open the IIS Manager […]
Read More →Prerequisites Review the requestFiltering attribute here Read information about HTTP 400 – Bad Request here Check out the new Microsoft Message Analyzer here Check out Network Monitor here Setup Install and Configure CSharpGuitarBugs on an IIS server as described in Lab 1 Lab 23-1 Access the CSharpGuitarBugs website from a client machine, not from the […]
Read More →This is a important concept to know and it really isn’t an intuitive one, you need to get into the guts of IIS or configure some 3rd party web based application to ever see or configure modules and handlers in IIS. When you install ASP.NET for example, the handler is installed and configured by default. […]
Read More →Setup: Install Debugging Tools for Windows – for WinDbg Install and configure CSharpGuitarBugs on an IIS server as described in Lab 1 Place PROCDUMP executable on the IIS Server Review memory dump collection process for W2K8 and W2K12 Lab 21.1 Open the main page of the CSharpGuitarBugs website so that a W3WP process is instantiated […]
Read More →Setup Install Debugging Tools for Windows – For WinDbg Install and Configure CSharpGuitarBugs on an IIS server as described in Lab 1 Place PROCDUMP executable on the IIS Server Review Memory Dump using PROCDUMP on 2008R2 or 2012R2: Lab Open the CSharpGuitarBugs website Click on the ‘Enter Payment Information’ link and note about how long […]
Read More →