3 Replies Latest reply on Feb 18, 2014 7:13 AM by lhoong

    Send mail stopped working for scheduled script on FMS13

    nealalanfrank

      Greetings all!

       

      I have scheduled a script that sends out emails using the FMS smtp settings every 30 minutes. It was working like a champ until I attempted to upgrade FMS12 to FMS13. The short of it is FMS13 isn't working for us yet for multiple reasons and so we rolled back to FMS12, however, the send mail still doesn't work even though we are now back on 12 where it used to work. The SMTP Test works; I receive the test email. If I run the script manually, not by the server schedule, the email goes out. But, if I let the schedule trigger the running of the script then the emails don't go out. Any ideas?

       

      Thanks!

       

      Neal

        • 1. Re: Send mail stopped working for scheduled script on FMS13
          wimdecorte

          Any info in the FMS event log?

          • 2. Re: Send mail stopped working for scheduled script on FMS13
            keywords

            Maybe the schedule trigger got corrupted in the conversion process. Try deleting it and creating a new trigger.

            • 3. Re: Send mail stopped working for scheduled script on FMS13
              lhoong

              Neal,

               

              I encountered a similar situation recently. In my case, it was a scheduled script on FMSA11 to process about 2000 records and send email as appropriate, all within a 30-min. window, every 30 min.. The process ran flawlessly when via FMP client but resulted in numerous "Can't send email errors" (1506) in the FMS log when scheduled to run by FMS. The problem was solved by using an email plugin (we use 360Works Email) instead.

               

              I suspect what was happening was that every time the built-in SMTP function is run, it tries to establish a new connection to the mail server. If you have a lot of email to send within a short time-window, the email server may balk at having so many connection requests from the same IP. Switching to the email plugin allowed us to establish a single connection to the email server at the beginning of the process, through which all subsequent emails were sent. The single connection is closed at the end of the process.

               

              Something similar may be happening in your case, and using an email plugin may provide a solution.  Good luck.

               

              Lee.

              =================

              Binary Assist

              220 Gaines Oak Way

              Suwanee, GA 30024

              Voice: (678) 313-5604

              Internet: lhoong@binaryassist.com

              Website: www.binaryassist.com

               

              FileMaker Certified Developer