PDA

View Full Version : Why no Log Entries?



Joe Coley
14-Aug-2006, 01:09 PM
I just today activated an Electos site -- which has been getting hits
throughout the day. However, unlike my other Web apps, there have been no
entries made to the log file, even though it appears to be turned on, and
has been set to maximum 0 (for an unlimited number of entries).

Joe Coley
14-Aug-2006, 01:37 PM
To further confuse me, I just checked the "mywebsite" default site and it is
in fact logging connections. This is running on a Windows2003 Service Pack
1 machine. Looking at the security settings they appear to be the same.

Buffaloed in MA,
Joe


"Joe Coley" <sjoec@charter.net> wrote in message
news:Wj7$L28vGHA.3652@dacmail.dataaccess.com...
> I just today activated an Electos site -- which has been getting hits
> throughout the day. However, unlike my other Web apps, there have been no
> entries made to the log file, even though it appears to be turned on, and
> has been set to maximum 0 (for an unlimited number of entries).
>
>
>

Knut Sparhell
15-Aug-2006, 03:23 AM
Joe Coley wrote:
> I just today activated an Electos site -- which has been getting hits
> throughout the day. However, unlike my other Web apps, there have been no
> entries made to the log file, even though it appears to be turned on, and
> has been set to maximum 0 (for an unlimited number of entries).

The Web Application log is always "turned on". It can't be turned off
by the administrator, as far as I know. What you can turn on or off is
the "all access" logging. This means that every session creation and
closing is logged by the Web Apllication Server. Even if this is not
eabled, the application itself (Electos) may log, using the LogEvent method.

Examine your Windows Event Log, Application section. This is beacuse
the usual reason for no logging is that the log data file is corrupt.
If it happens, the Web Application Server will disable all logging and
report this to the Event Log at startup.

To fix this, delete the webapp.log and restart the Application Server
(service).

--
Knut Sparhell, Norway

wila
15-Aug-2006, 09:43 AM
Hi Knut,

Knut Sparhell wrote:
> To fix this, delete the webapp.log and restart the Application Server
> (service).

Don't you love that fix :P
I know its the standard solution for this webapp problem, but a "delete
your history" in order to get the history log working always felt a bit
of a counter intuitive solution to me.

Guess its the price of having a proprietary closed log file format as
you can't fix it.. you cannot save history either as its a bit of a
problem viewing it in bits and bytes. Converting the data from Unicode
to Ansi helps a tiny bit, but that's about it.

...and don't get me even started on using detailed logging on a high
traffic website as it doesn't work that well (too slow in the viewer
triggering the weirdest error, sorting the data works 'kind of' as it
gets reset when refreshed, you can't view details on a lower screen
resolution...)

The only thing i think it's useful for (*very* useful i might add) is to
spot runtime errors, not for detailed visiting logs.
Of course that's where the IIS logs come in handy.

Ok, off my soap box now <g>
--
Wil

Baz
15-Aug-2006, 07:14 PM
what colour IS your soapbox this year, anyway?
Baz.