Unexpected prompts for integrated authentication on WSS Developer VM

After installing all outstanding updates on the WSS Developer VM I started getting unexpected prompts for authentication. First I tried disabling the loopback check as per KB896861.  Unfortunately, no luck. Seems the issue had to do with IE detecting the wrong zone.  It was detecting the Internet zone whilst I’m clearly in the Intranet zone…

1

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

Lucascan’s top 5 tips for a healthy ASP.NET application

These tips are reasonably well-known and have been blogged by others.  However, considering how often I come across these common “mistakes”, I felt yet another blog post was worthwhile: 1) Disable ASP.NET debugging in production! I cannot emphasize this enough, Set debug=”false” in all your web.config’s.   I’m regularly pleasantly surprised by how many production issues can…

2

.NET 2.0 WebException "The underlying connection was closed: A connection that was expected to be kept alive was closed by the server"

I’ve been working with a few customers lately that have been experiencing this WebException that has been confirmed as an issue introduced by connection management design changes incorporated into .NET 2.0.  The exception typically ocurrs during a web service call however any scenario involving a HttpWebRequest with keep-alives could encounter this issue.    Note, this…

1

Reducing Netmon trace file size via capturing only a single port using a capture filter

This is a handy tip to reduce the file size of your Netmon traces.  This is particularlly useful when you need to leave the trace running for an extended period of time.   Thanks go to my collegue Andreja Rusjakovski for this tip… Just before starting the trace go to Capture->Filter->Load button and select a *.cf file. …

1

Using Microsoft Network Monitor (Netmon) to capture a network trace

1) Download and install Netmon from the following URL.  Note, the password for the .zip is “trace”. ftp://ftp.microsoft.com/pss/tools/netmon/netmon2.zip 2) Start Netmon. Administrative Tools->Network Analysis Tools->Network Monitor 3) Select the appropriate network interface. The first time you run Netmon, you’ll be asked to select the network interface to trace.  The following command from the command line…

2