Blog of "Brian Murphy-Booth" a.k.a. "Brian Booth"
-
IIS7: Using Basic Authentication may cause premature user lockouts.
PROBLEM:
-
DelegConfig v2 (beta)
http://www.iis.net/downloads/default.aspx?tabid=34&g=6&i=1887
-
The Application Data folder for Visual Studio could not be created.
PROBLEM:
-
The object identifier does not represent a valid object.
PROBLEM:
-
Remote debugging ASP.NET applications using Visual Studio 2008
If you have recently upgraded a Visual Studio .NET 2003 ASP.NET application project or a Visual Studio 2005 Web Application project to a Visual Studio 2008 ASP.NET Web Application project you may have noticed the following popup. Needless to say this makes it a little more difficult to connect remotely to your project in order to run and debug it:
-
Static variable, Shared variable... does it matter?
Introduction
-
How to troubleshoot an IIS "Event ID: 1009" error.
An error that most IIS 6.0 administrators have probably encountered is "Event ID: 1009" which usually leads to a "503 Service Unavailable" error being displayed in a browser. "503" usually indicates the Application Pool has been disabled for some reason. The IIS support team frequently gets support calls to help resolve this issue and over the years I have compiled a list of steps I use to troubleshoot this. If the following information seems too confusing please let me know and I'll clarify any confusing points. The follow list is broken down into different sections for the various "exit codes" that are in the Event 1009.
-
DelegConfig (Kerberos/Delegation Configuration Reporting Tool)
Where is the tool?
-
The biggest mistake: ServicePrincipalName’s
Note: All of your Kerberos configuration questions can be answered by using the DelegConfig tool that I wrote. You can find that tool here
-
How to setup ASP.NET v1.1 (Visual Studio .NET 2003) projects on IIS7 (Vista)
Note: Although you can get Visual Studio .NET 2003 to work properly on Vista, Microsoft does not support this scenario. "Not supported" doesn't mean "won't work". It just means if you run into any trouble you just can't call the MS support line for assistance with this issue. Microsoft does, however, fully support *running* a .NET v1.1 app on Vista.