Application not generating e-mails on server

We have a mass e-mail application on one of our mail servers. This application has been in production and working for two years or more. Here is the process.

Our marketing department creates an e-mail control document, which contains the subject and body of the e-mail along with date/time when it is scheduled to sent and who it is to be sent to (i.e. all employees). There is a scheduled agent which runs each half hour and builds and sends those e-mails.

Internally, it builds the e-mail in memory (body, subject, from, replyto, etc.) and then loops through the names sending to each name via call to docEMail.Send(False,docNAB.FullName(0)). Document sent is not saved.

When it runs as a scheduled agent, it does not generate those e-mails. When run manually (select agent and run) it works perfectly. The code has not changed in 6 months and has worked until this morning. I have it logging via NotesLog and it always runs to completion – no errors nor does it appear to abort anywhere.

One final note. Once while it was running as a scheduled agent, I was watching Mail.box and there were no documents being created there.

Does any one have any idea why apparently the server is not generating and mailing those documents?

Thanks for your help.

Ron Reed

Subject: Application not generating e-mails on server.

The id the agent is signed with - does it have rights to create documents in that database?

Subject: Application not generating e-mails on server.

I would check the rights for the agent signer when it is scheduled,make sure the signer has ability to create documents/run agents in the ACL.Also check the security tab of agent properties.

Subject: RE: Application not generating e-mails on server.

If your agent has not been modified, there are only 3 possible reason of failure. One is if your server’s security settings was changed and it restricts your agent to run on that server. Second is if the security settings of the database where the agent run was changed. Check if the signer and the delegated user is allowed to run agent in the database. Also check if your database property allows background agent to run. Third is if your agent is accessing different databases, check the security settings of those databases including the database property where it allows to run backround agent. Hope this help.