Troubleshooting an unresponsive web server (IIS) – Part 1 of 2, gathering the data

A web server is deemed to be unresponsive if it’s either not providing a response at all and/or it’s not achieving the response time (performance) expectations of the users.   In my “Troubleshooting 101” post, I mentioned that after the problem has been defined (ie basic facts collected), the next step in the troubleshooting process…

0

Troubleshooting 101

It’s been far too long between blog posts so here’s a post and a promise to blog more frequently…   I thought I’d share some of my thoughts on this topic that’s been the focus of my career for the past 7.5 years.  I’ve tried to keep this as generic as possible.   Troubleshooting is…

3

ASP.NET instrumentation (tracing) to a file

It’s often helpful to instrument your code to help with troubleshooting, etc.  Instrumentation is really just a fancy word for tracing. Here’s an example of tracing to a file from ASP.NET. <%@ Page Language=”C#” CompilerOptions=”/d:TRACE” %><script runat=”server”>void Page_Load(object sender, EventArgs e){                System.Diagnostics.Trace.WriteLine(String.Format(“{0},{1}”, DateTime.Now, “Hello world!”));}</script> <configuration>  <system.diagnostics>    <trace autoflush=”true”>      <listeners>        <add name=”mytrace” type=”System.Diagnostics.TextWriterTraceListener” initializeData=”c:\temp\mytrace.csv” />     …

1