I have several agents that do not show within the agent manager on the server even though I’ve verified that they are scheduled and enabled. Some are simple such as out of office, others are scheduled to run only once a day. While some of the OOO show in the list of agents scheduled to run others do not. All users have manager access to their mail files. There is no consistency as to the types of databases, most are mail files but I have a few that should be running against names.nsf. I’ve searched through a ton of posts, followed most suggestions, including replacing designs. Any thoughts out there?
Subject: Agents not showing in amgr
Check these three scenario if they are correct.
-
Did you specified a different server on the Run On Server property of the agent?
-
Do the signer or id of the one who saved the agent is allowed to run an agent in the server?
-
Do the signer or id of the one who saved the agent are allowed to run Unrestricted operations. (normally agent who access Domino server objects i.e, notes.ini or network resources are categprized as unrestricted). You can set this up in the security settings of your Domino in your PAB.
Subject: RE: Agents not showing in amgr
Agent is set to run on the correct server.Signer is allowed to run agents.
Signer (the notes admin) is allowed to run unrestricted operations.
Subject: RE: Agents not showing in amgr
Do you do a Tell amgr sched?
if the schedule is past, the agent will not be in the list. To have a “perfect” list (complete one), you would have to run a Tell Amgr sched at midnight to have the full list of the day.
For example. If you do a Tell amgr sched at 3Pm and that an agent is schedule to run a 2Pm, it will not appear in the list because the schedule of that day, for that agent, is done.
From the knowledge base
‘Tell Amgr Schedule’ at the server console. This command shows the Agent Manager schedule of all the agents scheduled to run for the current day. This is useful for debugging purposes, because you can see if your agent is waiting in one of the Agent Manager queues.
The Agent Manager has three different queues: a queue for agents that are eligible to run (E), another queue for agents that are scheduled to run (S), and a third for event-triggered agents that are waiting for their event to occur (V). Scheduled agents (the ones that have any of the schedule triggers) are queued in the “Scheduled” queue. When the time they are scheduled to run arrives, they are moved into the “Eligible to run” queue. Event-triggered agents (new mail and document creation/modification agents) are queued in the “Event” queue until an event they are waiting for occurs. When the event occurs, the agents move into the “Scheduled” queue and then into the “Eligible to run” queue.
Here is a sample output from the “Tell amgr schedule” remote console command:
E S 04:03 PM Today agent1 CENTRAL.NSF
S S 05:04 PM Today agent2 CENTRAL.NSF
V U agent3 CENTRAL.NSF
The first column of the output contains the Agent Manager queue type. The second column contains the agent trigger type, where S means the agent is scheduled, M represents a new mail-triggered agent, and U represents a new/updated document-triggered agent. These columns are followed by the time the agent is scheduled to run, the name of the agent, and the database name.
In the sample output above, agent1 is a scheduled agent that has been moved to the “Eligible to run” queue, and it will run as soon as the Agent Manager is free to run it. Agent2 is a scheduled agent that is waiting in the “Scheduled” queue for its scheduled time to arrive. Agent3 is an event-triggered agent waiting in the “Event” queue for a document to be created or modified.
JYR