The location from which a process is invoked is important. A process, I.e. an executable (.exe) is the program which contains the entry point to the code which needs to run. If the location is in a relative position related to the assemblies it requires, then the .exe can use relative paths to access an […]
Read More →NOTE: it is now possible to achieve this in the Azure portal which means the modification of the XDT file is no longer necessary. It will still work and knowing about this capability might help you implement something which does not currently have an interface to do so…yet. Here is some information about doing this […]
Read More →
In this post, these status codes have to do with ASP.NET Core running on IIS. ASP.NET Core uses a module to direct the request to Kestrel which can be referred to as a proxy. When there is a timeout in the ASP.NET Core application it will return a 408 to the IIS proxy. An HTTP […]
Read More →
These labs provide a group of debugging scenarios focused on helping you get some hands on experience in debugging the most common type of IIS issues. For example, hang/performance, crash and memory issues. Installation These labs are focused IIS 8.5, but can be run on the following versions of IIS IIS Version Operating System IIS […]
Read More →During my many years of active IIS administration which hosted ASP.NET application, we had many discussions about why the first request to the web site took longer than those coming after. In short, it’s because the first request, after a restart of the process results in a recompilation of the temporary ASP.NET files. In complicated, […]
Read More →
On a web server with multiple application pools, there most likely will be multiple W3WP processes. Therefore, the first action to take when creating a memory dump of a W3WP worker process is to find which one you need to get the dump of. I wrote a short article on how to get a worker […]
Read More →An HTTP status code of 502 – Bad Gateway means “The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.” I interpret that to mean that there is a server (server A) between my client and the server (server B) […]
Read More →
I was making a deployment to an ASP.NET Core application from Visual Studio and got this error, see Figure 1. Figure 1, deployment asp.net core web deploy msdeploy from visual studio Read some of my other web deploy articles here: Web Deploy ERROR_DESTINATION_NOT_REACHABLE Azure Web App ERROR_CONNECTION_TERMINATED msdeploy web deploy All of them are accessible […]
Read More →I wrote a number of articles related to this topic, have a look to get a better context in regards to this one. Download Azure App Services Web App log files from Visual Studio Enable logging on your Windows Azure Web App – App Service from Visual Studio Using LogParser to analyze the EVENTLOG.XML, Azure […]
Read More →I was troubleshooting this issue on an Azure App Service (ASE) and found the 404 was actually a 404.63.0 which translates into “Site not found: Hostname lookup failed, we are probably under attack”. The interesting thing was that it was only reproducible randomly and after I sat an hit the F5 or refreshed the page […]
Read More →