Our agents stopped sending email notifications. Some of them show up in the log as running successfully, and one agent even though it runs, it does not even recorded as running in the log databse. When I look at the agent log by right clicking on the agent and looking at log, it says done running and sent email notifications. No mail.
The agent signed by a user who is authorized to run agents in the server document.
Subject: Re: Schedule agents not sending emails
Formula or LS?
If it’s formula, you need to know that @MailSend, on almost any type of failure except no SendTo, doesn’t let you know it failed. It just doesn’t send anything. Typically this is due to the msg portion containing a non-text piece of data that hasn’t been converted to text.
Subject: RE: Re: Schedule agents not sending emails
It is script.
The agents used to send emails. Now, they run and send emails but users are not getting them.
Subject: RE: Re: Schedule agents not sending emails
You’ll probably find this message in the server’s log file:
“Notes error: You do not have a mail file/server specified. Use File Mobile Edit Current Location… to set them”
Just recycle your server.
HTH
Subject: RE: Re: Schedule agents not sending emails
I trapped the error it is same as you mentioned above. However, recycling the server did not help. I checked the server document and the "Mail Server’ field has the server name also correct.
Any other ideas?
Subject: RE: Re: Schedule agents not sending emails
Did you just restart Domino or reboot the whole box? Sometimes restarting Domino is not enough.
To check the ability to send mails, type
sh config mailserver
at the server console. If you get the response
“Invalid value for command option”
it means the server has “forgotten” its own name, thus the strange message in the log file.
We have this issue every 60 days the servers has been running straight on our iSeries box. It’s a well known bug Lotus seems to be unwilling to fix.
Subject: RE: Re: Schedule agents not sending emails
Opened a call with Lotus support regarding this and found out it has been addressed in Domino 6.5.5, SPR# BTLW69P4RG