>>Hi
>>
>>Can anyone recommend software or techniques to alert when a server is having problems. I have scheduled jobs running that alert me if there is an error but I don't get alerts if the server has experienced a problem and the scheduled jobs just don't get run.
>>
>>I was wondering if I need something that regularly tells me I'm here and I'm working like a heartbeat.
>
>There are lots of ways to approach this:
>
>- is the server a Microsoft server, or something else?
>- do you want a Fox-only solution?
>- do you want the server to periodically broadcast a heartbeat, which your workstation monitors, or do you want your workstation to periodically poll the server?
>- do you want to monitor a heartbeat, or be explicitly notified if/when a problem occurs?
>
>One simple thing to do is periodically attempt to write a file to the server, and/or PING its IP address. One potential issue with this is that it might not be a real indication of availability. For example, if your scheduled task relies on Exchange running on the server, and Exchange has a problem, the file-write test might succeed but your task fail because Exchange is down or has a problem.
>
>SNMP ( http://en.wikipedia.org/wiki/Snmp ) is specifically designed for this type of task (see "Usage Examples"). You can set up an SNMP agent on the server, and configure your W/S to be a management station to receive info ("traps") from the server's agent, or to query the server's agent on demand, or on a schedule. All server OSs (MS or otherwise) have SNMP agent implementations available.
>
>Some server management software such as Dell OpenManage can be configured to send alerts via e-mail. In the MS world, tools such as System Monitor can be used to monitor local or remote machines. There are other tools available with versions such as Small Business Server that can be helpful for specific monitoring tasks.


Thanks Al

There's several servers (all microsoft but different flavours) I wouldn't want a workstation to be involved. rather Server A checks Server B Server B checks Server C and Sever C checks Server A. Any servers detect issues they email or sms the error reporting addresses.



Nick