IIS7 – post #29 – 100 days and counting of IIS7 / Longhorn

I was celebrating my https://iislogs.com server has been up for 100 days by geeking on HTTP Modules / HTTP Handlers.  I’m still working through my HTTP module / handlers example.  Once I have the code finished, I’ll post up.  I found some good links for this topic.  Enjoy

ASP.NET Application Life Cycle Overview  (Nice graph of all events)

Introduction to HTTP Handlers 

Introduction to HTTP Modules 

Custom ASP.NET Processing with HTTP Handlers 

ASP.NET 2.0 Internals 

appcmd list config /section:system.webServer/modules

appcmd list config /section:system.webServer/handlers

appcmd list config /section:system.webServer/handlers

The first 100 days of IIS7

Basic Powershell examples, couple useful commands

I’ve been bitten by the Powershell bug.  My scripting background tells me I should really learn this tool.  Since I’ve been writing console applications for a few years, mostly to do WMI and related Web service calls.  This should be fairly easy in Powershell.  As with anything, learning the syntax and how things are done is a bit frustrating at first.  There are tons of examples available, however if you are like me, you need to figure it out the hard way. Once you get the swing of it, things should be pretty straight forward.

After figuring out a couple of examples, which are posted below, I’m starting to get the swing of it.  There is a lot though I don’t understand but this will come in time. I miss intellisense that is built into Visual Studio.   The get-member cmdlet is useful in helping figure out which methods / properties are available to use.  Another command I like is man.  A few years back, I got into FreeBSD and used the ‘man’ command all the time.  Powershell has this available and it seems natural.  This is a basic blog, but helps me learn Powershell and share some a couple examples for future reference.  Happy Scripting!

Using MAN to pipe out information on get-member cmdlet

Type PS c:>man get-member

This is what is displayed,  a nice short version of help.

    Gets information about objects or collections of objects.
    Get-Member [[-name] <string[]>] [-inputObject <psobject>] [-memberType {<AliasProperty> | <CodeProperty> | <Propert
    y> | <NoteProperty> | <ScriptProperty> | <Properties> | <PropertySet> | <Method> | <CodeMethod> | <ScriptMethod> |
    <Methods> | <ParameterizedProperty> | <MemberSet> | <All>}] [-static] [<CommonParameters>]
    Gets information about the members of objects. Get-Member can accept input from the pipeline or as the value of the
     InputObject parameter. You can use the MemberType parameter to specify the type of members you want information ab
    If you pipeline input to Get-Member, it outputs a MemberDefinition object for each distinct type of input object. 
    For example, if you pipe the output of Get-ChildItem to Get-Member in a directory that includes at least one subdir
    ectory and one file, it returns two MemberDefinition objects. One includes information about the FileInfo object an
    d the other includes information about the DirectoryInfo object. Get-Member outputs only two MemberDefinition objec
    ts, regardless of how many files or subdirectories are in the directory.
    The output of Get-Member is different if you supply input by using the InputObject parameter. In that case, Get-Mem
    ber returns a single MemberDefinition object that represents either the single input object or the collection class
     that contains the set of input objects.
    To retrieve information about static members, you must specify the Static parameter.


    For more information, type: "get-help Get-Member -detailed".
    For technical information, type: "get-help Get-Member -full".

Create a new object at the command line
$sw = new-object System.IO.StreamWriter("c:tempss.txt")

Type this to find out all methods available
$sw | get-member -memberType methods

PS C:temp> $sw | get-member -membertype methods

   TypeName: System.IO.StreamWriter

Name                      MemberType Definition
—-                      ———- ———-
Close                     Method     System.Void Close()
CreateObjRef              Method     System.Runtime.Remoting.ObjRef CreateObjRef(Type requestedType)
Dispose                   Method     System.Void Dispose()
Equals                    Method     System.Boolean Equals(Object obj)
Flush                     Method     System.Void Flush()
GetHashCode               Method     System.Int32 GetHashCode()
GetLifetimeService        Method     System.Object GetLifetimeService()
GetType                   Method     System.Type GetType()
get_AutoFlush             Method     System.Boolean get_AutoFlush()
get_BaseStream            Method     System.IO.Stream get_BaseStream()
get_Encoding              Method     System.Text.Encoding get_Encoding()
get_FormatProvider        Method     System.IFormatProvider get_FormatProvider()
get_NewLine               Method     System.String get_NewLine()
InitializeLifetimeService Method     System.Object InitializeLifetimeService()
set_AutoFlush             Method     System.Void set_AutoFlush(Boolean value)
set_NewLine               Method     System.Void set_NewLine(String value)
ToString                  Method     System.String ToString()
Write                     Method     System.Void Write(Char value), System.Void Write(Char[] buffer), System.Void Wr..
WriteLine                 Method     System.Void WriteLine(), System.Void WriteLine(Char value), System.Void WriteLi..

‘Create a web request
$request = [System.Net.WebRequest]::Create("http://www.iislogs.com/testlink.aspx")
$response = $request.GetResponse()
$requestStream = $response.GetResponseStream()
$readStream = new-object System.IO.StreamReader $requestStream
new-variable db
$db = $readStream.ReadToEnd()

‘Create a new file and write the contents of that to a file
$sw = new-object system.IO.StreamWriter("c:tempss2.txt")
get-content "c:tempss.txt"

Take care,

Steve Schofield
Microsoft MVP – IIS

Searching logfiles with Powershell, Log parser, Findstr, QGrep

I’m on a mission!  I have to search log files that are between 150 MB and larger.  These are syslogd files generated.  Here is sample output.

2023-01-15 00:00:10 Mail.Debug join[00000]: server.steve.net[] 1168837209-0ff301650000-3Bdfku 1168837209 1168837210 SCAN – [email protected] [email protected] – 2 39 *abcdef.xyz.com SUBJ:Blah this is replaced

I don’t confess to be an expert but this has got to be easier than I’m making it.  I want to share my experiences, so far and I love adventures like this, because I learn a lot. What am I after?  I want the ‘server.steve.net[]’ or just [].  

Example #1 – For small files this works good

$sb =  new-object System.Text.StringBuilder
$re = new-object regex(‘[(d{1,3}).(d{1,3}).(d{1,3}).(d{1,3})]’)
$m = $re.match((get-content mySysLogfile.txt))
while ($m.Success)
$m = $m.NextMatch()
$sb.ToString() > st1.txt

Example #2 – Works for large files extracting the data, performance takes a couple hours.

$sb =  new-object System.Text.StringBuilder
$re = new-object regex(‘[(d{1,3}).(d{1,3}).(d{1,3}).(d{1,3})]’)
$m = [System.IO.File]::OpenText("d:tempsyslogcatchall16.txt")
while($line = $m.ReadLine())
$line = $re.Match($line)
$sb.ToString() > st1.txt

Log Parser example

‘Example 1
logparser -i:tsv "select top 50 Count(extract_token(field6,1, ‘[‘)) as CountOfIt,extract_token(Field6,1,'[‘) as IPAddress into Steve.csv from  ‘\ServerNameShareNamesyslogd11.txt’ Group By IPA
ddress order by CountOfIt DESC" -headerRow:off -iSeparator:’spaces’

‘Example 2
logparser -i:tsv "select Top 10 Count(field6),Field6 from\ServerNameShareNamesyslogd11.txt Group By Field6" -headerRow:off -iSeparator:’spaces’



In conclusion, the clear winner was Log parser, speed and accuracy were great.  Powershell was ‘cool’ but took too long.  Maybe as I get better at Powershell, that will change.  Findstr & QGrep appear to be more for parsing out entire lines of text.  That was my experience, it could be my lack of advanced knowledge with these tools.  I use FINDSTR a lot for doing quick searches, it is faster than FIND.  I was hoping to use regular expressions, but found Powershell was easier to use for regex.  I didn’t try a grep utility found on sourceforge, because Log Parser did the trick.  If you have other experiences using FINDSTR, QGrep or some other tool, please pass them along.  Hope this helps!

Debug Diagnostic Tool v1.1 download

The Debug Diagnostic Tool (DebugDiag) is designed to assist in troubleshooting issues such as hangs, slow performance, memory leaks or fragmentation, and crashes in any Win32 user-mode process.


This is very handy if you are responsible for troubleshooting IIS and related application issues.

System.Web.Mail and PDF getting corrupted workaround

I was troubleshooting an issue where I was sending an email using .NET 1.1 and attaching PDF files. The PDF files where getting an error when trying to open the attachment.  Here is what was displayed in Adobe reader.  "There was an error processing a page. A file I/O error has occurred".  Thanks a bunch to Dave Wanta, creator of http://ASPNetEmail.com for providing a great resource about System.Web.Mail ( http://www.systemwebmail.com ).  A similar example worked in ASP.NET 2.0, comparing email headers provided the clues it was how the attachment was getting encoded.  I found the answer in the article listed below.

This article explains it.

The bolded code is what you have to alter

<%@ Page Language="C#" %>
<%@ Import Namespace="System.Web" %>
<%@ Import Namespace="System.Web.Mail" %>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<script runat="server">

protected void Page_Load(object sender, EventArgs e)

    string FilePath = Request.PhysicalApplicationPath + "/c.pdf";
    MailMessage msgMail = new MailMessage();

    msgMail.To = "[email protected]";
    msgMail.From = "[email protected]";
    msgMail.Subject = "Your Favorite Subject";
    msgMail.Body = @"Some Text goes here";
    msgMail.Attachments.Add(new MailAttachment(FilePath, MailEncoding.UUEncode));
    Response.Write("Thank you."); 


<html xmlns="http://www.w3.org/1999/xhtml" >
<head runat="server">
    <title>Untitled Page</title>
    <form id="form1" runat="server">

Hope this helps

Steve Schofield
Microsoft MVP – IIS


IIS7 – post #28 – 86 days and counting for IIS7

If longhorn RTM runs as well as RC1 has, things are going to be really awesome!  My RC1 (version 5600) Longhorn server has been up for 86 days and counting.  I’ll put some stats together to see how many requests https://iislogs.com has served.  Memory usage has stayed at about 80% to 85% memory usage.  Not bad for a desktop pc with 512 MB shared memory.   I wanted to pass this along to let people know how stable IIS7 and Longhorn is.  Exciting things to come! 

‘Here is a picture showing the uptime.

How to fix – HTTP Headers – Always return 200 code

I found an article that explains in further detail how to make the "404 Not Found" show-up even when using a custom error page.  You need to add <% response.status = "404 Not Found" %> to your custom 404 webpage and the appropriate status code is returned. 

http://web-sniffer.net/ tool.

‘Here is a link to the article

‘Status codes KB article.

IIS7 – post #26 – Logging in Vista options

I’m following a thread in the newsgroups, actually I replied a few times about setting Logging options at a global level.  Unlike previous versions of client OS’s, Vista allows more than 1 site.  One thing that I couldn’t find was the Logging options in Vista IIS manager.  I can set this with appcmd and manually set in applicationHost.config.   There are 2 sections I could find, <system.applicationHostlog> section and under <sites/site/siteDefault>  Here are some raw notes I had.  I tried to clean up as best as possible.  One of my favorite appcmd command is "appcmd set config -section:XXXX -?   (XXXX represents what section)"  This pipes out a list of properties for that section.  It was a good evening digging into logging and Vista!   Hope you find this useful.

Example 1
C:WindowsSystem32inetsrv>appcmd list config -section:log
    <centralBinaryLogFile enabled="true" directory="%SystemDrive%inetpublogsLogFiles" />
    <centralW3CLogFile enabled="true" directory="%SystemDrive%inetpublogsLogFiles" />

Example #2
C:WindowsSystem32inetsrv>appcmd set config -section:log -?
ERROR ( message:-logInUTF8

‘Set the log default path
C:WindowsSystem32inetsrv>appcmd set config -section:log /centralW3CLogFile.directory:c:wwwlogs
Applied configuration changes to section "system.applicationHost/log" for "MACHINE/WEBROOT/APPHOST" at configuration commit path "MACHINE/WEBROOT/APPHOST"

‘Set the log default output
C:WindowsSystem32inetsrv>appcmd set config -section:log /logInUTF8:true
Applied configuration changes to section "system.applicationHost/log" for "MACHNE/WEBROOT/APPHOST" at configuration commit path "MACHINE/WEBROOT/APPHOST"

C:WindowsSystem32inetsrv>appcmd list config -section:log
  <log logInUTF8="true">
    <centralBinaryLogFile enabled="true" directory="%SystemDrive%inetpublogsLogFiles" />
    <centralW3CLogFile enabled="true" directory="c:wwwlogs" />

Example #3
C:WindowsSystem32inetsrv>appcmd set config -section:sites -?
ERROR ( message:-siteDefaults.name

‘Set the default log path on the siteDefault section
C:WindowsSystem32inetsrv>appcmd set config -section:sites /siteDefaults.logFile.directory:c:wwwlogs
Applied configuration changes to section "system.applicationHost/sites" for "MACHINE/WEBROOT/APPHOST" at configuration commit path "MACHINE/WEBROOT/APPHOST"

Log schema in the IIS_schema.xml

 <sectionSchema name="system.applicationHost/log">
    <attribute name="logInUTF8" type="bool" defaultValue="true" />
    <attribute name="centralLogFileMode" type="enum" defaultValue="Site" >
      <enum name="Site" value="0"/>
      <enum name="CentralBinary" value="1"/>
      <enum name="CentralW3C" value="2"/>
    <element name="centralBinaryLogFile">
      <attribute name="enabled" type="bool" defaultValue="false" />
      <attribute name="directory" type="string" defaultValue="%SystemDrive%inetpublogsLogFiles" />
      <attribute name="period" type="enum" defaultValue="Daily">
        <enum name="Hourly" value="4"/>
        <enum name="Daily" value="1"/>
        <enum name="Weekly" value="2"/>
        <enum name="Monthly" value="3"/>
        <enum name="MaxSize" value="0"/>
      <attribute name="truncateSize" type="int64" defaultValue="20971520" validationType="integerRange" validationParameter="1048576,4294967295" />
      <attribute name="localTimeRollover" type="bool" defaultValue="false"/>
    <element name="centralW3CLogFile">
      <attribute name="enabled" type="bool" defaultValue="true" />
      <attribute name="directory" type="string" expanded="true" defaultValue="%SystemDrive%inetpublogsLogFiles" validationType="nonEmptyString" />
      <attribute name="period" type="enum" defaultValue="Daily">
        <enum name="Hourly" value="4"/>
        <enum name="Daily" value="1"/>
        <enum name="Weekly" value="2"/>
        <enum name="Monthly" value="3"/>
        <enum name="MaxSize" value="0"/>
      <attribute name="truncateSize" type="int64" defaultValue="20971520" validationType="integerRange" validationParameter="1048576,4294967295" />
      <attribute name="localTimeRollover" type="bool" defaultValue="false"/>
      <attribute name="logExtFileFlags" type="flags" defaultValue="Date, Time, ClientIP, UserName, SiteName, ServerIP, Method, UriStem, UriQuery, HttpStatus, Win32Status, ServerPort, UserAgent, HttpSubStatus">
        <flag name="Date" value="1"/>
        <flag name="Time" value="2"/>
        <flag name="ClientIP" value="4"/>
        <flag name="UserName" value="8"/>
        <flag name="SiteName" value="16"/>
        <flag name="ComputerName" value="32"/>
        <flag name="ServerIP" value="64"/>
        <flag name="Method" value="128"/>
        <flag name="UriStem" value="256"/>
        <flag name="UriQuery" value="512"/>
        <flag name="HttpStatus" value="1024"/>
        <flag name="Win32Status" value="2048"/>
        <flag name="BytesSent" value="4096"/>
        <flag name="BytesRecv" value="8192"/>
        <flag name="TimeTaken" value="16384"/>
        <flag name="ServerPort" value="32768"/>
        <flag name="UserAgent" value="65536"/>
        <flag name="Cookie" value="131072"/>
        <flag name="Referer" value="262144"/>
        <flag name="ProtocolVersion" value="524288"/>
        <flag name="Host" value="1048576"/>
        <flag name="HttpSubStatus" value="2097152"/>