TROUBLESHOOTING

An agent isn't running at the expected times
If the agent is running, but not at or near the expected times, the server may be busy with other tasks. To gather information about when the agent last ran and if it completed successfully, check the agent log. Then check for these conditions and correct them, if necessary.

1. 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. If the values in these fields don't account for a portion of the day, the Agent Manager will not run during that period. For example, if the daytime parameters are 8 AM and 5 PM and the nighttime parameters are 8 PM and 8 AM, Agent Manager will not run any agents between 5 PM and 8 PM.

2. The NOTES.INI settings may be incorrect. Check these Agent Manager settings in the server's NOTES.INI file:

3. Edit the NOTES.INI file to include the Log_AgentManager setting and set it to 1. You can also enable this setting in the Configuration Settings document in the IBM® Lotus® Domino™ Directory.

4. For servers running Domino 4.6 or earlier, the "Max % busy before delay" setting may have been exceeded. The "Max % busy before delay" setting on the Server Tasks - Agent Manager tab of the Server document controls the maximum percent of time the Agent Manager spends running agents. If the percentage of time is exceeded, a delay occurs before Agent Manager runs the next agent. After the percentage falls below the threshold, Agent Manager resumes running agents.

See also