I have a script that sends notification emails. It stopped sending emails after the server HD was cloned by their IT department.

The script works as intended from FM, I receive the emails, client receives the emails.

When sending from server, the scrip completes with errors:

 

http://cloud.zerobluetech.com/image/2G1b2u0B2M3A

http://cloud.zerobluetech.com/image/0O321Z0N2R3c

I really don't think the second error is relevant.

I checked and the file permissions are correct for FM server, the login account clearly works.
The system clock is fine on the server, getting time from Apple.

Any ideas anyone?

your link does not work.

 

Do you do any error trapping and logging for the server-side scripts?  If so what do they say?

It could be that the new server does not allow outgoing SMTP...

Yeah, it does, it was just double-pasted. :-)

 

I can set up error trapping.

 

If the new server had SMPT issues, would I get the notification that the server schedule completed?

Ok, sent test email through gmail, and that worked, so the server can connect through SMTP.

I debugged the offending script in FM and there's not one error and the alert email came in.

 

I am scratching my head here.

Glad I could help you fix it

 

As to the schedule completing without reporting it in the admin console: it might, depends on how you have configured the allow user abort and set error capture.

The FMS event log will tell you if any script errors were thrown.

The errors are in the screenshots above (edited original post).

 

Problem is not solved.

Not knowing what your routine is like but I'm guessing there are a number of records that you locate and then loop through to send through SMPT.  Are you tracking in your script which ones are sent ok and which ones are not?

 

The 1506 error is a pretty generic one.

 

I'm also seeing error 401 which is a bit weird, where does that one come from?

None of them get sent out from the server.

 

I'm gonna make some changes to the script and experiment.

I learned that the cclist gets a question mark for some extra recipients, which apparently FMPA didn't have an issue with but the server does.