Upon perusal of the analog-help archives, I noticed a couple of references to problems
with the Win2K W3C Extended format. Putting in my $0.02, I'd like to confirm a couple
of statements I came across...
Turning on Referer and Browser data for the W3C Extended format in the Management
Console breaks Analog's parsing, period. Turning OFF Referer and Browser data fixes it
immediately.
Analog does, in fact, happily auto-detect the Fields data and generates what should be
a workable LOGFORMAT.
I tried hand-creating a LOGFORMAT line when I had the Referer and Browser data turned
on with no good results.
With Referer/Browser enabled, Analog complained of everything from "no file names" to
corrupt loglines... usually corrupt lines. If I were smarter, I'd almost try playing
with the possibility that IIS5 isn't terminating the lines correctly... or something
like that...
I throw myself upon the mercy of the court. For the record, Analog is doing a
fantastic job with our Linux-based servers, so no I'm NOT blaming this fine product!
At this time I'm simply going to suffer with the lack of Browser data... which, given
that the machine in question is our token Frontpage-enabled unit, is a bit of a pain.
But what can you do, hmm?
Karel P Kerezman
Network Administrator
Entercom Radio Portland
KGON KKSN-AM/FM KNRK KFXX KRSK
Visit the Lab: http://washuu.kgon.com
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GO d- s: a- C++ UL P+ L++++ E---- W++ N+++ o-- K- w---
O M V-- PS+ PE Y+ PGP t 5++ X-- R tv+ b+++ DI++ D++
G e h---- r+++ y++++
------END GEEK CODE BLOCK------
------------------------------------------------------------------------
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe" in the main BODY OF THE MESSAGE.
List archived at http://www.mail-archive.com/[email protected]/
------------------------------------------------------------------------
