Darrell blogs about where URLScan logs its "failures" and points out that this is a very good place to start looking if you are running a "locked down" server and get *any* IIS-related problems. There are a few little known but extremely useful logs and tools like this that it would be handy to document somewhere. The first two that spring to mind are:

  • the code download log, which I believe MS provide an unsupported viewer to read, if you're having problems with IE code downloads (ActiveX controls, for instance)
  • the MDAC "component checker", which is very badly named "cc.exe", for trying to get to the bottom of "it works on my machine but not the customer's" problems with data access components

Anyone else think of any others?