A website I built is experiencing intermittent failures where a posted back page appears to not be processed. In its wake, the user is left with a blank white page. A typical response to this situation is, "well, I have verified that it is not code related. I cannot reproduce this error. I think it has everything to do with the server and not the code." How frustrating is this for the customer?

After a few months of moving the code base around since that seemed to ameliorate the problem, at least temporarily, the source of the error is uncovered. "Ah hah!" I knew it was not code related, and secretly, I am grateful it was not code related. As it turns out, the server was the culprit.

After you install the Microsoft .NET Framework Software Development Kit (SDK) or Microsoft Visual Studio .NET, Microsoft Internet Information Services (IIS) mappings are created to associate new file name extensions and new settings for ASP.NET. The web server needed to repair IIS mappings so that the file name extensions for ASP.NET are properly associated. To read more about it, follow this link, ASP.NET Pages Exhibit Unexpected Behavior Because the Server-Side Code Is Not Processed.