Lotus Domino Administrator 8 Help - An agent isn't running as expected

TROUBLESHOOTING

An agent isn't running as expected
In addition to the possibility that there are errors in the agent code, an agent may fail to run properly because the agent has insufficient access or because the agent is not set to run on the given server.

1. Insufficient access in the database ACL can prevent an agent from running properly. For example, a user may design an agent that copies selected documents from database A to database B. If the user -- and by extension, the agent -- doesn't have Author access in the ACL of database B, the agent runs, but it is not allowed to copy the documents. To determine if this problem exists, examine the Agent Log for access errors after the agent runs unsuccessfully.

2. If an agent won't run on a particular server, check the Agent Restrictions on the Security tab of the Server document. This section contains the "Run simple and formula agents," "Run restricted LotusScript/Java agents," and "Run unrestricted LotusScript/Java agents" fields that specify who has access to run agents on the server. Although a user who has the appropriate access in the database ACL may be able to create an agent on the server, without the appropriate access in the Server document, the user can't run the agent.

You should also check the Server Access section on the Security tab of the Server document. This section contains the "Only allow server access to users listed in this Directory," "Access server," and "Not access server" fields, which allow and deny access to the server. Because an agent inherits the access privileges of the person who creates it, the agent can't run on a server for which its creator does not have access.

3. Scheduling conflicts may prevent an agent from running. In the Server document, click the Server Tasks - Agent Manager tab and check the "Daytime Parameters Start time/End time" and "Nighttime Parameters Start time/End time" fields. Any time not specified in these fields represents downtime; if a user creates a scheduled agent and specifies that it run during the server's Agent Manager downtime, the agent will not run. Compare these fields in the Server document to the time the agent is scheduled to run. If a conflict exists, change the Agent Manager schedule on the server, or ask the user to reschedule the agent.

4. If a LotusScript™ or Java™ agent terminates before completing its tasks, check the "Max LotusScript/Java execution time" fields in the Server document. If a complex agent requires more time than is scheduled, the Agent Manager terminates the agent before completion.

Ask the user to reschedule the agent to run at night, when the default maximum execution time is longer; or increase the value of the "Max LotusScript/Java execution time" field in the Server document, as needed. If neither of these solutions is practical, ask the user to rewrite the agent as several smaller agents.

Glossary

Feedback on Help or Product Usability?

Help on Help

All Help Contents

Glossary