I have been fighting to get this Out of office agent working, no Joy.
I am using Win2K and Notes client 6.01 and DOM server 6.01.
If I run it from the client agent designer screen by right clicking and selecting RUN it works fine.
When the server runs it through agmr, I can see the job scheduled with “s” status but
I get the following error message,
started running agent ‘OutOfOffice|OutOfOffice’ on 06/13/2003 04:12:20 PM
Running on new or modified documents: 5353 total
Found 5353 document(s) that match search criteria
06/13/2003 04:12:20 PM: 5353 found for processing.
06/13/2003 04:12:26 PM: Error (4000): Notes error: The server is not responding. The server may be down or you may be experiencing network problems. Contact your system administrator if this problem persists.
(This same message 3 tims)
06/13/2003 04:12:26 PM: 3 errors detected.
Ran LotusScript code
Done running agent ‘OutOfOffice|OutOfOffice’ on 06/13/2003 04:12:26 PM
It’s amazing how much time can be wasted on something like this.
Subject: Check the servers network port configuration
This looks like a network port config issue, not a out-of-office agent issue.Take a look at the server document in the Domino Directory, at the Ports, Notes Network Ports tab.
Make sure that the “Net Address” column has the correct network addresses listed for each port.
For a brute-force test, temporarily change the Net Address of the servers TCPIP port to “127.0.0.1”, restart the server and try again. Chances are that it will work now. If that’s the case, you had the wrong network address listed.
The error you posted seems to suggest that the out-of-office agent ran fine, but was unable to send the out-of-office email, due to the bad network port configuration.
YESS!!!Thank you, I found your answer after 5 years.
The “trace servername” reported an obsolete IP address. I looked for every occurrence of this IP and found one forgotten Connection document. This was the reason why the mails stopped working.
The problem is not with the agent but with your configuration, I think. There is a note on this error message in the Agent FAQ, did you try suggestions in the FAQ?
If that field was misconfigured, it would not run the agent. From the log it is clear that the agent ran, so it is not the agent security that is causing the problem.