i created an agent to run on a stand-alone R6 client by schedule in order to move new or modified documents to certain folders (Mail-DB). The checkbox “enable local scheduled agents” in my user preferences is enabled, but still the agent does not start. Debug is of no use cause nothing happens - the agent somehow is not triggered.When i do start the agent from the action menue though it works perfectly well?
Subject: locally scheduled agent on stand-alone client doesn´t start
And how did you specify what server it should run on? It should say Local. And where is the database residing? Should be Local. Did you run “agent test” on the agent? That’s how I start when I have a problem, it tells you if it will run or not and why.
Did you look at “Troubleshooting agents in R6” article (in Agent FAQ) it gives you a lot of help on how to get it to tell you what is wrong.
Subject: RE: locally scheduled agent on stand-alone client doesn´t start
unfortunately anything you were suggesting already had been tried by myself when posting.
Subject: RE: locally scheduled agent on stand-alone client doesn´t start
Rick had good suggestions. If you could include information you obtained in your debugging in your post, perhaps people will be able to give direct assistance.
Subject: summary: locally scheduled agent on stand-alone client doesn´t start
SITUATION: *Client: Lotus Notes 6.0 - (stand-alone)-> no server.
*Template: StandardMail R6
*locally scheduled agents (in “user *preferences”) is enabled
*server the agent runs on is LOCAL
*database resides on is LOCAL (stand-alone client!)
Agent Test:
The following will occur when this agent is run:
Agent designed to run as locally scheduled agent for user ‘CN=Florian Zimmermann/O=y’
Agent scheduled to run on ‘CN=Florian Zimmermann/O=y’.
Started running agent ‘yMailRules|yMailRules’ on 18.03.2003 09:11:14
Running on new or modified documents: 73 total
Found 73 document(s) that match search criteria
Testing: Ran LotusScript code
Done running agent ‘yMailRules|yMailRules’ on 18.03.2003 09:11:14
Question1: does it make sense to perform “test agent”, when it is scheduled (local or server)?
when i do rightclick the agent and choose “Log” it says that this agent never has run before - but it should have done so(by schedule)
Agent:
no UI class in the agent
default access for viewing and running this agent = all readers and above (default user in DB ACL = manager)
Subject: RE: summary: locally scheduled agent on stand-alone client doesn´t start
Generically, speaking it does make sense to run Test for locally scheduled agents because it catches the most common errors. But it does not catch them all. It your case, though it appears not to produce definitive results.
Since the common gotchas don’t seem to be the problem, the next thing I would look at would be the trigger type. What trigger are you using? ‘before mail’ delivery is designed to run by the router, and would never run as locally scheduled agent. ‘after new mail’ trigger is triggered by events generated by the router which does not happen on the client, and it runs based on the special settings designed to be a catch all for replicated mail. You can find more info on these settings in the article “Minimizing delays in the agent manager”.
Have you set up to catch messages in the local debug file? In some situations you will find additional information/warning there. (I have notes on how to do it for locally scheduled agents in "Trouble shooting agents in R5 and R6).
Good luck, please post when you figure out what it is. I am sure it will help someone else in the future!
Subject: RE: summary: locally scheduled agent on stand-alone client doesn´t start
as i described in my first post the agent should execute when condition “new or modified documents” is true. how can i debug execution, when it just does not start? i assume then, that the problem lies within the trigger, but it is beyond my knowledge which conditions to meet in order for my agent to start (then i´d gladly debug).
Thank you for your posts so far.
Subject: RE: summary: locally scheduled agent on stand-alone client doesn´t start
Have you read “Minimizing delays in the agent manager?” I found that article very helpful to see the default condition which control it and how to change them. If the condition are met and the agent does not start, the system generates a message why it could not start. For locally sheduled agents you need to get this information from the local debug file like “Troubleshooting agents” explains. Hopefully this will get your further along to figuring it out.