Automation sending out emails in a "looped" function stops after sending 3 emails when run from server

Toad Data Point & Toad Intelligence Central
1

We have a remote server (Amazon AWS, “spinup”) with TDP (4.3.0.718 (64 bit)), which we use to schedule our automation scripts (we don’t have T.I.C.).

I created a script with a “loop dataset” element that sends an email with each loop. When run locally it performs as expected but when we run or schedule a run on the remote server the automation sends out the first 3-4 emails normally but then "chokes on the later ones. If the loop dataset is large enough (say 50) it sometimes happens that a couple of emails are send between the 20-30th loop before it chokes again. I have found that a “pause” element in the loop alleviates the problem a bit (when set to ~200 seconds or more) but this is a far from ideal solution.

The log shows the following error message:

– 6/11/2018 2:41:26 PM: test1.log: Email message:

– 6/11/2018 2:41:26 PM: test1.log: Setting up SMTP email

– 6/11/2018 2:41:26 PM: test1.log: Smtp Server: mail.xxxx.xxx (partly redacted)

– 6/11/2018 2:41:26 PM: test1.log: Smtp Port: 25

– 6/11/2018 2:41:26 PM: test1.log: Begin email send

– 6/11/2018 2:41:26 PM: test1.log: Socket connection has timed out. InnerException message follows: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond xxx.xxx.xx.xx:25 (partly redacted)

– 6/11/2018 2:41:26 PM: test1.log: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond xxx.xxx.xx.xx:25 (partly redacted)

– 6/11/2018 2:41:26 PM: test1.log: at a.ae.a(Exception A_0)

at a.ae.a(IPEndPoint A_0)

at a.p.a(IPHostEntry A_0, Int32 A_1)

at a.m.a(String A_0, Int32 A_1, Boolean A_2, Socket A_3, EndPoint A_4)

at a.m.x()

at a.f.m.x()

at a.f.l.a(MailMessage A_0, String A_1, EmailAddressCollection A_2, DeliveryNotificationOptions A_3, Smtp8bitDataConversion A_4, Boolean A_5, SendFailureThreshold A_6, Boolean A_7, DataTable A_8, Int32 A_9, String A_10)

at a.f.e.a(MailMessage A_0, String A_1, EmailAddressCollection A_2, DeliveryNotificationOptions A_3, Smtp8bitDataConversion A_4, Boolean A_5, SendFailureThreshold A_6, Int32 A_7, aw A_8, Boolean A_9, DataTable A_10, Int32 A_11, String A_12)

at a.f.n.a(String A_0, EmailAddressCollection A_1)

at a.f.n.a(Boolean A_0, String A_1, EmailAddressCollection A_2)

at Quest.Toad.Workflow.Activities.SendEmailActivity.SendMail(SmtpServer server, MailMessage email)

– 6/11/2018 2:41:26 PM: test1.log: Email_1 - There were errors encountered sending the message. See the log file for details.

– 6/11/2018 2:41:26 PM: test1.log: Continuing after error

–

Has anyone encountered this problem?

– 6/11/2018 2:41:26 PM: test1.log: Email message:

– 6/11/2018 2:41:26 PM: test1.log: Setting up SMTP email

– 6/11/2018 2:41:26 PM: test1.log: Smtp Server: mail.yale.edu

– 6/11/2018 2:41:26 PM: test1.log: Smtp Port: 25

– 6/11/2018 2:41:26 PM: test1.log: Begin email send

– 6/11/2018 2:41:26 PM: test1.log: Socket connection has timed out. InnerException message follows: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 130.132.50.52:25

– 6/11/2018 2:41:26 PM: test1.log: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 130.132.50.52:25

– 6/11/2018 2:41:26 PM: test1.log: at a.ae.a(Exception A_0)

at a.ae.a(IPEndPoint A_0)

at a.p.a(IPHostEntry A_0, Int32 A_1)

at a.m.a(String A_0, Int32 A_1, Boolean A_2, Socket A_3, EndPoint A_4)

at a.m.x()

at a.f.m.x()

at a.f.l.a(MailMessage A_0, String A_1, EmailAddressCollection A_2, DeliveryNotificationOptions A_3, Smtp8bitDataConversion A_4, Boolean A_5, SendFailureThreshold A_6, Boolean A_7, DataTable A_8, Int32 A_9, String A_10)

at a.f.e.a(MailMessage A_0, String A_1, EmailAddressCollection A_2, DeliveryNotificationOptions A_3, Smtp8bitDataConversion A_4, Boolean A_5, SendFailureThreshold A_6, Int32 A_7, aw A_8, Boolean A_9, DataTable A_10, Int32 A_11, String A_12)

at a.f.n.a(String A_0, EmailAddressCollection A_1)

at a.f.n.a(Boolean A_0, String A_1, EmailAddressCollection A_2)

at Quest.Toad.Workflow.Activities.SendEmailActivity.SendMail(SmtpServer server, MailMessage email)

– 6/11/2018 2:41:26 PM: test1.log: Email_1 - There were errors encountered sending the message. See the log file for details.

– 6/11/2018 2:41:26 PM: test1.log: Continuing after error

–

2

Hi,

I am not sure how this could be related to TDP. Isn’t it possible there are some restrictions on your server? When you are sending emails so often maybe FW or SMTP server can block your requests. Can you take a look on AWS if there are not any rules? Or can you try it with some different SMTP server?

Filip

3

This is definitely a network issue reaching the SMTP server. Adding the Pause is something I would have suggested but you are already doing this. We do not have a timeout value for email

I would try turning on Verbose logging. When you do this the email log will included a lot of detail. That detail might help.