Iis – What does zero time-taken in IIS log file mean

iisiis-6log-files

What does a 0 (zero) in the time-taken field of an IIS 6 log really mean? I'm trying to get the average time-taken before and after a particular change to see if it had a positive affect, but I'm not sure how to interpret the zeros. Including/excluding them from the average gives me radically different results.

Specifically, if the application actually performed a database hit during a request, it seems virtually impossible for the time-taken to be zero. Is it reasonable to assume that a database call did not occur in that case?

Here's an example from my log file:

cs-method: GET
sc-status: 200
sc-win32-status: 0
sc-bytes: 6,966
time-taken: 0
cs(User-Agent): Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+5.1;+Trident/4.0;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.4506.2152;+.NET+CLR+3.5.30729)

Best Answer

Are they image files, or static files? They might serve up at virtually 0 ms. Also, as Christopher G suggested, a 304 non-modified wouldn't take any time either. Also, IIS caching would allow files to be served up fast enough that it wouldn't register any time. Compression of static pages also serves as a form of caching.

Related Solutions

IIS logs show sc-win32-status=64 but only through some networks

This is my understanding of the issue so far:

sc-win32-status 64 means “The specified network name is no longer available.”
After IIS has sent the final response to the client, typically it waits for an ACK message from the client.
Sometimes clients will reset the connection instead of sending the final ACK back to server. This is not a graceful connection close, so IIS logs the “64” code.
Many clients will reset the connection when they are done with it, to free up the socket instead of leaving it in TIME_WAIT/CLOSE_WAIT.
Proxies tend to do this more than others do.

Update: I found some interesting information here and here, so I basically re-wrote the page to ensure there wasn't any bad markup etc. and... the problem is now gone! It was just a shot in the dark, and I couldn't definitely say what it was that fixed the problem, since it was only affecting some of our clients under some very specific circumstances...

Windows – Password for iis after installing

Another try: is there a web.config file in wwwroot (or in a parent folder)? If yes, check if authentication is explicitly defined:

 <system.web>
     ...
     <authentication mode="Windows"/>
     ...

See: How To: Use Windows Authentication in ASP.NET 2.0 (MSDN)

Best Answer

Related Solutions

IIS logs show sc-win32-status=64 but only through some networks

Windows – Password for iis after installing

Related Topic