I found that if you turn on the "event log failure" alert under monitoring configuration / alerts, that on some systems you will get this error when shutting down the system without stopping ISA Server first. I think that ISA Server tries to write a "stopped successfully" type message but the server is too far into the shutdown process to allow ISA Server to write to the event log. I just turn that alert off. Pete -----Original Message----- From: Jim Harrison [mailto:jim@xxxxxxxxxxxx] Sent: Thursday, January 10, 2002 1:53 PM To: [ISAserver.org Discussion List] Subject: [isalist] Re: Failed to log event to system log http://www.ISAserver.org Possibly.. It's either a system glitch at that particular instant (never to be repeated, of course) or it's an indication that you may have access issues to the event logging service or the logs themselves. What other event log entries have you found in the near timeframe? Jim Harrison MCP(NT4, W2K), A+, Network+, PCG http://isaserver.org/authors/harrison/ Read the books! ----- Original Message ----- From: "Larissa Aigner" <laigner@xxxxxxxxx> To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx> Sent: Thursday, January 10, 2002 12:25 Subject: [isalist] Failed to log event to system log http://www.ISAserver.org Is the following alert reason of concern? Alert Service: failed to log event to system log. The following message '(null)' could not be logged. Thanks, Larissa ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: jim@xxxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub') ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: peter@xxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub')