Das sagt die KB dazu :
KlickiProblem
A server runs a Notes agent, such as the Out of Office agent, in the background, which is supposed to send a mail message. The agent runs, but the mail message is never sent. In some cases errors such as the following are logged in the Notes log:
"Unable to find path to server" or,
"Server Not Responding" or,
"...remote server is not a known TCPIP host"
Or, the Agent Log will contain a message such as:
"Unable to send mail" or,
"Server Not Responding"
Mail is sent correctly when a user runs the same agent manually from a workstation.
Note: In order to see agent activity written to the Notes Log the following property must be enabled in the Notes.ini file:
Log_AgentManager=1
Solution
These errors may be caused by an improper entry for the Mail Server field in the Server document within the public Name & Address Book (NAB), or it may be caused by a server configuration or TCPIP issue. Several cases have been seen where the Network Address field for a TCPIP port contained either an incorrect host name or an IP address, or DNS was not working correctly.
To troubleshoot this issue:
Check the Mail Server field in the Server document. If this entry is incorrect the error returned typically is: "Server Not Responding". This might happen if the server name has been changed and this entry has not been updated. The entry should match the server's abbreviated hierarchical name. Example: Mail01/US/Widgets
From the server's client attempt to open a database on the server. Indicate the server using the server name rather than using Local. If this produces an error, then the TCPIP port setting's Network Address entry within the Server document should be checked for accuracy against their Hosts file or DNS. The correct syntax to use in the Network Address field should be the server's Fully Qualified Domain Name (FQDN). For example, Mail01.widgets.com. Refer to the related document, "Troubleshooting Script: How to Diagnose Notes and Domino TCP/IP Issues" (#144302) for more information on troubleshooting TCPIP issues.
If the above troubleshooting techniques do not resolve the issue then see the Supporting Information section and the Related Documents noted below for troubleshooting this issue further.
LotusScript agent that can be used to rule out a problem within the agent itself
Use the following LotusScript code to create an agent that simply sends a message to the person troubleshooting the problem. If the message is not sent, then this proves that the problem spans all background agents on the server, and rules out anything specific with the agent that you are troubleshooting. This can be especially useful when trying to rule out code in a complex agent such as the Out of Office agent.
Dim session As New NotesSession
Dim db As NotesDatabase
Dim doc As NotesDocument
Set db = session.CurrentDatabase
Set doc = New NotesDocument( db )
doc.Form = "Memo"
doc.SendTo = "John Howard/OrgUnit/Org"
doc.Subject = "Here's the document you wanted"
Call doc.Send( False )
With Designer access, create a new shared agent and change the agent's action to Run "LotusScript". Click on the "Initialize" object and place this code between Sub Initialize and End Sub lines. Change the recipient of the Sendto Method in the code from "John Howard/OrgUnit/Org" to the hierarchical name of the person that is creating the agent.
Change the "When should this agent run?" setting to "On Schedule More Than Once A Day". Click on the Schedule button and change it to run Once every 5 minutes. Save the agent and enable it. An email with the subject "Here's the document you wanted" should be sent every 5 minutes.
If no mail is sent, then the problem spans all background agents on the server and is not an issue with the coding of the particular agent.
IMPORTANT NOTE: The above is a sample script, provided only to illustrate one way you can approach your troubleshooting. Notes Support Services does not support this script and will not be able to customize it for a customer's specific configuration.
Troubleshooting Technique for Cases Where No Error Occurs:
In cases where mail does not get sent and no errors are logged, error handling around the line which sends a document may capture an error.
...
On Error GoTo SendFailed
Call doc.Send( False )
On Error GoTo 0 ' disable error handler
An example of an appropriate error handler would be
SendFailed:
Print "Mail send failed because of Error " & Str(Err) & ", " & Error$
Resume Next
Scenario Where Both a Public and a Private Port Exist:
It has also been observed in one incident that this issue can occur on a server where both a public and private port exist (refer to the document, "How to Assign Multiple NICs and/or IP Addresses for a Host Computer and Domino Server Using TCP/IP" (#155513) for an example of this), even though the configuration appears correct. As an acceptable workaround in this specific scenario, a Server connection document can be created that is from the Server itself and to the intended IP address of this server (as in the document for the AS/400, "AS/400: Scheduled Agents that Include @MAILSEND or Send Method Do Not Deliver Mail" (#170217)).
Supporting Information:
This issue occurs because when the server runs an agent, it accesses the server as a client. The Server document is used in place of a Person document for user information for this particular client.
The server uses the entry in the Mail Server field of the Server document as its home server. This defaults to the server itself. If the network address of the server is incorrect, or the server cannot resolve the host name in the network address field, it is unable to make a connection to send mail, and an error occurs.
NOTE: If you change the Mail Server field, the server may need to be downed and brought back up in order for the change to take affect.
The Server document can be located by opening the Servers view, then opening the Servers sub-view in the Public NAB (also called the "Domino Directory" in Notes R5).
Thema: Out of Office Agent läuft nicht (Gelesen 7521 mal)