Out Of Office agent woes

I know this topic has been hashed through already, but I’m a newbie to this game…

I have a user that I’m trying to get Out of Office (OoO) working on. It worked recently, so I know this is possible.

-Confirmed home mail server within location document

-“tell amgr schedule” shows that the agent is ready to run. I changed it run every two hours

-User has Manager Access to mail database

This is the log:

Started running agent ‘OutOfOffice|OutOfOffice’ on 07/31/2008 06:11:12 PM

Running on new or modified documents: 18614 total

Found 18614 document(s) that match search criteria

07/31/2008 06:11:12 PM: 18614 found for processing.

07/31/2008 06:11:12 PM: No errors detected.

Ran LotusScript code

Done running agent ‘OutOfOffice|OutOfOffice’ on 07/31/2008 06:11:12 PM

This is the test:

The following will occur when this agent is run:

‘CN=Paul Garth/O=DEPT’ has unrestricted rights to run LotusScript/Java agents on ‘CN=ACME/O=DEPT’.

Allow restricted operations flag is de-selected in this agent. Restricted operations will be disallowed.

Agent scheduled to run on ‘CN=ACME/O=DEPT’.

Started running agent ‘OutOfOffice|OutOfOffice’ on 07/31/2008 06:20:38 PM

Running on new or modified documents: 18614 total

Found 18614 document(s) that match search criteria

Testing: Ran LotusScript code

Done running agent ‘OutOfOffice|OutOfOffice’ on 07/31/2008 06:20:38 PM

Feel free to ask me questions to narrow this down, because it’s driving me a little batty…

Thanks.

Paul

Subject: Out Of Office agent woes…

check this out:http://www-1.ibm.com/support/docview.wss?rs=463&context=SSKTMJ&context=SSKTWP&q1="out+of+office"+and+troubleshoot&uid=swg21296389&loc=en_US&cs=utf-8&lang=en

Subject: RE: Out Of Office agent woes…

Thank you for the pointer to the diag tool and extra detail.

Will report back with my findings.

Paul

Subject: RE: Out Of Office agent woes…

I haven’t gone down the path yet of running the diag utility, but I didn’t notice a couple things:

  1. The OoO agent was working up until the user tried to extend the date. I’m thinking the user modified the date without first disabling the client, which confused the OoO agent – even though the date had been pushed back by two weeks I still got a notice a couple days later reminding me of disabling the prior date.

  2. Another user had been going into the OoO mailbox and was opening, foldering various emails. I believe this also affected the OoO agent because the mail had been modified.

When I have some time I’ll play with the diag tool – looks as if it will tell a lot.

Paul