Further to my last. We have two SA's running, one on a remote server and one locally. The local machine does URL checks whilst the server machine installation performs service checks. Neither machine detected this stoppage we had which lasted at least 8 hours. Both running as a service only when run manually did they detect the failure. Why?
Also, the logging to SQL data is now recording NULLS in all fields except 'host'. David -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Lewis-Waller Sent: 20 March 2003 08:59 To: [EMAIL PROTECTED] Subject: [SA-list] SA isn't reliable Why is SA unreliable? We have found that SA doesn't perform checks reliably when running as a servive. We had the w3svc service stop this morning and SA didn't perform an IIS restart as part of its routine. However, when SA is launched after logging on then it restarted the service correctly. We've had this happen quite a few times and we feel that SA isn't the tool for the job if we can't rely on it. David To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive
