** We were seeing periodic issues where for some reason one large outbound email would stop outgoing emails. When we would delete that email, all outbound would start flowing again. We were also seeing issues with the our outbound mail host server. Finally we would sometimes see issues with the Exchange servers that the inbound mailboxes were on. This routine exercises the round trip for two different mailboxes.
The processing with using two mailboxes tells us if it's an outbound issue, issue with the mailhost server, limited to one Exchange server or the other or even if the Exchange servers are backing up and there are email delivery delays. Dave ------------------------- dave.shell...@tycoelectronics.com (Wireless) ________________________________ From: Action Request System discussion list(ARSList) <arslist@ARSLIST.ORG> To: arslist@ARSLIST.ORG <arslist@ARSLIST.ORG> Sent: Thu Jul 15 16:11:25 2010 Subject: Re: Looking for Trouble David, Thanks. Regarding your email health routine, this lets you know if emails are bottlenecked or not processing, even if the email service is still running? Rebecca From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Shellman, David Sent: Thursday, July 15, 2010 1:28 PM To: arslist@ARSLIST.ORG Subject: Re: Looking for Trouble ** Rebecca, We use HP OpenView to monitor the arerror.log, the email log file (stderr.log and stdout.log), monitoring services and restart them if needed, etc. The monitoring is set to look for specific errors in the log files. In turn it's a learning experience. Each time we see something new we adjust the monitors to compensate for it. Instead of monitoring the email stderr.log file with OpenView, we could add workflow to the AR System Email Error Log form. Additionally workflow could be added to the AR System Email Messages form looking for if records are being set to sent or the record is flagged with an error. We have also written a specific email health routine that sends out an email (with a unique GUID) that creates a record in a receiving form. The receiving form has workflow that updates the Status of the appropriate record on the sending form. If the record in the sending form is not updated within a specific amount of time, an escalation triggers a page to us through TelAlert. Also have Server Statistics turned on. We have added workflow that watches the Floating Write Lic Connection field. A filter will email us a warning if the number goes over a certain level. If we reach a more critical level then again a filter triggers a page to us through TelAlert. Occasionally reviewing log files is also a way to identify what you should add some monitoring, work flow to alert, or even add workflow to create and error or a warning. Dave ________________________________ From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Boyd, Rebecca E. Sent: Thursday, July 15, 2010 9:37 AM To: arslist@ARSLIST.ORG Subject: Looking for Trouble ** Good Morning, Every day (most every day, anyway) I try to find problems before they find me. For instance, I check the Requester Module and email messages for errors. I got to wondering: what do other people do? Do you have certain forms or processes you monitor? Do you check your arerror.log or other server logs on a regular basis? Is there something you learned the hard way & now you always keep an eye on it because you never, ever want to repeat that lesson? Inquiring minds want to know… Thanks! Rebecca Boyd Application Administrator Information Systems 336.758.5671 [cid:image001.jpg@01CB2438.5FF98E30] _attend WWRUG10 www.wwrug.com<http://www.wwrug.com> ARSlist: "Where the Answers Are"_ _attend WWRUG10 www.wwrug.com<http://www.wwrug.com> ARSlist: "Where the Answers Are"_ _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_
<<inline: image001.jpg>>
